Perhaps the smoking gun that this is on Asobo's side is the problem doesn't exist in flatscreen... Asobo made changes to object culling in SU5 and perhaps that affects mipmapping too. This was almost certainly motivated by PSVR2 on PS5 - and thus could explain the difference between flatscreen and VR. The problem with complaining to Asobo is they'll most likely kneejerk blame it on the third party aircraft and I haven't seen it in first-party aircraft so it'll just get deflected back. I have seen this exact behavior in one other aircraft: Taogs Hangar A365. One panel behaves exactly the same as what I see with the A/S indicator in the Baron; it's one or two mipmap levels lower than the rest of the cockpit, in VR only. I'm hoping they'll dig into it and find something that points a finger at something. Note: aircraft are downloaded so it's not a streaming issue, rolling cache reset - just in case, dynamic settings off, foveated rendering off, off-screen terrain caching set to ultra - just in case.

On the plane irl, it is the same

@knollo thanks a lot, works as intended!

Thank you very much

Great idea!

@Lerno1 Oh ok, I misunderstood, I thought you were talking about the FPL equipment list Then, I don't know either. I'm surprised that it was not RVSM approved in US. Bunch of old aircraft of this era are approved (ERJ-145 for exemple).

Thanks, I just couldn’t remember if the INIT page was accessible. Anyway, my subsequent flight in the F100 had no spurious AFCAS messages.

I.. hmm. I was like 99% sure I was in Normal mode, but I did take screenshots... and I was indeed in V2 mode. So chalk this one up to operator error.

Nice workaround, it worked. Thanks so much

Hi Mark, thank you very much for your lengthy and detailed response. I do believe that the F28 is a fantastic addon and i am not at all disappointed by it. Quite the contrary. I am a huge fan of it hence i am worried whether the product will keep receiving updates even with the new products coming in and overshadowing the older ones. To some of the issues which i raised concern to, as you say that they are not logged in your internal tracker, should i do that through the support by raising a ticket? Or are you suggesting the issues are not present hence they arent logged, or is it the first you hear of this and thats why they arent logged? Im just wondering as what to do. Kind regards, Leon

Same thing also happens on takeoff, the call "thrust set" is already heard about 0.2 EPR below target TO thrust (about 1-2 seconds early).