I've been using neXt for a few months with my USB connected Taranis X9D+ and the application just recently stopped seeing the Joystick Device for some reason. At first I suspected the latest Application update, so I reverted to 1.585 with no success. Then I tried reinstalling the FrSKY Driver, no success. I tried a different X9D+, nope. I tried different cables, nope. I tried a different computer, nope.
At this point I suspect that the latest version of Windows 10 on all my computers is the problem, but I'm not sure, and I have no idea what to do next to try to fix this.
switch on your Taranis and connect then the Taranis with the USB cable to the computer.
This is the change log of FrSky: massstorage option has been removed. When plugin the radio to USB, you have a choice between accessing SDcard or using the radio as a joystick (choice can also be setup in radio settings)
Or you change the presets of your Taranis from mass storage (SD) to usb joystick (HID)
Thank you so much for your response, I sure do wish the solution were that quick and easy.
I always select USB Joystick (HID) when connecting the Taranis to the computer when using neXt. The only time I select USB Storage (SD) is when I'm interacting with Open TX Companion.
can not you see the Taranis as a joystick input device in Windows Hardware Manager? If it is not there, the problem is probably the Windows driver.
Remove all other USB joystick devices. And take a look at what you have recently installed. This may be blocked by a security program or other hardware.
Yes, I can see "FrSky Taranis Joystick" in "Windows 10", "Settings" > "Bluetooth & other devices" when I plug in the Taranis. It is the only USB Joystick Device connected. I also see "FrSky Taranis Joystick" in "Devices and Printers". When I open the "FrSky Taranis Joystick" Device Properties, it says "This device is working properly", and has a Description of "BETTER_USB_HS". As I mentioned previously, I have Deleted, and Reinstalled the Driver with no difference.
Is there any kind of debug mode, command line args, or something like that in neXt that'll enable me to see/pick Devices in the neXt Application? It's just not picking up the Device for some reason.
Please review my original post for a list of things I've already tried.
Sounds curious. I have the same Windows build installed and everything is working well.
Please open the menu and go to Settings > Input Device. There is the Input Monitor window. The raw data and, if available, the names of joystick # 1 and joystick # 2 are shown in this window.
No input device was detected when "- No Input Device x -" is shown.
What do you see there?
What happens when you start the neXt and then plug in your Taranis?
I can compile a 64bit version ... maybe that makes a difference in your case.
What happens when you connect an Joypad to your computer? For example an Xbox Controller. Is this working then?
Have you installed any security software?
What happens when you rename the neXt folder in your documents folder? When you rename it, the simulator is running without any old setups. If there is no difference, you can delete the new neXt folder in your documents folder and rename the old back to 'neXt'.
I tried an Xbox 360 controller, Windows sees it and says it's working properly but doesn't show up in neXt... same results as Taranis.
Renamed neXt folder in Documents folder... same results, didn't work.
I have no added security/virus software, just what's built into Window 10 (which I haven't messed with).
Not sure if 64bit build would make a difference, but I suppose it's worth a try. If 64bit build works, I will be amazed that more people aren't have this problem... but, I guess with this problem being so consistent for me, I'm already amazed that no one else is having the same problem.
Then your Taranis drivers are not the problem. And I think a 64-bit build can not solve the problem either. I tested this on some computers with the same Windows build and had no problems. There are no other customers with this problem. There is another problem because the Xbox controller is not working.
Where is the installation directory of the simulator? Please uninstall the simulator and rename the neXt folder in your Documents folder. Then reinstall the simulator and do not change the installation folder. Default is programs x86/neXt. And of course you should always do this as a normal user with administrator privileges.
Thanks very much once again for your effort with this problem!
I tried everything you suggested, and many iterations of variations there of with no success. I finally found a how to that led me into the Devices and Printers > Right click on the "FrSky Taranis Joystick" Device > select "Game controller setting", and there it was (or should I say wasn't)... no Controller in the "Installed game controllers" pane (please see attached screenshots).
I get this same result on 4 of my computers, using 2 different Taranis X9d, and 1 FrSky X-Light.
Definitely; 1) A Windows problem, 2) that can't be fixed by reinstalling the Driver, 3) that isn't happening wherever you are... I'm in USA btw.
I have no idea what to do now, but thanks again Klaus for all your help.
Sorry for the small screenshots, they were bigger before I uploaded them.
this looks like a strange Windows error. I think it has nothing to do with the Taranis drivers because the Xbox 360 controller does not work on your system either.
Do you use the cloud desktop? Maybe this causes the problem.
I found some links in Google. Some of them recommend installing more tools ... Please do not install any other tools and try to fix this with built-in Windows features.
and this: 'Run the Hardware and Devices troubleshooter: An unrecognized gamepad on Windows 10 could arise due to conflicting drivers. To fix the problem, reboot the computer and plug in the gamepad. Now run Hardware and Devices troubleshooter, by doing the following: Press Windows Key + I to open the Settings app.'
So this is a huge Windows 10 Driver problem, that isn't fixed by reinstalling the driver, I fixed it by following the direction from the DRL Sim link above, and rolled back to the previous Driver installation and BAM!!!... I have my favorite SIM back... neXt of course ;)
