I imagine it’s an option, but not one that’s been simulated at present.
Recommendation to disable X-RAAS completely for the CL-650 applies to everyone.
That should work. Insofar as the livery should be saved in Airframe Manager at least. Can check if it’s getting saved by looking at the airframes.db file.
However if you don’t match the livery in the X-Plane interface when loading a flight, if you then subsequently reload or reposition then X-Plane will change the livery back to what it thinks it should be. Best to always keep them in sync.
Could you possible install a second copy of XP and run this test again without any extra plugins or scenery, please? The log is very full and hard to debug. The installers from Laminar and X-Aviation allow a second copy.
I understand, I’m just explaining why they’re different; one is LR logic, one is Toto logic. If a change is going to made it’ll likely be made to every knob that uses the latter, so will need to be considered with care.
Read closely you’ll see IVAO clients are not supported as there is no way to determine whether one is connected to the network or not. Once the authors of the clients provide this mechanism then we will look into supporting it.
You are the only one to report this issue, unfortunately for you. I’m sorry it’s happening.
Can you provide screenshots of the Plugin Admin window, the tab with the pie chart, for steady state vs. the “stutter”, please?
No, I think “developers” in this context are the X-Plane developers; the response is being written from the point of view of the technical support person. They still provide no actual reason to think it’s Hot Start’s code, they just don’t want to deal with their own bugs. Plus Librain is not part of the addon at this time.
Default commands? They have their own behaviour.
Mouse wheel acceleration is tuned per knob at least. Setting minimums should be quicker in the next update.