Voice Attack + Windows 10 + X55 Rhino HOTAS

[GG]

Wondering if anyone else is having the same problem, or has found a solution?

Prior to windows 10, I was running windows 7 and everything worked fine.  I upgraded to windows 10, and now Voice Attack does not recognize button presses on my HOTAS.  Or to be clear, it does not recognize any buttons other than Joystick 1 button 1.

I have tested this by trying to create a new command, and trying to assign a joystick button.  Nothing works, except joystick 1 button 1.

-The Saitek/Madcatz joystick software recognizes all button presses and axes.

-Games (Elite Dangerous) recognizes all joystick buttons and axes.

-Windows 10 joystick calibration does NOT recognize joystick button presses or axes.  The X-55 Rhino driver is still BETA and if I understand correctly, Windows 10 automatically downloads and installs the latest SIGNED driver on each boot-up.  Not that the beta driver works any better...

I am at a loss.  I have tried to google a solution, but I can't find anything that is specific to my setup.  All buttons work in game, but Voice attack does not.

Help!

GG

[MilchKuh Paula]

Hi GG,

I have the same Setting (X-55, Win10, ED) :)

So far all is running fine on my machine!
I'm not using the Beta-Drivers for the X-55.
A few days ago I had a similar issue while I was trying to write some AHK-Scripts for the X-55:
The Joystick worked well, but no button from the Throttle was recognized!
Even the Windows-Calibration-Setting wasn't displayed.
Replugging the Throttle doesn't helped either.
The MadCatz-Software had no problem - it showed me all buttons I pressed on the Throttle!

So I deinstalled all X-55 Devices (there were 3 of each) in the Device-Manager, unplugged the X-55 and restarted Windows.
After that I replugged the Joystick and the Throttle and all was working fine again: AHK (and Windows) could recognize the Throttle!

Perhaps this would work on your maschine, too?!

Regards,
MilchKuh Paula

[GG]

I have already followed the Saitek/Madcatz instructions to unplug joysticks,completely uninstall everything,  reboot, reinstall.

AHK = Auto Hot Key?  Does VoiceAttack work on your system?  I want to be sure before I go through the whole process all over again.  If you say you have a Rhino + VoiceAttack + Windows 10 all working, then I'll accept the problem is on my PC.

GG

[Damon Brodie]

I have X-55 + VA + Windows 10 64bit - all working on my end.  I have a fresh install of Windows 10 - not an upgrade.  All of this working with ED as well.

[MilchKuh Paula]

AHK = AutoHotKey, yes.
And yes, all works very well on my System.
Even the problem with Screensaver (and Monitor-Standby) not working when the HOTAS or a GamePad is connected has gone! I think that came with the november update from Win10.

With AHK I try to get rid of the MadCatz-Software for the X-55. For every button I created a "hotkey" in AHK that sends the assigned key to Elite.
This way I have more control what happens and I work around the fact, that you can only bind two keys/inputs to an action in Elite. As with Horizons I now also use a XBox360 Gamepad for driving around on planet surfaces, so for some functions in the Game I need 3 different Input-types: Key, HOTAS and Pad. ;)

[GG]

Just to be clear... Do you have a command that executes using a joystick button press, and it works?  Can you assign any joystick button to initiate a command?

I ask because my HOTAS works fine in Elite Dangerous.  It works fine with the Saitek software.  It doesn't work with Voice Attack.

GG

[Ed Jacobs]

I'm having this problem.

with my x55 rhino I want to open galactic map with switch SW1 on the hotas throttle block.  I can set it up in elite dangerous to do so, but cant find a way of making it work in voice attack.  TBH its doing my nut in.

[MilchKuh Paula]

You're right!

I can't assign Joystick Buttons to actions, too.

If I try to configure a button to an action, the status window doesn't recognize button presses either on the X-55 Stick or X-55 Throttle.

All other Software is fine (MadCatz-Software, Windows-Settings, AHK, ...)

I didn't realized that, because - as I mentioned earlier - I moved to capture buttons with AHK and mapped them to a keypress.

(I must definitely try if this works as intended. Haven't tried this in combination with VA)

Perhaps someone else has a solution to this (Gary?)...

MKP

[Gary]

I don't have a suggestion, other than to try the beta (I found some issues at some point that had to do with needing to refresh in certain cases).

Anybody else using this setup with success?  

Gary

[MilchKuh Paula]

The actual Beta (1.5.8.12) has the same problem.

VA doesn't recognize the push of any Joystickbutton from an X-55 HOTAS.

I'll do some further tests and report back...

MKP

[MilchKuh Paula]

Ok, did some tests here, too.

Now it's working: VA is recognizing the Buttons from the X-55! :)

I'm still not sure what exactly got it to work, as I have done more than one thing before testing it. It's because I have some other trouble (see my actual thread).

These were the things I did:

- set VA to default (under VA Options)

- restartet VA

- in the VA Options under "Joystick Options" (was disabled after reset), I added the X-55 Joystick and the X-55 Throttle again. The checkmark for "Enable Joystick X" appeared automatically.

After that I was able to assign Joystick-Buttons in profiles (or in the VA Options) again. :)

Hope it helps all you other guys with the same problem!

MKP

[GG]

Confirmed this fix works.

Reset VA to default.

Restart VA.

Re-assign joysticks (stick + throttle).

Now works.

Thanks!

[Gary]

Hmmm... very strange.  What's happening behind the scenes is VA is holding on to the device id that it is presented (you choose the device out of the list... each device has its own id, even if they are the same model).  When you clear the settings, you clear the device id (same as setting the stick to, 'unassigned' and disabled).  When VA runs it's asking DirectX for status on the device (extremely generic).  The only thing I can think of is that the device id was either changed or got munched somehow.  If I had to guess, I'd lean more toward ids got changed, as this is the same model of stick.  I have an Xbox 360 controller as stick 1, and an Xbox One controller as stick 2... VA has held on to their ids for some time.

Might have an X-55 in the house soon...  looks like you can get them for $199 at MyPilotStore.com.

Gary

[GG]

FYI,

I encountered the problem after upgrading from Windows 7 to Windows 10.  The device ID's could have gotten borked during the upgrade.

[Gary]

Ok... this is good to know.  Thank you!

Gary

[Femina Street]

I see this problem still exists with the Rhino x55 I can allocate the throttle but as soon as I try to test the stick VA stops working and crashes. Done all the reset stuff and so on perhaps I should take out the xbox controller and see if that stops the problem as if it is treating it as a joystick also there may be some interference as regards the id's.

[Gary]

Very weird that it would crash VoiceAttack, as VA is just asking the operating system what the status of your joysticks are (there are no hooks into anything).

Anybody else having this problem with the Rhino X55?