Page 1 of 1

Controller not working

Posted: Fri Sep 18, 2020 6:49 pm
by wbrooks003
Hello -

I recently installed the XWA Upgrade 1.6 and then the day 1 patch 1.0.

I used to play on the original version 2.02 of the game via Steam with my XBOX 360 Controller. I had installed Joy2Key and made a profile in order to map my controls the way I wanted them. Secondarily, I had downloaded this version of ddraw (https://github.com/rdoeffinger/xwa_ddraw_d3d11/releases) in order to enable keyboard and mouse support in lieu of a joystick in order for my XBOX 360 controller to properly emulate a Keyboard and mouse via Joy2Key. This worked really well.

Since installing the XWAUP the game does not read any type of joystick (shows no joystick buttons in the game controller menu) and as a result, I cannot fly my ship during missions, it just spins out of control.

I tried using the ddraw file I linked above, but it appears to be incompatible with the latest patched version. I receive an invalid parameters error message when trying to launch a mission that requires a ctrl+alt+del and end task. Does anyone have any suggestions on how to get my controller to be recognized and working again?

Thanks

Re: Controller not working

Posted: Sat Sep 19, 2020 1:12 pm
by wbrooks003
Hello again - I did some further tinkering. I was able to launch the game directly through steam, versus through the xwingalliance launcher by changing the names of the .exe files. I also had to use the no_dinput hook in order to prevent the game from crashing to desktop when launching a mission. Steam's controller support allowed the game to recognize my xbox360 controller and provided basic flight support (a step in the right direction); however, what frustrates me about this is the way the throttle maps to the analog trigger axis and there does not seem to be a way to disable this.

The version of the ddraw.dll that Reimar had modified of the JeremyaFr version has the keyboard/mouse support (which was helpful for doing some heavy customization to my controls with the 360 controller with Joy2Key). It also has the ability to unmap the throttle from the analog triggers. When I use this version of the ddraw DLL on the new v1.6 patch 1.0 version of XWAUP, everything appears to work fine until you are about to launch the mission and you receive an error message saying "Direct3DTexture::Load - The parameter is incorrect.". Has anyone else experienced this or know if there is potentially a hook or something that needs to be disabled that may be driving this error message?

Re: Controller not working

Posted: Sun Sep 20, 2020 3:04 am
by Ace Antilles
You aren't supposed to use other versions of ddraw with XWAU.
That's the whole point of the patch to update the correct one. Other versions are intended more for XW,TIE,XVT so it can't be guaranteed on how well they work.

You should use Jeremys latest one from here
https://github.com/JeremyAnsel/xwa_ddraw_d3d11/releases

Otherwise if you install the Effects from Blue Max then it will add the correct version to make the effects work.

Re: Controller not working

Posted: Tue Nov 03, 2020 8:46 pm
by GlyphTrick
wbrooks003 wrote:
Sat Sep 19, 2020 1:12 pm
Hello again - I did some further tinkering. I was able to launch the game directly through steam, versus through the xwingalliance launcher by changing the names of the .exe files. I also had to use the no_dinput hook in order to prevent the game from crashing to desktop when launching a mission. Steam's controller support allowed the game to recognize my xbox360 controller and provided basic flight support (a step in the right direction); however, what frustrates me about this is the way the throttle maps to the analog trigger axis and there does not seem to be a way to disable this.

The version of the ddraw.dll that Reimar had modified of the JeremyaFr version has the keyboard/mouse support (which was helpful for doing some heavy customization to my controls with the 360 controller with Joy2Key). It also has the ability to unmap the throttle from the analog triggers. When I use this version of the ddraw DLL on the new v1.6 patch 1.0 version of XWAUP, everything appears to work fine until you are about to launch the mission and you receive an error message saying "Direct3DTexture::Load - The parameter is incorrect.". Has anyone else experienced this or know if there is potentially a hook or something that needs to be disabled that may be driving this error message?
Were you able to unmap the throttle from the analog triggers? I encountered the same error, and since updated to the correct XWAUP ddraw.dll file so the game runs stable, but haven't been able to unmap the throttle with Reimar's ddraw.cfg file installed. Changing the JoystickEmul parameters hasn't yielded any change for me yet.