21 hours ago, B777ER said:

What are the file names that you deleted? 

They are called UmPolicy and sits in every /FSLabs/"Aircraft/Data folders) IF you had FSL auto optimise

They can be opened with notepad

Michael Moe

Edited December 28, 20214 yr by Michael Moe

On 12/27/2021 at 1:23 PM, Michael Moe said:

Hi, I have to say i also tested this as there was different UmPolicys in my FSlabs/Data folders under each aircraft type. They were not with the same AM.

I deleted them and the section above prior to starting up P3D and now its butter smooth with cameras and engines running. Try this!

Michael Moe

Thank you, this worked for me, so far!

Doing a flight this morning in the 321SL, once engines were started I had constant stutters on the ground whilst taxiing. Still the same once airborne so I saved the flight and tried this fix, loaded back up from where I left off and it seemed to have disappeared. I'm now 1 hour into the flight and its still smooth.

Opening the files with notepad, I had different entries in the 320 compared to the 321 strangely enough.

I have a feeling these files were left behind from previous versions as this was the first time flying the 321 since the update. The 320 I had flown previously which maybe why I didn't have this issue yesterday as I did a flight yesterday in the 320SL and had zero problems with stuttering, was smooth from start to finish.

Previously I had always ticked the box when prompted by FSLabs to optimise CPU policy. I deleted the above files and it asked me again on loading up P3D but this time I unticked it.

Thanks again,

Happy New Year

Edited December 31, 20214 yr by Avionixz

iam going to try this thanks , been getting terrible stutters since reisntall of the sim, thought my GPU was overheating , but apparently 70-75c is normal 🙃

V5.2 also ran better for me.

In any case, VRAM problems are there again with V5.3 ..

I got along well with 5.2 VRAM ... 5.3 is again too little

ive also done the affinity mask thing ( ray again ) will report back after these two changes 

My P3d.CFG is automatic changing between AM=253 and AM=255 by itself so guess this could also contribute to some issues using ProcessLasso as well ?

I had really bad stuttering comming in to FT YSSY 34R with FTX ORBX AUSV2 . Never saw that before. as YSSY is very smooth even in the FSL bus.

Made a restart  and took a spin around YSSY from the the gate with absolute no stutters.

 

Michael Moe 

It's interesting for the length of time these stutters have been reported there is not a fix from LM. Mine for the most part has been unflyable for quite awhile. Just tried it again yesterday and actually once got a smooth flight and the rest had to shut it down.

So do I understand currently some have removed the 5.3 client and replaced it with the 5.2 client and solved the problem?

 

I am getting extremely smooth performance after the affinity mask tweak. No stutters at all in 5.3. Have pretty much all the add-ons running Orbx global, open lc, gsx, active sky, rex 5, pmdg. Not a single dip below 30fps. All sliders to the right with EA on volumetric clouds off. Res at 4k. System is Amd 5900x, RtX 3080.

Pardon my lack of knowledge but i don't know what affinity mask is or how to tweak it.

I9-9900k, 7900xt 20 gig.

2 hours ago, dbw1 said:

Pardon my lack of knowledge but i don't know what affinity mask is or how to tweak it.

I9-9900k, 7900xt 20 gig.

Please take a look at this thread 

 

P3d config - where can I find this? Thanks very much.

C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v5

Replace <username> with your login name.

Edited January 29, 20233 yr by pgde

pgde...Thanks.

AM settings will vary based on the CPU used and how you load 3rd party software like AIG, ChasePlane, and then specific aircraft settings.  

FSLabs forcing setting changes is something they shouldn't be doing.  There is no valid reason for it given it doesn't factor in CPU types and the users add-ons.  I know many have requested FSLabs stop doing this but it falls on deaf ears or stubbornness thinking it will reduce support when in fact it just creates more support.

If you run AMD CPU with multiple CCDs, then assign cores so that only ONE CCD is used, don't cross CCD ... in the case of AMD 7950X 8 cores on one CCD is more than enough and you should see an improvement, more so if you plan to run AMD 7950X3D variant due in Feb.

Now the bad news, Microsoft have changed Win11 specific to AMD and Intel core scheduling which can basically invalidate core assignments.  If you install Process Lasso that might help but be aware Process Lasso comes with overhead and you lose a little performance.  It's a battle between this is what I want my cores to do vs. OS saying this is what I want the cores to do ... hopefully Microsoft sort out their scheduling.

Edited January 29, 20233 yr by CO2Neutral