2 hours ago2 hr I've been investigating quite a lot of scenarios after installing the 1.0.1. I made sure I delete the ThrottleData.ini file, and tested in non-VR as well.While in non-VR - everything works OK.In VR (Pimax crystal light) - after a minute or so, any movement of the throttle through binding to a hardware (tested with multiple hardware units) causes an immediate CTD. To test I created an empty Honeycomb profile and only did a bind to throttle 1 axis. Works OK out of VR but once I switch to VR and I touch the throttle - I get CTD. 100% of the times. The A380 worked great for me prior to 1.0.1.Just to add - I crossed-checked with other aircrafts and the throttle binding in VR works OK. This is something that probably related to the V1.0.1, I believe some throttle code was changed?Issue confirmed on my end - controlling the throttle with keyboard/mouse in VR works OK. Once I bind it to ANY controller and try to move it - I get an immediate CTD. Ini team, can you please please look at this? Other than that it was a GREAT plane to fly (also in V1.0.0) so please examine the new throttle binding code to resolve this.
Create an account or sign in to comment