Manipulators increased timings (lower fps)

Description of the issue:
Manipulator time increasing by changing A/C causing lower fps

Did you experience this issue before you joined the Beta?
No

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
No

FREQUENCY OF ISSUE

Every time

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

1. First load-in is always/usually ok - lets say Fenix: getting 125fps, manipulators(man.) 9ms.
2. Load-in with ini A350. It might be ok. 75-85fps, man. 15ms.
3. Load in ini A300 (+different airport?): now manipulators usually go ‘haywire’: 45-50fps, man. 30ms. (Here I usually have 80fps, man. 15ms if it is first load-in).
4. Now go back to Fenix: fps dropped to 95ish, man.increased to 13ms
5. Back to ini A350: fps dropped to 55, man.increased to 20ms.

Im only able to reproduce this (but then every time) switching between A350 and A300 from iniBuilds - WASM heavy A/C(?). Switching between lighter GAs etc does not produce this. Is there some cache not emtying between load-ins? WASM not clearing in memory?
Restarting MS2024: ok again.

[PC Only] Are you using Developer Mode or have you made any changes to it?
Yes

[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:
5090 - 572.83
[PC Only] What other relevant PC specs can you share?
7900x3d, 64gb ram(5600MT), HDR on, 4k (5120x1440), 2xFG

MEDIA

Please add a screenshot or video of the issue occurring.
FlyTampa EHAM D47, except changing airport when loading in A300.
1. First load-in Fenix=ok. 124fps/9ms
2. A350 ok. 74-80fps/15ms
3. Load in A300. Man going bad. 49fps/30ms
4. Back to Fenix. Also having increased man.time. 98fps/12ms
5. A350 also incresed man.time. Fps worse. 55fps/20ms






**

Are you running on the balanced power plan (which is the AMD recommended)? I also have the 7900x3d cpu and with the balanced power plan the 2nd CCD is parked so basically everything runs on the 1st CCD which has the 3d cache. What I have found with this config is that a heavy cpu intensive workload will impact performance due to everything on just 6 cores/12 threads. The complex planes you are using along with any other 3rd party add-ons is definitely increasing the strain on the cpu as you are mainthread limited.

I’d recommend trying the ultimate power plan to see if it works better for you. The ultimate power plan will still force all games to run on the 1st CCD with the 3d cache however it will never park any cores. You’ll most like see in Task Manager a more even utilization across all cores which will help out with the cpu intensive workloads. MSFS 2024 does much better utilizing all of your cores. This is how I run the sim with my 7900x3d/7900xtx gpu.

Balanced power plan. Using all threads in 2024. Unlike 2020 where I forced the v-cache cores.

This has nothing to do with CPU setup though.
Performance is excellent: ultra, tlod 350-400 etc etc. But fps deteriorates if one change from one A/C(wasm heavy?) to another. And it wont recover unless I restart ms2024. That is not intended behaviour…

But tnx :wink: i can certainly check the ultimate power plan though.

2 Likes