Spooky Mulder

I'm getting this same issue on Syria at present. Any target with a building as backdrop is effectively invisible to Petrovitch. nullIt's admittedly crude but I include an image of the target area of a (botched) attack run here, from the rough direction of the attack run. Targets on the road or in more open spaces (green)were easily acquired and engaged by Petro. Ones which had buildings behind them, even if not particularly close (in red, that BMP-1 on the right strikes me as a particularly bad example) were not targetable, even at very close range. Somewhat disappointingly, I tried to reproduce this to generate a short .trk - but was unable to. I've had this happen twice over the course of this week in multiplayer, but it works fine in singleplayer, apparently. I don't know if any of that is helpful, but I really hope so, it's been a bit of a drag.

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)