Minor update this time - a possible fix for all those axis detection problems, and an extension to 32 output DirectX buttons.

As always, new releases are available at http://vega.dyndns.org/x36/

Note that after installing this version, you may need to remap your axes in your games. The axes are now reported as:

X - X
Y - Y
Throttle - HID Throttle, may appear as 'Slider'
Rudder - HID Rudder, may appear as Z rotation (Rz)
Rotary 1 - X rotation (Rx)
Rotary 2 - Y rotation (Ry)

-D

Minor for you maybe...fixed a big problem for me in CFS3 (ie: using the thumb dial). Thanks again.

I got a Problem with the new Driver, MW4 Merc won´t run any more, when loading a mission it crashes back to desktop, it din´t with the old driver and doesn´t with the X36 unplugged, it gives the following error message :

STOP : Invalid allocation, 0 bytes

Processor Registers EAX=0x00000000 EBX=0x00000000 ECX=0x00000000 EDX=0x00000000 Flags=0x00000000
=================== ESI=0x00000000 EDI=0x00000000 EBP=0x0012F860 ESP=0x0012F6F8 EIP=0x00000000
EIP (0x00000000) ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
ESP (0x0012F6F8) 0012F854 0F5230C8 00000000 00000000 0012F688 0012F844 00000001 00000000
77C5A69A 00000020 00000041 00000000 00000010 00000F00 000000F0 0000000F
0000F000 77C5A9DF 77C5A9B2 03200001 00000000 0012F768 0012F7F0 0012F7A4

Machine details
===============
Executable name : D:\games\MW4-Merc\MW4Mercs.exe
Executable time, date : 14:07:54 Saturday 11/2/2002
Command line :
Current directory : D:\games\MW4-Merc
Current time, date : 13:56:50 Tuesday 11/12/2002
GameOS build version : Version 1.1 11/2/2000
Software rasterizer : d:\games\mw4-merc\blade.dll (Size 286,786 bytes)
User name : Pierre Waldfried
Machine name : ELYSIUM
Processor : 1403MHz AMD Unknown MMX 3DNow! SSE Model=6, Type=6, Stepping=2
Cache Information : Unknown
L2 r/w/rw speed : 8 cycles 5612MB/s, 8 cycles 5612MB/s, 8 cycles 5612MB/s
Main memory r/w/rw speed : 27 cycles 1662MB/s, 79 cycles 568MB/s, 72 cycles 623MB/s
Video memory r/w/rw speed : 741 cycles 60MB/s, 41 cycles 1095MB/s, 864 cycles 51MB/s
AGP memory r/w/rw speed : 197 cycles 227MB/s, 44 cycles 1020MB/s, 319 cycles 140MB/s
Operating system : Windows XP (5.1.2600) Service Pack 1
DirectX version : 8.04.02.0134
Time since booted : 0h 1m 24s
Time in game logic : 0h 0m 10.11s (on frame 693)
Time app running : 0h 0m 21.06s
Physical memory : 267,898,880 bytes (255 Meg)
Available physical memory : 47,501,312 bytes (45 Meg)
Swapfile size : 648,396,800 bytes (618 Meg)
Swapfile available : 467,083,264 bytes (445 Meg)
Virtual memory : 2,147,352,576 bytes (2048 Meg)
Available virtual memory : 1,853,509,632 bytes (1768 Meg)
Amount of stack used : 2576 bytes
Memory load : 82%
Desktop video mode : 1280,1024 32bpp
Mode when crash occured : Full Screen 800x600x32 Refresh=60Hz (NVIDIA GeForce4 Ti 4200)
Networked Machine : No
Executable version : 50.06.09.3002
PCI Chipset : Unknown

Processes Pri Threads Path
==========================================
CTHELPER.EXE : 8 : 2 : C:\WINDOWS\System32\CTHELPER.EXE
daemon.exe : 8 : 2 : C:\Programme\D-Tools\daemon.exe
hpztsb04.exe : 8 : 1 : C:\WINDOWS\System32\spool\drivers\w32x86\3\hpztsb04.exe
EM_EXEC.EXE : 8 : 2 : C:\PROGRA~1\ Logitech \MOUSEW~1\SYSTEM\EM_EXEC.EXE
AdBlocker.exe : 8 : 2 : C:\Programme\Tweak-XP Pro\AdBlocker.exe
MW4Mercs.exe : 8 : 17 : D:\games\MW4-Merc\MW4Mercs.exe

DLL Version numbers
===================
msvcrt.dll - Version 6.00.8397.0 - Found in D:\games\MW4-Merc
Could not find 'msvcrtd.dll'
msvcirt.dll - Version 6.00.8168.0 - Found in D:\games\MW4-Merc
Could not find 'msvcirtd.dll'
amstream.dll - Version 6.04.2600.0
quartz.dll - Version 6.04.2600.1106
Ir50_32.dll - Version R.5.06.15.2.44
dsound.dll - Version 5.1.2600.0
dinput.dll - Version 5.1.2600.1106
d3dim.dll - Version 5.1.2600.0
ddraw.dll - Version 5.1.2600.1106
dplayx.dll - Version 5.2.3677.134

Input devices
=============
Saitek X36 D-USB
Buttons 0
Axis 7
Sliders 1
POV hats 1

Sound device 0 (Current) - (HW Mixing Disabled)
==============
Description : SB Live! Audio [D400]
Driver file : ctaud2k.sys
Driver size : 835,636 bytes
Driver date : 13:00:32 Sunday 10/27/2002
Attributes : Final Release, Private Build
Driver version : 5.12.01.0244-1.31.0040
CERTIFIED : Yes
EMULDRIVER : No
CONTINUOUSRATE : Yes
PRIMARYMONO : Yes
PRIMARYSTEREO : Yes
PRIMARY8BIT : Yes
PRIMARY16BIT : Yes
SECONDARYMONO : Yes
SECONDARYSTEREO : Yes
SECONDARY8BIT : Yes
SECONDARY16BIT : Yes
MinSecondarySampleRate : 4000
MaxSecondarySampleRate : 191999
PrimaryBuffers : 1
MaxHwMixingAllBuffers : 32
MaxHwMixingStaticBuffers : 32
MaxHwMixingStreamingBuffers : 32
FreeHwMixingAllBuffers : 31
FreeHwMixingStaticBuffers : 31
FreeHwMixingStreamingBuffers: 31
MaxHw3DAllBuffers : 32
MaxHw3DStaticBuffers : 32
MaxHw3DStreamingBuffers : 32
FreeHw3DAllBuffers : 31
FreeHw3DStaticBuffers : 31
FreeHw3DStreamingBuffers : 31
TotalHwMemBytes : 0
FreeHwMemBytes : 0
MaxContigFreeHwMemBytes : 0
UnlockTransferRateHwBuffers : 0
PlayCpuOverheadSwBuffers : 0

Video device 0
==============
Description : NVIDIA GeForce4 Ti 4200
Company / Chipset : nVidia / GeForce4 Ti4200
Driver file : nv4_disp.dll
Driver size : 2,596,938 bytes
Driver date : 14:38:00 Friday 9/27/2002
Attributes : Final Release, Private Build
Driver version : 6.13.10.4072
Version : 6.13.10.4072
Hardware ID : 10DE.0253 (Rev 163, Subsys 0x0)
Video memory : 128,319,488 bytes (122 Meg)
Card texture mem : 128,319,488 bytes (122 Meg)
AGP texture memory : 67,108,863 bytes (64 Meg)
FourCC modes : UYVY YUY2 YV12 YVU9 IF09 IV32 IV31 NV12 RAW8 NVN0 NVN1 NVN2 NVN3 NVN4 NVN5 NVX0
Texture formats : 555 1555 4444 565 0888 8888 Bump map DuDv (8,8) Bump map DuDv (5,5) Bump map DuDv (8,8) FourCC (1TXD) FourCC (2TXD) FourCC (3TXD) FourCC (4TXD) FourCC (5TXD) 8bit FourCC (0MVN)
Z Buffer formats : 16 bit Z 24 bit Z (Z=32 (0xffffff00) Stencil=8 (0xff))
16 bit modes : 512x384 640x400 640x480 800x600 848x480 1024x768 1152x864 1280x720 1280x768 1280x960 1280x1024 1360x768 1600x900 1600x1024 1600x1200 1920x1080
32 bit modes : 512x384 640x400 640x480 800x600 848x480 1024x768 1152x864 1280x720 1280x768 1280x960 1280x1024 1360x768 1600x900 1600x1024 1600x1200 1920x1080
CERTIFIED : No
DRAWPRIMITIVES2 : Yes
DRAWPRIMITIVES2EX : Yes
DRAWPRIMTLVERTEX : Yes
FLIPINTERVAL : No
FLIPNOVSYNC : Yes
NO2DDURING3DSCENE : No
NONLOCALVIDMEM : Yes
NOPAGELOCKREQUIRED : Yes
CALIBRATE GAMMA : No
PRIMARYGAMMA : Yes
ZBuffer : 16 24
Render Depth : 16 32
Texture Size : 1x1 to 4096x4096
Maximum u,v coords : (for a 256*256 texture) 32.0
Guard Band Clipping: -100000000,-100000000 to 100000000,100000000
AlphaTest NotEqual : Yes
Missing Src blend :
Missing Dest blend :
AGP Texture : Yes
Texture Coords : 8
Blend Stages : 8
Max Textures : 4
Hardware T&L : Yes
Vertex Blending : 4
Maximum Lights : 8
Clip Planes : 0
Blend Lightmap : Ok
Blend Specularmap : Ok
Blend Detail : Ok
Linear vid memory : Yes
SELECTARG1 : Yes
SELECTARG2 : Yes
ADD : Yes
ADDSIGNED : Yes
SUBTRACT : Yes
MODULATE : Yes
MODULATE2X : Yes
MODULATE4X : Yes
BLENDCURRENTALPHA : Yes
BLENDDIFFUSEALPHA : Yes
BLENDTEXTUREALPHA : Yes
BUMPENVMAP : Yes
BUMPENVMAPLUMINANCE: Yes
DOTPRODUCT3 : Yes
ANISOTROPY : Yes
ANTIALIASSORTINDEP : Yes
FOGTABLE : Yes
FOGVERTEX : Yes
FOGRANGE : Yes
WFOG : Yes
WBUFFER : Yes
MIPMAPLODBIAS : Yes
WBUFFER : Yes
ZBUFFERLESSHSR : No
MIPNEAREST : Yes
LINEARMIPLINEAR : Yes
DONOTSTRIPELEMENTS : Yes
TEXTURE CLAMP : Yes
TEXTURE BORDER : Yes
TEXTURE MIRROR : Yes
ALPHAGOURAUDBLEND : Yes
SQUAREONLY : No
COLORFLATMONO : Yes
COLORGOURAUDMONO : Yes
COLORFLATRGB : Yes
COLORGOURAUDRGB : Yes
SPECULARFLATRGB : Yes
SPECULARGOURAUDRGB : No

I hope this will help you in finding out what error occured

MW4 has a problem with joysticks with 32 buttons. It came up at some point in the past. I thought there was a patch for it, but maybe not. There's nothing I can do - it's a bug in the game.

If you don't need any of the features of the new driver, just use the old one.

-D

[This message has been edited by Dhauzimmer (edited 11-12-2002).]

Thx I didn´t Know that, and the Ms Guys don´t seme to be botherd by it, as Mw4 Merc just came out

Woodman,

You might want to post this problem over at MekTek or DSC to see if someone might address it in a patch.

/D

Whoohooo

Before I grab this and upgrade... will it have any effect on XDP's axis programming?

Also-Does this driver possibly help with the "noise" many of us have been getting from the rotaries?

As always, thanks for your work Dhauzimmer

------------------
Fixitman
--------------------
FreeBirds VFW
--------------------
My F4 SP3 Profiles
--------------------

Fixitman:

There is no difference in XDProfile programming - only how the axes are reported via DirectX. I also haven't added any jitter correction, either. (If I had, it probably would've been a 2.110 release - something like that can be fairly CPU intensive).

-D

OK, thanks for the quick reply

------------------
Fixitman
--------------------
FreeBirds VFW
--------------------
My F4 SP3 Profiles
--------------------

Dhauzimmer how much did you change in the code to get the 32 DX Buttons?
is it just the line in FAKEHID.H refferring to the maximum buttons?

That, plus making sure my padding was correct, plus adjusting the data copied from the state buffer (making sure I was still within the 'reserved' window of HID codes), plus adjusting the 'Windows hat' commands to point to a new location, plus making sure the keyboard report blanks out those fields. Whew!

-D

Wow thats alot, I thought, maybe I could change back 2 or 3 lines of code, and compile a version wich has the new axis code but still the old 26 buttons, but i don´t think I could revert your changes (I understood but half of them).
Just a question, why does anyone need 32 DX buttons anyway? I never used more then 10 a keyboard can give you 567 keykombinations that are useable.

Actually, I didn't post the source for the new version. The axis changes, however, were entirely contained in fakehid.h - if you're really interested I could send you a patch or somesuch.

Why 32 DX buttons? It's actually got to do with game input models. Some games have various forms of keyboard-accessible menus or chat functions or somesuch. This is all good and well, but when that send message dialog is opened, all your keys suddenly map to the chat window - while your DirectX buttons continue to control the simulation. Nothing worse than being in the middle of typing a message when you come under fire, then be unable to take action because the chat window is still open! Sometimes a few extra DX buttons are all you need to map those last few critical functions.

I'm half tempted to add another 16 buttons to see if it will correct the MW4 issue.

-D

I just got my X45 a few hours ago and before doing anything I downloaded the latest Dhauzimmer Drivers, HazardScript, JimBud and all of the instructions for everything. I even printed them out so that I could follow along.

Well, I ran into problems from the start. When loading the drivers I clicked on the update driver tab and after that none of the Windows that popped up were the same as in the instructions. I went to load drivers from a specific location and after I directed it to the Dhauz driver folder it didn't like it because it kept taking me back to the start again. Finally after 3 tries I just let it look for the drivers,then after it didn't find any I directed it to the Dauz folder. It started downloading but immediately asked for the Win 98SE disk. I put it in and it continued on but couldn't find a joystick file (don't remember the exact name)on the 98SE disk, So, I directed it back to the Dhauz folder and finished up. When I check back in Device Manager the Dhauzimmer drivers showed up, so I continued on. I then continued following the directions and check out the x45 in the Gaming options window. Everything seemed to check out so I then went on to the calibration. I dropped the bpf file into the query file and this is where my windows again don't look anything like the ones in the instruction. The instructions said to open the Saitek controller properties window and select the settings tab. I assumed that I was supposed to go back to the gaming devices in the control panel to get to it. When I click on properties my window is completely different looking for the calibration, but I continued on anyway and it seemed to work except I didn't know what to do with the POV capture.

Again everything seemed to work so, I decided to make a profile using the JimBud editor. I entered the command file and assigned a few buttons hoping to try it out. I made an hsp file and when I drop it into the HazardScript desktop icon I get an error "Output file bin\_scratch could not be opened". Below that message it says something about making desktop icons. Well I know how to make icons and I checked to make sure that the shortcut target was right. I even tried to drop the default DX file in and got the same message.

Would appreciate any comments. I asssume that even though my driver installation didn't quite go according to the directions the stick seems to work. I don't know where I stand at this point. Maybe I should have used an older driver, or maybe I should just start over again.

ramjet

A patch would be really cool, and if you any other ideas for me to try out i will test them.

to ramjet
It looks like you dropped the hsp directly o the HazardScript executable wich doesn´t work, you have to use a shortcut. And to get it foolproof just copy the hsp in the hazardscript folder and run the comand line, change to the hazardscript folder and run hazardscript in the command line to programm the script, if that won´t work somthing went wrong in your instalation

Woodman:

I did drop it to a shortcut. In fact I deleted the one that I originally made and made another one. As I said I checked to make sure the target of the shorcut worked but whenever I drop an hsp file into the shortcut I get and error.

You also said:
"And to get it foolproof just copy the hsp in the hazardscript folder and run the comand line, change to the hazardscript folder and run hazardscript in the command line to programm the script, if that won´t work somthing went wrong in your instalation"

I don't quite understand what you mean by copying the hsp and run the command line. Are you talking about Run on the start menu, or do you mean in DOS?

Do you think I should just start all over from installing the drivers?

ramjet

Well ramjet, i ment to use the dos box, and to copy the scriptfile to the same folder as the hazardscript executable, then start hazardscript in the dos box and type
"hazardscript -debug filename.hsp"
and if that doesn´t work start einstalling evrything

Thanks Woodman. I finally got things running. Just to be safe I started over again first loading the drivers. You were right about the & symbol. I also had parentheses and an apostrope that didn't work either. Unfortunately, I didn't know that you can't edit an hsp file outside of the JimBuds editor and continue to use it. I first made the changes in wordpad and then discovered that JimBuds editor wouldn't open the file anymore. So, I had to redo the file again in JimBuds. It took a little more time but I got it working. Thanks again.

ramjet

Oh now i got your error, just don´t use Wordpad, it uses a Fileformat wich is like MS Word, HSP has to be plain Text, just use Notepad.