prato_1994

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.

Thanks! I’m asking for something that should be equivalent to avoid the blue highlights in “Lock” cockpit interaction mode in 2D, because in VR it’s like the only interaction mode available it’s “Lock”, instead of “Legacy” mode that naturally don’t have the blue highlight.

Is there any way to remove the blue highlight from the buttons in VR when I’m pointing with the controller? It’s really annoying, and the trick of switching the cockpit interaction mode to "legacy" only works in 2D. I was able to fix it on the iniA350 by editing an XML file, but I can't find anything similar for the A380.

MSFS 2024 SU4 Oficial, latest aircraft version and this issue still there, making the aircraft unflyable in VR. I paid for this airplane, please fix it, we have a year with this issue. Thanks