FBW bus is eating frames after a while ....

[CptBayer]

Hi developer team,

EDIT: I found that known issue on your discord page !! But please take a look on my first question down the bottom!.

.... did a leg with experimental ... same results like development mode .. becomes unflyable after 1 hour ....

since a longer time I regognize issues when flying longer legs with the FBW bus. What do I want to tell?! Most of the time I fly legs over 3 hours. After round about 1 hour, there is a mysterious frame drop and stutterimg starts and will not end. And the longer the flight the worser the stutter party. When I am on final I have a frame drop of more the 65 %. You can see it in the following pictures.

There is just another thing to tell. I am using a hardware MCDU and I always dock the MCDU window of and move this to the screen of the hardware MCDU (this caus frame drops up to 30%, but only with the GBW bus!). I alsways thought, that this is a problem of Asobo and another failed update of them. To check this I did two similar legs. One with the FBW bus and the same leg with the original Asobo bus (ZSPD - VVTS). In both flights I started with the above explained docked of window for the MCDU.

Starting with the FBW bus:

1.) NO screenshot. During takeoff I think normal frame drop down to 24 fps (from locked 30) due to scenery. During climb frames will be back to my locked 30 fps, cause I guess the airport scenery is not anylonger "insight".

2.) NO screenshot. After 1 hour frame drop and oscilating of the frames starts. Till this point of flight, there are normaly constant 30 fps .
3.) After 3 1/2 hours during descent, nothing changes. The frames are going up to 30 but the high peaks in general and the GTUI thread becoming crazy and causes a huge amount of stuttering. Remember, at this stage the docked of window is closed, cause otherwise I only had about 20 frames.

4:.) During final approach bombastic frame drop nearly impossible to fly .. Without docked off window for the MCDU, too!

Same leg with Asobos bus:

1.) Smooth flight during climb. Nearly no stuttering. Remember second docked off window also in use with the hardware MCDU.

2.) After 2 1/2 hours flight. Everything is still smooth. Docked off window is active.

2a.) after 3,5 hours during descent .... still smooth ... flying over landside ..

2b.) 25 miles out of VVTS. Running smooth with docked of window for hardware MCDU.

3.) Picture during final approach will follow in about 1 hour (left leg time :-P). here we go. Nearly same position than pic 4 above. Smooth. also when turning head to take out a look on captains left window (I am using a trackir 5).

So, there are two questions I have.

A:) Why does the docked of window for the hardware MCDU eats so much frames? Remember, with the Asobo bus, no frame drop with docked off window.

B:) Have you any idea, why the issue with the crazy stuttering will happen after round about 1 hour flightime? I am flying the FBW bus for a very long time and I remember, that there were times without this problems during long flights. For me it seems that a kind of running full of memory phasis will be active. When looking in my task manager, it seems there is no bottleneck. I am using a strong system with a rtx 3090, AMD Ryzen 7 3800 XT, M2 drive, Asus Rog strix 570-e and a good RAM with a value of 32 gig.

Greets Klaus