August 6, 2025Aug 6 Hi, I'm having a look at X-plane, both 11 and 12. My Saitek throttle is recognised. The problem is that I have a VKB Gladiator NXT Evo joystick that isn't recognised. I get this message as X-plane starts, then go into the configuration screen, get everything calibrated, and then save to a configuration profile. Everything apparently OK. But when X-plane gets to the cockpit, the joystick doesn't work. Yet if I go into configuration it shows all the axes set up correctly. The only similar problem I can find is at https://questions.x-plane.com/11333/saitek-controls-calibrate-unconfigured-joystick-appears, but I've tried the steps and references suggested. What on earth am I doing wrong? Many thanks
August 6, 2025Aug 6 After Calibration, have you set each of your axis to your joystick? For example, move the joystick up/down - in the axis you can see moving, set it to 'pitch' axis. Edited August 6, 2025Aug 6 by MrBitstFlyer CPU Ryzen 7800X 3D RAM 32GB Corsair VENGEANCE DDR5 6000MHz GPU GEFORCE RTX 4090 Monitor AOC AGON AG352UCG UltraWide G-Sync @ 3440x1440 Internal Storage 1TB NVMe PCIe SSD External Storage Three 4Tb HDs
August 6, 2025Aug 6 3 hours ago, Malcolm Street said: and then save to a configuration profile Do you also have this configuration profile assigned to the aircraft you are trying to use? Normally there is a "default" profile that is assigned to all aircraft initially. But you can make as many profiles as you want and assign them to different groups or even individual aircraft. This allows a high level of customization. So if your aircraft still have the "default" profile assigned, but you are setting up and saving to a different profile (that is possibly not assigned to any aircraft), your configuration efforts won´t show when you try them out.
August 6, 2025Aug 6 Best thing to do is set up the default profile and calibrate your devices, than modify that profile and save as a different one for specific planes.
August 7, 2025Aug 7 Author Thanks for your replies - yes, I hadn't noticed that I had to assign the axis to a function via a drop down menu. Now working fine!
Create an account or sign in to comment