Very Low performance on a breand new PC

msfs-2024 Good evening, everyone. In July, I decided to treat myself to a new desktop computer, since I had been using a laptop for years. These are the specifications:

With those settings:

UserCfg.txt (3.9 KB)

I’m getting this result:

currently flying on a PMDG 777. But same with the inibuild A350.

Can someone help me to sort out this mess? I really can’t get out of it… thank you in advance. Mirko.

Check in the BIOS under memory that XMP is enabled

1 Like

Your download speed 6 Mbps is quite low — if the sim is tryinng to stream world data and the connection is slow, it can also stall the main thread

Thank you for the insight. I’ve moved the XMP profile from 1 to 3 and enable the CPU gaming boost.. Regarding the download speed I guess is because I was flying at FL390. On ground at the moment I have

Let’s see during the flight. Thx for the moment

1 Like

@Mondin1995 you appear to have 96GB of RAM. How is that arranged? How many DIMMs, how big are each of them, what max speed are they supposed to run at?

If it’s 2x48GB and your motherboard is rated to run them at XMP speed then that’s probably fine, but few boards will run more than 2 DIMMs at the max speed for DDR5. And if the modules you have are not tested with the board and on the QVL, you may get poor results.

That said, I’d expect RAM problems to manifest as CTDs, not low FPS. And your first graph shows 12FPS with a main thread time of 75ms, but you say you were cruising at FL390. I’ve only ever seen main thread times that high when I’ve been on the ground with MANY other players in a group flight, and it’s specifically the number of aircraft models being rendered that causes the main thread spike. Literally nothing else does that for me. I also see your manipulator and CoherentGT thread times are very high, despite the CoherentGTDraw thread being completely idle. That’s odd.

Are you using multiple displays? Do you have instruments popped out? Are you using Nvidia App or Control Panel? Are you setting any kind of frame cap in either?

@TwinMuffin81832 talked about download speed - what’s your actual connection speed? Is the sim using 6Mbps because that’s all it needs, or because that’s all you have available?

What are your sim graphics settings? Do you have VRR, and if so which kind, or are you running with vsync on and if so, what % of the monitor frequency? Your hardware info suggests you’re running your display at 99Hz, which is not something I’ve ever encountered before. 120Hz, sure, but 99? Hence the VRR question.

FrameGen? If yes, which kind? DLSS? If so, what settings?

Something’s not right here, that’s for sure. With those specs, away from the ground and nearby player traffic, you should be seeing much better performance and your main thread times should be <15ms.

2 Likes

That’s looking more normal. It’s a CyberpowerPC build, correct? Congrats on that new rig!
XMP 3 is the least aggressive, most stable setting. XMP 1 is the most aggressive, least stable setting. I have mine set at level 2, fyi.
For testing, it helps us if you use a standard method each time you report results. For example, set the graphics preset to High (no customizations), clear skies, load the default 172 at your airport of choice, and take the screenshot at the same spot (ready for takeoff).

2 Likes

Ciao all and thank you for your time. This is the situation at the moment (FL 310, PMDG 777)

I use only one display. No popup or anything else.

For the RAM that’s correct 2x48. Those are the settings form nvidia graphic panel

Frame Gen is off –> FrameGeneration NONE

It’s a CyberpowerPC build, correct? –> yes :slight_smile:

1 Like

If you compare your three screenshots from the FPS window: On the first the system needs around 18000 allocs per frame, on the second one it’s 5000 and on the third 3000. On the second screen you see one alloc can take up to 49 us, but this is worst case of course. So a large delay you are seeing in your frame times is caused by the required allocs per frame.

The number of allocs per frame becomes yellow at 1000 and red at 1500. You are always far behind this value. If I fly with the A350, it is around 1200, on smaller planes it is below 1000. I think, this is one point you have to deal with. Many allocs per frame cause CPU overhead, and the garbage collection has to clean up all the memory, which my cause CPU spikes and therefore micro-stutters.

From my experience, the allocs per frame is significantly influenced by addons, in particular by addons using simconnect. Maybe you can try to keep an eye on the values and try to figure out, what causes such high values.

Interesting point. At the moment I have MobiFlight, simlink (navigraph), GSX pro, VasACARS and Elevatex… not really sure who is using simconnect and who is using FSUIIPC7…

I also have a bunch of Simconnect stuff running whenever I fly, and I don’t usually have issues with it. I did once badly muck up a Spad.neXt script which started just spamming the API with a ton of requests and that did destroy my FPS until I found it.

MobiFlight and SimLink are unlikely to be issues - unless you’ve got hardware working in such a way that MobiFlight is overtaxing its Simconnect connection. I assume you’re using MF to interface with hardware that runs Arduinos?

I guess analyse what you had running in your first screenshot vs the second. If you had all the same stuff running, what might those things have been doing when you were at FL390 that they were not when you were on the ground? GSX shouldn’t be doing anything when you’re in the air.

I use mobiflght for using the WinWing devices (MCDU and FCU).

I didn’t change anything in this regards from yesterday evening to today… Also, the first screen of yesterday was taken at FL390 (night), the second one, on ground (night), the third one while flying (day)…

this is now FL330 (night).

How much traffic do you have turned on? I always turn all traffic off and get a base line fps. Then I add traffic in until I get the minimum FPS at a large airport I can live with.

No AI Traffic at the moment .

I have a similar CPU to yours - mine is the 13900 KS S - and with a high end GPU these processors will always be the bottleneck, hence ‘Limited by Mainthread’ showing up every time.

Without taking the drastic step of changing to an AMD X3D CPU + new mobo, there are steps you can take to push more of the load onto the GPU. At the moment, your 5090 will be idling relative to the CPU, same as my RTX 4090 was. Try enabling HAGS in your graphic settings on the PC, and then enabling DLSS and the lowest level of Frame Gen in MSFS. At these lower levels, any artifacts and blurring are extremely minimal, and may not even be noticeable at 1440p.

There are other settings tweaks you can adjust to make things a bit easier on the CPU and achieve a better balance. As already mentioned above, it’s best to settle on a repeatable scenario with a certain aircraft and location in order to do this repeated testing. You could use a stock aircraft and local airport as discussed, or you could just use one of the existing Discovery flights.

With the FPS counter running, try one of these scenarios and fly around for a bit. Then pause it and make small changes to LOD settings, or Shadows, or Terrain pre-caching, resume the flight and see how it looks. The important thing is to make small changes and do them one at a time.

After a while, you will understand which settings have the most effect on your rig, and also how they interact with each other as well as your hardware. Once you have a reasonable baseline, you can try further adjustments around refresh rate, V-Sync etc., and just see which gives you the best result with smooth flying and good details.

Good luck!

1 Like

Thank you all for the valid output. At the moment, seems that changing over XMP from 1 to 3 and enable the CPU gaming boost into the BIOS setting fix a lot the issue.. This is currently the situation. (flying 350 with PMGS 777).

overall seems more stable and less lagging… and really more enjoyable…

That looks a lot better!

2 Likes