Joystick Hats not recognized

[vinkrogel]

Hi guys--

I bought VA for Elite Dangerous VR.  I enabled Joystick + POV Hats, but when I go to test, they don't get detected.  However, the buttons on the base of the Joystick do get detected.  I am using dual Thrustmaster 16000m sticks with the TARGET software.  Any help would be greatly appreciated.

[Gary]

Hi, there.

If your joystick is emitting its POV hats to the system as POV hats, they should be picked up (it's a very generic system).  Make sure that your software is presenting your POV hats properly.  Also, you'll want to make sure all your drivers are up to date.  Unfortunately, I don't have this stick, but I know others do - hoping they'll come by soon to offer some insight.


Anybody else out there using Thrustmaster 16000m sticks that may be able to lend a hand to vinkrogel?

[vinkrogel]

Thanks.  All drivers are up to date, and the hats work fine in game. 

It may have something to do with the TARGET software that maps the two sticks to a single virtual/root joystick.  I should be able to try the sticks without the TARGET software to confirm that theory. 

Is anyone else here using dual T16000m sticks?

[vinkrogel]

Just a quick update -- same thing with or without TARGET running.  Hats work in-game, but not detected in VA.  I've tried just about everything I can think of, including drivers, reinstalling, etc.  If any stick users have any other ideas or ways to further debug, it would be greatly appreciated.

[Pfeil]

What does this combined device look like? If you type "Set up USB game controllers" into the start menu, it should bring up the list of joysticks; Which controls does it show for the combined device?

Is the combined device assigned to Joystick 1 in VoiceAttack?

Did you try checking "Enable Joystick 1 POV Hat Switches" and setting "POV 1 Switches", "POV 2 Switches", "POV 3 Switches", and "POV 4 Switches" to 8?


The "Test Joystick Buttons" window does not respond to either POV hat?


When trying without the software, was one 16000m assigned to Joystick 1 in VoiceAttack, with the "Enable Joystick 1 POV Hat Switches option checked, and the "POV 1 Switches" option set to "8", and the other 16000m assigned to Joystick 2 in VoiceAttack, with the "Enable Joystick 1 POV Hat Switches option checked, and the "POV 1 Switches" option set to "8"?

I.E. without using the combined device.


You could have a look at this, though as it's apparently working ingame the config is likely already correct:

Apparently it's not quite straightforward how to configure combined devices, perhaps this may prove useful.

[vinkrogel]

The window shows "Thrustmaster Virtual Game Controller (root)" when running TARGET, and two entries of "Thrustmaster T16000m FCS" when not running TARGET. 

I have assigned it to Joystick 1, enabled hats, and checked the POV Switches to 8 down the line.  The test window is not responding to the hats (or currently anything at all - it was responding to buttons earlier).  Everything still works in game.

One thing I failed to mention is that VA is crashing about 1/3 of the time when messing with Joystick stuff.  Disabling this at VA startup works, but then obviously I can't use Joysticks.  This is why I tried a full reinstall.  I did notice a
I did notice a VoiceAttackFault.txt file in the VA install directory with the following stack trace:

Code: [Select]

SharpDX.SharpDXException: HRESULT: [0x80070006], Module: [General], ApiCode: [E_HANDLE/Invalid handle], Message: The handle is invalid.

   at SharpDX.Result.CheckError()
   at SharpDX.DirectInput.Device.SetCooperativeLevel(IntPtr arg0, CooperativeLevel arg1)
   at VAJS.VAJS.
(Guid , Int32 )
   at VAJS.VAJS.()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

[Gary]

Thank you for the info.  VoiceAttack's interface to DirectInput (DirectX) is a simple polling mechanism - that is, when it's turned on, it is using components to query the state of what Windows is reporting.  If you've reinstalled VoiceAttack fully (that is, uninstalled and verified that all components have been removed) and then installed again, there is going to be a component somewhere on your system that is out of sorts.  You're going to want to try running a system file scan to see if something can be found readily:
https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker

You also may try uninstalling and reinstalling your joystick drivers as well.

Does running dxdiag.exe from your command prompt yield anything under input?


If none of this works, you've got a unique situation that I've not yet encountered with VoiceAttack, thus, will not be able to offer a solution or workaround until more users can present some type of pattern that can be reproduced, unfortunately