On 12/13/2021 at 10:40 AM, tangjuice81 said:

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. 

This is the advice I've got and that "relieved" great pressure of my cores. As  @Rob_Ainscough pointed and makes sense. As soon as I changed to recommended, on the ground with just engines running I was getting much better FPS, but monitoring my cores, none was "clogged", especially LP0 and LP1. In the AIR I never achieved better FPS. Everything seems to be much faster. So...that was my experience.

11,11,11,11,01,01,01,00 = 65364 = AffinityMask
11,11,11,11,01,01,01,00 = 65364 = P3DCoreAffinityMask
00,00,00,00,00,00,00,01 = 0 = MainThreadScheduler
00,00,00,00,00,00,01,00 = 1 = RenderThreadScheduler
00,00,00,00,00,01,00,00 = 2 = FrameWorkerThreadScheduler

However, now since I found calculator above, result is 65535. I believe that was LM default but that one somehow didn't work. It worth to test.

Edited December 16, 20214 yr by cyyzrwy24

4 hours ago, cyyzrwy24 said:

This is the advice I've got and that "relieved" great pressure of my cores. As  @Rob_Ainscough pointed and makes sense. As soon as I changed to recommended, on the ground with just engines running I was getting much better FPS, but monitoring my cores, none was "clogged", especially LP0 and LP1. In the AIR I never achieved better FPS. Everything seems to be much faster. So...that was my experience.

11,11,11,11,01,01,01,00 = 65364 = AffinityMask
11,11,11,11,01,01,01,00 = 65364 = P3DCoreAffinityMask
00,00,00,00,00,00,00,01 = 0 = MainThreadScheduler
00,00,00,00,00,00,01,00 = 1 = RenderThreadScheduler
00,00,00,00,00,01,00,00 = 2 = FrameWorkerThreadScheduler

However, now since I found calculator above, result is 65535. I believe that was LM default but that one somehow didn't work. It worth to test.

Could someone explain to me what changing what changing the thread scheduler could achieve ?, ive already changed the default 255 to 254 by reading these forums ( 9700K ) happy ish with the result so far 

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

thanks

On 12/11/2021 at 5:33 PM, Ray Proudfoot said:

@SteveW, you’ve clearly gone to a lot of work to create these AF settings for various CPUs. It would be a pity if your posts were buried inside this topic and be difficult to find.

If you want to copy and paste them into a new topic in P3D Tips and Tricks we can lock and pin it.

If Steve does that please don’t reply if you get there before a moderator as we’ll delete any replies.

Thanks Ray I will do that!

I'll be away from my desk for a few weeks but will put together a more detailed explanation for this as soon as I am back in the new year.

 

I appreciate the fantastic support from forum members very much and I wish you all a very happy holiday season.

Regards

Steve

@SteveW, thanks Steve, I’ll look out for it next year.

A happy Christmas and a better 2022 to you and yours too. 😁👍

Been performing a long haul flight for the last 8 hours and in the last 30 minutes my FPS dipped to single digits. There's plenty of room left for CPU and GPU and the weird thing is, the computer fans got quieter, the GPU temperature is around 60 degree. Something is way defineltly off. It's been totally fine for about 7.5 hours and now it''s literally a slide show

Thank you for the tips Rob, I'll try those and see if it yields any improvement. It's the first time it happend, all my flight had been around the 2-hour mark so far.

6 minutes ago, Rob_Ainscough said:

Win10, turn OFF GPU scheduling

Same with Win 11. I'm still testing but I think this may be the key issue. I did a long flight yesterday with this off and had zero problems, sim was the smoothest I have seen it so far.

I checked and I have the latest NVIDIA already installed. I'll deactivate the GPU scheduler after I finish my flight and will do some tests.

1 hour ago, qualio said:

Been performing a long haul flight for the last 8 hours and in the last 30 minutes my FPS dipped to single digits. There's plenty of room left for CPU and GPU and the weird thing is, the computer fans got quieter, the GPU temperature is around 60 degree. Something is way defineltly off. It's been totally fine for about 7.5 hours and now it''s literally a slide show

Same experience here, often the FPS dip occurs after only 15-20 minutes. Some sessions are problem free, 90% of the time the fps suddenly drop to single digits.

https://www.prepar3d.com/forum/viewtopic.php?f=6315&t=143918&start=90

Personally I believe this is being triggered by new /scenery .bgl's introduced in v5.3

Take a look at the Orlando area in v5.3 - LM acidentally included a 970Mb .bgl with 300,000 OSM buildings converted to models, thus the massive filesize and slideshow when flying in that particular region (not to mention 5 minute loading time at KMCO). 

Possible these files exist elsewhere and when pages cause a sudden FPS drop?

Other than that v5.3 is the best performing version to date, so this has been very frustrating to say the least

 

 

Edited December 16, 20214 yr by PinkPony

53 minutes ago, Rob_Ainscough said:

I had a similar issue but didn't take that long to run into it ... I also started having CTDs.  In my case (may not be relevant to you case but thought I'd share) the following seems to have "fixed" it:

• Win10, turn OFF GPU scheduling
• Download latest GRD drivers for my nVidia GPU.
• Download latest DDU and run in Safe Mode with network cable removed (important to NOT have any internet connectivity be it wireless or hardwire).
• Boot back into normal mode and install the nVidia GRD drivers.

Cheers, Rob.

 

 

 

No CTD's at all on my end running v5.3 for up to 16 hours on end. FPS suddenly dropping into the single digits has occured on 90% of the sessions both with HAGS enable and disabled. There is definitely something off in how v5.3 pages specific scenery data. The confirmed traffic related slideshows and sloped runway freeze are all .bgl related as well!

7 hours ago, Rob_Ainscough said:

I had a similar issue but didn't take that long to run into it ... I also started having CTDs.  In my case (may not be relevant to you case but thought I'd share) the following seems to have "fixed" it:

• Win10, turn OFF GPU scheduling
• Download latest GRD drivers for my nVidia GPU.
• Download latest DDU and run in Safe Mode with network cable removed (important to NOT have any internet connectivity be it wireless or hardwire).
• Boot back into normal mode and install the nVidia GRD drivers.

Cheers, Rob.

 

 

The latest  Studio Driver ( 472.84 ) is very good.

Edited December 17, 20214 yr by GSalden

7 hours ago, PinkPony said:

 

No CTD's at all on my end running v5.3 for up to 16 hours on end. FPS suddenly dropping into the single digits has occured on 90% of the sessions both with HAGS enable and disabled. There is definitely something off in how v5.3 pages specific scenery data. The confirmed traffic related slideshows and sloped runway freeze are all .bgl related as well!

Hm I haven‘t had any FPS drop like that on 5.3, it‘s been the most stable version for me. I do have heavy addons (PMDG, fslabs) and heavy scenery (airports and some city scenery), and an average pc. Apart from Orlando I haven‘t experienced anything yet, and those sloped runway issues „only“ lead to a 30 second freeze, but not to a permanent FPS drop.
I guess there is something wrong with your setup. Did you do a clean install for 5.3?

7 hours ago, GSalden said:

The latest  Studio Driver ( 472.84 ) is very good

How so? Genuinely interested, as I should update sometime soon.

When I installed P3D 5.3, I did a complete fresh install, including Windows 11. Always do that with major releases of the sim. Currently using the NVIDIA 497.09 driver.

Followed Rob’s tip and deactivated the GPU scheduling in Windows settings and am performing another flight right now at about 4.5 hour length. Haven’t had issues on flights 1-2 hours long since the release. Happened for the first time yesterday at the 7.5 hour mark on my 9 hour flight. The interesting thing was the computer pretty much went idle, fans slowed down and the temperatures went down. The GPU was at about 60 degrees, utilization was at about 25 percent. It’s like the system shifted the focus or “dropped” P3D.

I haven’t adjusted or touched anything in the P3D.cfg. In the task manager all cores were assigned to P3D.

I’ve had the 20 second freezes before but didn’t think much of it since I’ve read about it and thought a fix would be released for that eventually or an updated graphics driver.

About 3.5 hours into my flight and micro stutters are occurring. It’s acceptable but very noticeable. I’ll just have to test more and want to disable the full screen optimization option for P3D for my next flight.

The frames are at a steady 55 to 70 in the cruise. I wonder if there’s some kind of overload happening since it’s been fine for first 1.5 to 2.5 hours, which ran smoothly without a single stutter or freeze. Even emptied the standby memory.