Spooky Mulder

I've had the issue a good bit over the past year with my Winwing Orion 1. Something about the Orions seems to initially sync with the F1 oddly in such a way that the throttle is imperceptibly past the cutoff. But enough to allow excess fuel to enter the engine and then fire. The best, safest way to mitigate this issue is to perform the following: There's other things I have noticed stopping the issue but this one seems to have a 100% success rate. Very strange. No idea why this happens with the F1 and seemingly no other aircraft.

Experienced this today. As far as I can tell it was because I was connected and desynced off the probe on an MP server. After this Jester would not stop talking with corrections and I had to mute him altogether.

This is all very minor, I know, but I thought I ought to report it because I haven't seen it anywhere else. Below: Mirage F1EE accelerometer. The "negative G/lowest G" indicator (forgive me if this is incorrect terminology) cannot be reset to 1 G, it remains fixed at -1 g unless you go below this value at some point during flight. Below: F1CE accelerometer. When pressing reset, it correctly sets that indicator to 1g. Both max and minimum indicators coalesce to within the "current acceleration" indicator. The difference in behaviour is the same for me between SP/MP and single threaded/multithreaded. Cheers, Spooky Mulder (EDIT: Ding dangit, I thought this was the bugs section... I need more coffee. Apologies all)