This is my first post here and I could really use your help! I have recently purchased a new PC, which has an i9 14900KF, paired with an RTX 4080 Super and 64Gb of RAM. My display is an Alienware 34in ultra widescreen OLED monitor. I previously used an old PC with an 15 4690k and a GTX 1070, which I ran at 30fps locked, on a 1080p monitor. Initially on my new system I was getting 84fps steady with the A2A Comanche over my test airfield which is Launceston in Tasmania. I could also get this over Auckland in NZ. I have enabled FG also. Suddenly I was getting 55-62fps in a kind of āpulsingā regular drop. I ran MemTest and there were 233 faults, so the RAM was replaced and MemTest was passed. The PC was given a clean bill of health by Scan, who built it. When I reinstalled MSFS, I once again got low 80ās fps for about a week and now the same fps drop has occured, with also occasional, erratic severe ghosting. Could the GPU be an issue? Would really appreciate anybodyās thoughts on this. Have attached an image to show the fps details.
Thank you for replying and your suggestions. The PC has a 1000w PSU and was working perfectly until the FPS drop issue. I lowered the global settings to Low from Ultra, but the issue continued. MSFS configured itself to Ultra when I first started it up. Itās not only that the FPS have dropped from what was a stable high fps system for over a week, itās that the drop literally happened overnight and along with the regular fps drops, the scenery has a ārubber bandā effect where it speeds up and slows down in time with the yellow areas on the fps counter. My broadband is 100Mb/s and my PC receives approx 90Mb/s when running. I only run the A2A Comanche and the BAe 146 at the moment, which before the issue could both achieve over 80fps over Auckland and Wellington, NZ. Temps are also not an issue. I only run SPADnext and TrackIR in the background. Itās so random. I am baffled.
Hopefully someone else will chime in here soon and give you a few more ideas
1000w will be fine for your PC as long as it is a decent quality make. Your broadband speed is also more than adequate. The A2A Comanche is also pretty well optimised too from memory (not simed in it for about 3 months though) so there shouldnāt be any problems there either.
Out of ideas myself at the moment.
Best of luck. If I think of anything else āIāll be backā. Please keep us posted
No worries. I have the latest version as I installed it after SU 15 and there was a little update after that. I canāt understand why one minute I have 84fps and smooth flights and the next, this weird fluctuating issue. MemTest is finishing in a bit, so I will look at maybe swapping out the GPU for my old 1070, to see if the fps, although lower, will stay at a relatively constant rate.
This is a problem created by latest game version. I can see many issues in forum related to a significant performance degradation. IĀ“m in the same boat as you, getting similar figures even if I have an i9-12900ks + 4090 card. I was on 80fps on ground with FG and now IĀ“m around 50-60fps, which means raw fps are only 25-30. Once I climb I canĀ“t barely hit 80fps, while before I could even hit 100fps.
When I monitor my CPU usage itĀ“s a rollercoaster, while in the past it showed a steady and consistent curve. This clearly indicates that something is wrong at main thread level. I have seen the exact CPU graph behaviour in the past with many other SUs since avionics updates appeared, which is the reason of all our current periodic freezings, hangs and performance degradations, as they were not existing before.
The āstableā updates are always showing steady CPU usage while the ones where they experimented with new magic solutions to squeeze software beyond its limits so that console version can handle the new workload, are always rollercoasters. Unfortunatelly I have learnt after 4 years that such things wonĀ“t be fixed for several months.
The main problem devolopers donĀ“t want to understand is that to save a relatively small amount of RAM, so that console and lower end systems can have more memory available, you need to keep main thread busy for longer periods of time and more frequently, and dump again a big amount of data which would be faster accessed if it had stayed in RAM as it did in the past. ThatĀ“s why this solution, even if it aparently looks fine from a technical perspective, will never work well, will always produce degraded performance and side effects such as those mini freezes we have seen during past months and will always require to lower previous quality to keep balance below the limits as soon as you increase a bit the main thread workload. I can honestly understand their wish to improve the situation by using this method but it would be better to forget it and go back to the older methods that produced much better results.
Unfortunatelly this optimization method is applied indiscriminately, so even high end systems like ours, which do not need at all such memory optimization as they still have plenty of unused resources, have to live with it.
Thank you for the explanation. I just canāt understand how I had 84 fps last Thursday after the updates, and like you say, a rollercoaster of CPU usage now. And this has happened twice now. I just canāt sim with it like this, so will park the MSFS till (if) it is sorted. I bought a new PC after using my old one for a decade so I wouldnāt have to deal with poor performance, but there you go. I have read that a W11 reset can help, but a whole day to install everything after I did that just last week, is something I want to avoid.
Avoid that. It will just put you at the same situation you are now I also did fresh installs in the past and they donĀ“t solve anything at all. The problem exists at MSFS code level and it will still stay there afterwards as well. This is one of those updates that will ruin our summer holidays IĀ“m afraid, so itĀ“s better to play other games until this is fixed.
Youāre probably right. I feel like the sim is hitting some weird barrier where it works for four days, even after SU15, then suddenly gets laggy and stuttery.
I started the sim after clicking on Repair and Verify files. The issue remains, however I have noticed that my PC makes a metallic ābuzzingā noise that corresponds exactly with the drop in fps every two seconds. I wonder if my GPU has an issue as I am experiencing the same symptoms as before the RAM was replaced?
Quick update. I read a post by Chewwy that removing everything from the Community folder would be a good thing to try. I did so and I have a constant fps back. The frames are lower, but this is being reported by quite a few people since SU15 and CU7.
My Community folder had these items:
NZA sceneries
Flightbeam NZ sceneries
A2A Comanche
JF BAe 146
Navigraph hub and toolbar widget
REX Accuseason
I have put everything bar the BAe 146 (which has an update) and Navigraph assets back and all is okay. The Accuseason trees and weather presets will not show in the sim despite being visible in the Community folder, but thatās another issue! Will add the Navigraph apps and the updated 146 later this evening and will report back. Hope this helps somebody. Just glad itās not a fault with my PC.
Did you ever fix it? Mines has just started doing this I have changed settings, even reinstalled it nothing is working for me at all and its driving me nutts!
I gained about 7-10fps back after the last update, but nothing like as good as it was when I first got my new PC. I have read about folks getting amazing fps with 4K, but that is a dream for me. Iāve given up now and am waiting for MSFS 2024. I have too many other hobbies/activities that I like to spend time with, so I donāt have the time to mess about with it at the mo.
I have the latest version as I installed it after SU 15 and there was a little update after that. I canāt understand why one minute I have 84fps and smooth flights and the next, this weird fluctuating issue. MemTest is finishing in a bit, so I will look at maybe swapping out the GPU for my old 1070, to see if the fps, although lower, will stay at a relatively constant rate.
I also did fresh installs in the past and they donĀ“t solve anything at all. The problem exists at MSFS code level and it will still stay there afterwards as well. This is one of those updates that will ruin our summer holidays IĀ“m afraid, so itĀ“s better to play other games until this is fixed.