Wizzo - Joystick not found please check the connection

[Daegarn]

Hello,

I just received my Gladiator MkII and It's working in games like Star Citizen, and the joy tester and button tester everything is working. When I launch the wizzo software I get an error though, joystick not found, please check the connection. I'd like to change some settings on it.



Anyone know what I can do?

Thanks.

[AeroGator]

1 - Try launching Wizzo as admin. This might work.
2 - Please read this howto: http://forum.vkb-sim.pro/viewtopic.php?f=25&t=2762 and follow all relevant directions (1, 2, 5, 6, 7).

[Daegarn]

1 - Device model and version: VKB SIM Gladiator MKII
2 - Controller Firmware version

5 - If VKB original software is used, please always mention its version
WIZZO: V.0.88
Vkbdevcfg-c: v0.81.83
6 - Vkbjoytester screenshots. Download it here: http://ftp.vkb-sim.pro/Programms/VKB_JoyTester.zip

7 - Vkbdevcfg-c screenshots.



Running as admin did not fix the issue.

[AeroGator]

Let me guess, you must be having a gamer's mouse or keyboard (or both).
Saying gamer's I mean anything that is more than "just a" mouse or kb. Anything with additional functions.
Those "enhanced" or "advanced" devices tend to have their own set of drivers that when in use would intercept any other pointing devices and grab them and pull under their command.
This does not prevent you from using your joystick playing but does prevent it from being recognized by Wizzo.
What you need to do is simply disable the "enhanced" devices, run Wizzo to configure your joystick, then re-enable whatever you have, reboot if necessary, and voila.

You may run this utility http://ftp.vkb-sim.pro/Programms/show_hid.rar to check which application tries to take over the game device.

[Daegarn]

Interesting stuff!

Thanks for your replies so far, I'll try that with a couple of my devices.



How can I see here which application is taking over the Gladiator?

[AeroGator]

We know this guy, the owner of the mice business. He's a great guy, and his mice are great mice, but he is a damn maniac, and always tries to squeeze crazy solutions into his mice' firmware. (but once again, his mice are great).
There is no way but trying and erring; disable first the mouse, then the kb, then both, and you will see which one was the culprit.
Don't forget to reboot every time you disable a device.
ATTENTION: you don't have to disable the physical device.
I mean, disable its advanced features, turn it into a simple Windows pointing device by temporarily disabling its proprietary software.
Then reboot, set up your joystick, and see how it goes.