Hi guys,

 

Probably Steve is the one that knows the answer, but I will post it anyway so all can read it.

 

P3Dv3 is running very smooth on my system, even though I switched from NVSurround to 3 seperate views.

V 3.2 has been optimized for Multi Monitor and performance is way better than before with Undocked windows.

 

At the moment I am looking for the best settings when there are multiple cloud layers with rain and detailed scenery.

When banking over a major city with autrogen on I have some smalll stutters.

 

First I was thinking of adding another graphcis card to my system ( already have a Titan X ) , but then I wanted to know the GPU load first.

Just did some testing and my GPU has a load : 34-92% depending on the scenery.

So the card can handle it.

 

 

Then I looked at the CPU load. I use AM=340 and this is what it looks in CPU ID HW when there some stutters are introduced when banking :

----------------------------- Current Value ------Min value ---------Max value ---

 

 

When those small stutters occur Core 6 has a load of 100% and core 8 has a load of 93%. Core 2 is a little better at 82%.

Core 1 , the main P3D core has a nice load of 90%.

 

I did not even fire up my Prosim modules and Opus , which are assigned by Proces Lasso to core  0, 1, 10 and 11.

 

 

Now with AM=1360 :

------------------- Current value --------- Min value ---------- Max value --

 

 

Both core 8 and core 10 are have reached 100%.

Stuttering was worse than with AM=340.

 

 

Would another AM be better in this case ?

Did some additional Tests with a saved flight.

 

The above screenshots are not correct as I startedCPU ID HW before P3Dv3. Now with P3Dv3 already running.

 

5820K :

 

AM 340

 

AM1360

 

AM1300

 

 

Why the banking stutters occur I do not know....

CPU not 100% stressedd and the GPU also not 100% stressed with AM 340 and AM 1360...

 Unfortunately, I don't have your AM setting answer - I have FSX-SE with an Intell 6700K chip not O/C'd.

 I set the AM to 14. (I think this is correct for my CPU).  I get really good FPS with few stutters.

 

 Unless I missed it, I don't see your CPU type mentioned in your post... 

Did some additional Tests with a saved flight.

 

The above screenshots are not correct as I startedCPU ID HW before P3Dv3. Now with P3Dv3 already running.

 

5820K :

 

AM 340

 

AM1360

 

AM1300

 

 

Why the banking stutters occur I do not know....

CPU not 100% stressedd and the GPU also not 100% stressed with AM 340 and AM 1360...

 

Not every stutter is CPU related I would say. With those AMs it shouldn't be an issue.

 

Might wanna check and try rolling back your GPU drivers though

 

That being said, another thing I've noticed with with my 3.2, the scenery rendering cores seem to peak a lot higher and more most of the time probably inducing stutters and etc.

 

 

 

I have FSX-SE with an Intell 6700K chip not O/C'd.

 I set the AM to 14. (I think this is correct for my CPU)

 

That would be correct if you turned off HT.

The Nvidia drivers I use are the very good 361.91 drivers...

 

The moment those banking stutters occur framerate drops to 12-14 for less then half a second.

Therefore I find it strange that no core shows a load of 100% at that time...

 

Normally I can fly with both AG sliders set to Very Dense with all kind of clouds. Only with an overcast I set the AG both to Dense.

I am able to improve ths situation by pulling back the autogen sliders to dense ( buildings ) and normal ( trees ) with OC + Rain. 3-4small jitters when comming out of banking now.

Just did a quickk test : without AG no jitters anymore.

 

That is very nice, but why do I have those banking stutters in the first place as no CPU core is stressed to 100% ?   Also the GPU not stressed to 100%....

 

System :

5820K @ 4.3Ghz

MSI X99S XPOWER AC

G.Skill Ripjaws 2400 Mhz  ( 15-15-15-35-2T )

Titan X

5x SSD Agility 3 ( write/read 500mb/s + )

3X Samsung 32"HD tv  (3x 1920x1080 @24Hrtz)

 

P3D :

Unlimited / Vsync On / TB On

 

NVI :

Frameratelock at 25

Yeah its probably not a CPU related thing in the first place. Have you tried running completely unlimited? Removing the framelock in NVI?

Yeah its probably not a CPU related thing in the first place. Have you tried running completely unlimited? Removing the framelock in NVI?

Did not try that. I will tomorrow.

Thanks for the suggestion.

I would remove the NVI frame lock also. Have tested it on my system, with a few different driver versions, and all it does is to increase stuttering. The sim will run smooth for a few seconds, then there are three long stutters, and then it will run smooth again, until the whole thing repeats itself. Much better with it gone, 30hz refresh rate + VSYNC + unlimited in my case:)

 

BTW - have you tried with HT off? In my case, my old 3770K @ 5.0ghz runs P3D far smoother with HT off. I suppose Intel has implemented some new HT tech since 2012, and that newer CPUs are better in this regard, so maybe HT on is the way to go. Dosen´t hurt to try anyway. 

Looks good, It can be seen that 340 gives just a little bit more to the system, and 1360 more to the sim by a few %. OK for your networked setup Gerard. Look more at the VSync/Refresh/fps/LOD/Autogen equation.

 

 

 

kristolz, on 11 Apr 2016 - 12:29 PM, said:

In my case, my old 3770K @ 5.0ghz runs P3D far smoother with HT off. I suppose Intel has implemented some new HT tech since 2012, and that newer CPUs are better in this regard, so maybe HT on is the way to go. Dosen´t hurt to try anyway.

With HT On, these sims cannot be run efficiently without the appropriate AM, whatever CPU in use. In reality, HT On with the old CPUs didn't decrease performance.

 

There is a case at 5Ghz however, that the extra work done with HT enabled could increase the CPU temp by a few degrees even with an appropriate AM, and prevent successful operation at 5GHz.

 

HT off would reduce the networking performance, and other resources of the O/S, not essentially the sim main threads themselves. The few percent lost with HT disabled can be made up with an increase of a few 100MHz. If you got the cooling it can be worth checking the trade-off.

Looks good, It can be seen that 340 gives just a little bit more to the system, and 1360 more to the sim by a few %. OK for your networked setup Gerard. Look more at the VSync/Refresh/fps/LOD/Autogen equation.

What I now have is a luxury problem, not a real issue...LOL