I bought the GOG release and was having errors getting the game to launch related to the deadzone X not being able to be configured.

I fiddled with vjoy, UCR, and plugging and unplugging all my USB devices.

The game runs fine if only my CH Figherstick Pro is plugged in.

It does not run if my Rudder Pedals (Racing pedals with UCR combining axis) are plugged in even if UCR and Vjoy are disabled and my figherstick is the default windows controller.

I'm posting this in case others have run into the same issue.

Thanks for posting to help out others.
I'll post this to try to help in some capacity.

Both the official MicroProse v1.2 and the un-official Code-Group v1.28 use the same joystick routines. Even the GoG released of those two seem too.
Although it is unclear to me if they messed with the DirectInput DX version.

I do know the dxinput.dll they included is suppose to get some modern sticks to work, but it fails on a lot of sticks. (removing the dll may help 'all in ones' like MSFF2 types.

Mark, you might know how to help me. I'm having an issue where my CH Fighterstck Pro's POV hat does not work.

I've tried what your page suggests of setting ID to 0. Unplugging my other sticks, etc. But no luck. Do you have any advice? If not I'm going to see if I can get UCR to map the hat as buttons.

I'm sorry not much. I haven't tested or worked with many other stick problems in a few years.
Try without the gog dx input.dll first though

ID0? hmmm are you talking about the eaw.ini entry? I think thats for 1.28a eaw.

You want Device ID 1 in windows os, JOY.CPL I believe its called. You run it from the start menu.
Stick should be first in line so EAW with except it for what it is.

The CH software I thought was supportive of this game with that stick too? *shrugs*


POV Hat Not Working Properly:
If you have problem with your POV hat not working properly with your joystick (for example: it fires guns when a POV hat direction is pressed. This has happened with a CH Flightstick), you can use the non EAW joystick routines (by using Windows API Joystick routine). To enable this mode, go edit the eaw.ini, and find the section [CONTROLS], and change the line from "Windows Joystick=0" to "Windows Joystick=1"

The CH Software doesn't not play completely nice with my system. It has some issues with Windows 10. I'm going to fiddle with it some more.