Can someone try this, this fix for me, input your flightplan direct to fmc, dont build/export a flight plan, just input directly onto your aircraft.
VHHH to Elato in the A320 is a short flight and I didnāt see any problem on SU8 beta. Enable a fps limiter if you are having choppy gameplay.
āRebootingā the sim didnāt do anything on my side. Actually multiple times did nothing. But deleting cache and re-building it, did work. Thatās my take. May not be true with other systems, but true with mine.
1 Like
Whatever gets you flying.
1 Like
Does anybody else suffer from these extreme stutters while on final/taking off? Itās basically unplayable because every stutter freezes the control inputs, making the plane uncontrollable.
3 Likes
āafter playing a few hoursā or in each case ?
If after some hours just scroll up and read 
If in each case , then check the LOD setting and better search in topics about "poor fps on ground / final " ( example )
1 Like
Just did my second flight today without performance loss or CTD 
Seems like locking fps to 30 in msfs AND disabling AI live traffic did the trick for me.
Side Note: also saw my first thunder storm since half a year today so maybe they fixed something in the backend and applied some server side patches?
EGLL/YSSY Trip Report 19.5 Hours
Plugged the trip in VFR direct from the main page with the plan to use 3D, set the autopilot after TO and have some performance monitors running.
Departing London, in 3D with FPS @ 42, it dropped immediately to 13. Photogrammetry can be difficult in certain areas and London is one of them. This is what the Windows Event Viewer was flagging during the brief drop and may speak to the audio popping some have reported
.
Getting away from London the FPS rose to 48. Leveling at FL 350, I switched to 2D mode (FPS 150), turned off WMR portal and resized the MSFS window to add performance / hardware monitors on the screen.
The flight was uneventful until checking status at 12 hours. FPS had dropped from 140-150ish to this
And from the Event Viewer
After seeing hardware and resource utilization looking normal, the COM warning made me suspect of the Photogrammetry issues with FPS and decided to turn it off. The jet was over water at the time.
Two hours later and coming up on land, things had improved a bit
FPS continued to improve driving across AU with the approach to Sidney looking like this
My impressions are;
The physical memory and paging are solid
Photogrammetry data handling has an impact on FPS / sim cache / manipulators
Iām tempted to bump the Manual cache up
The sim has a big wad to chew
I wonāt do this again. Iāll teleport.
I donāt really see any advantage to using the manual cache at all. In other words, the effort required in setting up manual cache does not seem worth the benefit, if there is any benefit. I can imagine it having some use for people with a slow internet connection, or people who fly in the same places often, but I do not.
it is the useless Windows stuff ( Log ) which you can see since yearsā¦ have nothing todo with msfs and you can ignore these 10016 eventsā¦
I deferred from using the sim Rolling Cache some time ago. I use the simās Manual cache option.
Simple events happening at the time the FPS plummeted.
these events happens allways, as also allways runs tons of processes in parallel. MS itself describe to ignore that stuff 
You use the simās manual cache option and have a FPS drop from 140-150ish to 48. Not that the manual cache has anything to do with the FPS drop, but how could you ābump up the manual cacheā enough to cover a 19.5 hour flight? Feel free to ignore my question if you think it is getting beyond the scope of this topic.
The Long Haul trip report was simply a exercise of data collection and putting my well oiled PC up to the task for this thread subject. Iād say it was mostly a successful trip. With AU just reopening their borders, my being tired of being cooped up, Iām headed for the Gold Coast next week for some relaxation from snowblowers and other irritable stuff. Cheers and try to have fun. Itās just a game.
1 Like
Hi, i donāt know about your PC performance. I have 2x 2080 GTX,128 gig ram & CPU up to 5 gig liquid,cooled with amoniak,my display is a 4k 65 inch (162x74 cm)". With large planes,the best you can do is reduce the rendering scale to 250 and the deph of field to"high". Large jets approche faster to the airport than small planes such as a Cessnaās and same category. Is the plane in your video a"A NEO" or āFBW(LEAP)ā? Before take of i test with a fast freelook sweep from left to right with the mouse,if i have no stutteringā¦ itās OK. I hope have help you.
2 Likes
PC: I have had consistent fps drop-off on long flights too. For example, today I was flying the Longitude from Teterboro. NY to Tamp Executive, FL. FPS started off at 55-60. About halfway to the destination, I noticed my FPS had dropped off to between 25-30. This was about 2 hrs. into the flight. Auto weather, flying 200 AGL, 200 Kts. On a hunch I saved the flight, shut down the sim, and re-opened the sim to the saved flight; same conditions. FPS was now back to what I started off with (55+) and stayed there until touchdown. PC- AMD Ryzen 5 2600, AMD RX 580 w/ 4Gb ram, 24Gb system ram. MS Store. During 55-60 FPS, GPU was 90-100%, 80 deg. C., 3,200 Gb GPU Ram in use out of 4Gb; 8 Gb sys. ram in use out of 24Gb. At 25-30 FPS all usages and heat were darned near identical. I expected to see Ram usage as much higher, but this was not the case.
1 Like
I am also seeing this which I have documented here if you can see it.
I have tested with default a320, no mods (except two freeware Airport mods) and I lose approx 20 fps over a 90 min flight from Bergen to Bodo, a flight with no PG and along the coast of Norway, so not complex scenery by any stretch of the imagination.
It really sucks and Iāve spend days tweaking settings and testing to try to resolve or improve the situation.
2 Likes
There is also mention in the SU8 Beta release notes, that this is āfixedā in SU8, but so far, I see no signs of any improvement when running the latest SU8 Beta ā¦
BTW: So easy to call ANYTHING fixed, if you do not give any information of what was causing the issue, or what was done to fix it ā AND, it still appears NOT to be fixed !
As a beta tester, have you talked to other beta testers and have you gotten together to let them know your findings? If so what was their answer. If not, why be a beta tester?