8 minutes ago, Ikarus280 said:

I tried the 30Hz refresh rate today via NCP, and the sim was very fluid. There was no stuttering or performance problems.

Sadly the movement of looking around the cockpit with noise made it very jerky, and even more so when looking around with the joystick hatswitch.

Due to that I had to lock FPS to 33 via NCP, as that fixes the jerky movements while panning.

It gives the impression that you are having performance problems, and detracts from the immersion. It has been an issue since FSX and apparently there is no fix for it as far as I know. 

I’ve never tried the NCP method but it sounds like it delivers the same results as a 30Hz display.

Yes, I accept the panning is compromised and it won’t suit everyone. It took me a while to adjust but I can now happily live with 30fps since I don’t pan that much. I use chaseplane keyboard commands for view changes.

4 hours ago, Ray Proudfoot said:

 since I don’t pan that much. I use chaseplane keyboard commands for view changes.

Never noticed any drag but then I use Chaseplane as well for inside. Outside I use the Cycle view and hat switch.

4 hours ago, IanHarrison said:

Never noticed any drag but then I use Chaseplane as well for inside. Outside I use the Cycle view and hat switch.

Which framerate lock/refresh rate are you using?

On 12/9/2021 at 7:13 PM, SteveW said:

Here I am showing how the new affinity settings in Prepar3D v5.3 can be used to avoid core sharing that  is reducing performance:

I have assumed a six core 12 thread HT enabled CPU.

 

in the Red box I have used:

[JobScheduler]
AffinityMask=4095
P3DCoreAffinityMask=4095
MainThreadScheduler=0
RenderThreadScheduler=2
FrameWorkerThreadScheduler=4
 

in the Green box I have used:

[JobScheduler]
AffinityMask=4053
P3DCoreAffinityMask=4053
MainThreadScheduler=0
RenderThreadScheduler=1
FrameWorkerThreadScheduler=2
 

Core 0 is LP0 and LP1. In the screenshots it can be seen that LP0 and LP1 are both used 100% and 30% so that the real throughput of LP0 which is the main P3D task is only getting around 70% of Core 0 because it is shared with a task of 30%, and that is worse when loading scenery. The result is a rise in fps of 20% at least.

Instead in the Green box I have used AM=4053 which is 11,11,11,01,01,01 Right-most digit is LP0 on core 0. This avoids LP0 ad LP1 sharing the available throughput of core 0.

We could always do that with FSX and P3D versions.

The new features of P3D v5.3 is to enable widening of the affinity mask (AffinityMask=) compared to the cores used (P3DCoreAffinityMask=) to accommodate other processes added in by add-ons, and also to enable placing of the main tasks on LPs we desire (Main, Render and FrameWorker) so that we can direct them onto unshared cores.,

 

Hi Steve,

first: thank you for your efforts. I tried the 4053 setting with my 6-core Ryzen and I have some questions.
I compared PMDG 747-400 with engines running, at KBOS with overcast and 100% AI traffic (AIG). I'll start with my observations:

1. The "resting" FPS (ie: cockpit view straight ahead, no view movement) was just the same as before, actually maybe even 3-5% lower.
2. The "moving" FPS (panning around the cockpit, switching between external and internal view, and then returning to straight ahead view) were a lot more stable. While previously (with 4093) they went down about 30% for ~10 seconds after resting the view and only after that went back up, with your setting (4053) they only went down by about 10% for ~10 seconds after resting.
3. For the LP1 exactly what you described happened (much less usage).

So indeed your setting seems to "stabilize" the sim and reduce stutters while moving (either in the air or with the view), which could be godsend for airliner approaches (my FPS usually tanks most on approach and takeoff, where the scenery view changes really quickly all the time on a close LOD level).
I do have two questions however:
1. Why does my "resting" FPS become a bit lower with your settings? Not that I'd mind a lot, but I just wondered if it was a random factor or if it was logically induced due to the new setting.
2. In your pics of the CPU monitoring you showed the FPS, which increased by about 20%. Is that "resting" FPS or some average FPS over a longer time during a normal flight (with view changes etc.)? If it is the former, I'm surprised I don't see that gain in "resting" conditions.

4 hours ago, Ikarus280 said:

Which framerate lock/refresh rate are you using?

RTSS at one half refresh rate and 30 fps.

So with my 8 core 9900k, HT off using the calculator instructions @SteveW  provided to us all cores I got the below:

[JobScheduler]
AffinityMask=255
P3DCoreAffinityMask=255

If I want to keep P3D off core 0 (which I may try) it would be

[JobScheduler]
AffinityMask=254
P3DCoreAffinityMask=254

 

Edited December 12, 20214 yr by B777ER

2 hours ago, B777ER said:

So with my 8 core 9900k, HT off using the calculator instructions @SteveW  provided to us all cores I got the below:

[JobScheduler]
AffinityMask=255
P3DCoreAffinityMask=255

If I want to keep P3D off core 0 (which I may try) it would be

[JobScheduler]
AffinityMask=254
P3DCoreAffinityMask=254

 

I’m currently using the 254 setting with my 9700K and having pretty good performance.  Then moving everything not P3D related to Core 0 has given me some nice headroom.  I’ve seen points where Core 1 is fluctuating just below 100% with the sim running at full tilt, but not stuttering and staying smooth.  Also using NCP to limit frames to 30 as an FYI.  

2 hours ago, B777ER said:

So with my 8 core 9900k, HT off using the calculator instructions @SteveW  provided to us all cores I got the below:

[JobScheduler]
AffinityMask=255
P3DCoreAffinityMask=255

If I want to keep P3D off core 0 (which I may try) it would be

[JobScheduler]
AffinityMask=254
P3DCoreAffinityMask=254

 

What are your MainThreadScheduler, RenderThreadScheduler, FrameWorkerThreadScheduler values then with Affinity =254? (and with AM=255 for that matter)

Thanks

Edited December 12, 20214 yr by Dirk98

20 hours ago, lownslo said:

Each of our systems is unique.  Good luck! 👍

Thank you very much for advice....I know and that is the main "problem" we all have. Your settings for now made it much better than default. I will test of course but what I see for now it is much better.

 

Thanks for help

Edited December 12, 20214 yr by cyyzrwy24

On 12/11/2021 at 10:02 AM, simfan1983 said:

I have just added the following reply in the LM forum. I seem to have solved my stutters:

"I think the stuttering is caused by an overloaded core LP0. Check in task manager on the performance tab if CPU0 is at 100% all of the time. If you are not using Hyperthreading ('HT'), turn this on in BIOS (if you have this option on your processor) and see if that helps, accept the default AffinityMask when you start P3D.

If this doesn't solve the stutters, or you already have HT on in BIOS, or you want to improve performance, you can move the threads for other apps away from the cores that P3D uses with Process Lasso ('PL'). This is a free download and relatively easy to configure. Download PL and run the installer, accept all the initial defaults. When PL is running you can see all the processes and for those running it tells you the CPU usage and the average CPU usage. Right click on non-Windows processes and set CPU Affinity - Always - Select CPU Affinity. Check the tick boxes for cores other than the ones Prepar3D.exe is using and uncheck the ones P3D uses. On my 8700k with 6 physical cores and 12 logical cores P3D uses 1-5 so I set ActiveSky, ChasePlane, Navigraph etc. to use 7 -11. This should help improve P3D performance and reduce stuttering. You can also do this for some other apps such as Microsoft Edge. PL will warn you if you are trying to change a service that needs to be left as it is for the Windows services."

I am right now trying this as I also get the stutters you mentioned, which forces me to restart the flight.

Is there any way global reset/undo button to revert all the changes to the affinity you did for the other programs, just in case? 

2 minutes ago, Ikarus280 said:

Is there any way global reset/undo button to revert all the changes to the affinity you did for the other programs, just in case?

If you mean undoing changes in Project Lasso, then can uninstall and that removes everything. Make sure the config file is not there and reinstall to start again. I have also marked P3D to Induce Performance Mode - which gives it priority while ProBalance does its thing. FYI I completed a 9 hour flight today in the PMDG 777 without any stuttering using PL to manage the processes.

1 minute ago, simfan1983 said:

If you mean undoing changes in Project Lasso, then can uninstall and that removes everything. Make sure the config file is not there and reinstall to start again. I have also marked P3D to Induce Performance Mode - which gives it priority while ProBalance does its thing. FYI I completed a 9 hour flight today in the PMDG 777 without any stuttering using PL to manage the processes.

I see, thanks.

I noticed that P3D was not using 1, 3 and 5. So I set navigraph, active sky, SODE to use those only. 

Hopefully it will fix the issue as on my last flight the stuttering gradually became worse ending up in a total freeze. 

Just now, Ikarus280 said:

Hopefully it will fix the issue as on my last flight the stuttering gradually became worse ending up in a total freeze. 

You can make changes 'on the fly' so to speak with PL and watch the impact on the core usage, especially if you have 2 screens.

Found this great Affinity Calculator posted by another user back in 2019. 

Edited December 12, 20214 yr by Wise87

On 12/10/2021 at 8:04 PM, cyyzrwy24 said:

I am trying hard...but I still can't figure what is best for 10700K and Z490 Prime. I looked everywhere and it seems that I am only simmer with 10700K.

 

Any help?

You're not the only one. I have the 10700k/ROG Maximus XII and I just recently started having issues. The first few flights I did were good; I noticed slight shutters but now it's worst which gives me headaches. I tried default AM, AM 65364, and 64853. I noticed that default was better overall, so I stuck with that. But ever since then my fps are fluctuating significantly. The values we all default so I don't know where the issue is coming from. I removed the AM, and even though I still get some pauses it's not bad as with AM enabled. Suggestions? Thanks in advance.