Should I be removing the AM setting from my config file?

 

I would (and do), default install has no AM settings.

What core should you look at to disable for P3D en enable for TrackIR?

 

Experiment and see what works for your system ... too many system variances for there to a "golden rule".

 

 

 

I highly recommend the program Process Lasso.

 

I purchased a version, but it didn't seem to do anything better than what I can accomplish with freeware "Process Explorer" -- it's "ProBalance" mode was interesting but didn't really change anything.  

 

However, I do like that Process Lasso allows you to set Affinity and Priority and other parameters on a per task basis and retains the settings so I don't have to keep changing them every time I fire up P3D and/or TrackIR.  That was worth the price of admission.

 

Cheers, Rob.

Hello Rob,

 

Thanks again for all your updates on P3D Updates.  Very Appreciated.   Would you say Process Lasso helped achieve the fluidness we see in the videos and what your seeing on screen.  I just seem to be a step away from this. I'm using Alacrity 64 version which allows me to start P3D/Trackir/AivlaSoft  and dictate which cores to use and what priority level which is set at above normal  but no control over where rest of computer processes fan out over cores. 

 

Great Job

Steve

My P3D v2.3 installation (patched) works definitely better without the AM in the cfg-file.

Spirit

Yep, also no AM tweaks and all works like clockwork

Thanks all, I will remove the line and see how it goes.

What are you saying about:

[Display]

TEXTURE_BANDWIDTH_MULT=1800  ??

 

Found it here (german site):

http://simmershome.de/prepar3d-2-3-einstellungen/

What are you saying about:

[Display]

TEXTURE_BANDWIDTH_MULT=1800  ??

 

Found it here (german site):

http://simmershome.de/prepar3d-2-3-einstellungen/

 

1800?  @_@   How powerful is this guy's video card?  @_@  The most I have ever gotten away with in FSX was 400.

I highly recommend the program Process Lasso.   It allows you to set priority and cores in real time while monitoring resources.   I used it to isolate P3D on to 4 of my cores and let NOTHING else in my process list touch those cores.   It is one of the reasons I went from struggling with high settings to 60 FPS pegged in most scenarios on my hardware.    Let NOTHING interfere with the cores your P3D is running on.

 

Check it out:  https://bitsum.com/processlasso/

Is there a rule of thumb so to speak on what core to run windows processes on? Everything including P3D on my processes list has all 8 cores running. Im getting desperate trying to get decent frames in weather.

 

 

Would you say Process Lasso helped achieve the fluidness we see in the videos and what your seeing on screen. 

 

I've experimented with various Process Lasso app profiles and to be honest, they really haven't made any difference for me. P3D V2.3 seems to work best when it's left alone.  I tried all kinds of combinations and priority settings and the results were always about the same ... there was no magic bullet here for me.  If you look at the Process Lasso documents, they are pretty clear that they don't/can't improve game FPS ... in fact, their documentation is refreshingly honest about what they can and can't do.  It's a good product, but it's not going magically improve your FPS unless you've got some other applications/services running on your computer that is hungry for CPU time/priority.

 

To get smooth operation the answer is what many don't like the hear ... turn down/off graphics settings.  The world location you fly, the 3rd party installed content, the aircraft type, and the weather add-on (with many cloud layers) will make the most impact to smoothness.

 

I target/lock 30 fps, because my 4K/video card (HDMI 1.4) monitor runs at 30Hz ... I go about adjusting graphics settings so that I can sustain my locked target FPS.  However, in some cases I'll drop to 20 fps lock just so I can enjoy more visual treats in those dense/demanding scenery areas.

 

If there is a rule of thumb, it would be let P3D V2.3 run on all cores (this is the default).

 

Cheers, Rob.

Nice info thanks guys

I've experimented with various Process Lasso app profiles and to be honest, they really haven't made any difference for me. P3D V2.3 seems to work best when it's left alone.  I tried all kinds of combinations and priority settings and the results were always about the same ... there was no magic bullet here for me.  If you look at the Process Lasso documents, they are pretty clear that they don't/can't improve game FPS ... in fact, their documentation is refreshingly honest about what they can and can't do.  It's a good product, but it's not going magically improve your FPS unless you've got some other applications/services running on your computer that is hungry for CPU time/priority.

 

To get smooth operation the answer is what many don't like the hear ... turn down/off graphics settings.  The world location you fly, the 3rd party installed content, the aircraft type, and the weather add-on (with many cloud layers) will make the most impact to smoothness.

 

I target/lock 30 fps, because my 4K/video card (HDMI 1.4) monitor runs at 30Hz ... I go about adjusting graphics settings so that I can sustain my locked target FPS.  However, in some cases I'll drop to 20 fps lock just so I can enjoy more visual treats in those dense/demanding scenery areas.

 

If there is a rule of thumb, it would be let P3D V2.3 run on all cores (this is the default).

 

Cheers, Rob.

 

Rob is right.   Process Lasso isn't about FPS improvement per say.  It's about not contaminating the cores your P3D runs on.   On my beast rig, for whatever reason, running P3D on ALL cores is bad for my FPS because the cores are getting contaminated by one or more processes my computer runs.   When I pushed all other programs away and isolated P3D on core 11, 9, 7 and 5 (6 core HT CPU) it made my FPS go from a dismal 29 FPS avg to pegged at 60 (my refresh rate of my monitors) in the default aircraft.   With PMDG 737NGX running my FPS on average is now 25 but because my P3D is not contaminated that 25 FPS is smooth as glass, even at payware airports in moderately craptastic weather.   SteveW and Rich really saved my bacon with their help about core contamination. 

Rob is right.   Process Lasso isn't about FPS improvement per say.  It's about not contaminating the cores your P3D runs on.   On my beast rig, for whatever reason, running P3D on ALL cores is bad for my FPS because the cores are getting contaminated by one or more processes my computer runs.   When I pushed all other programs away and isolated P3D on core 11, 9, 7 and 5 (6 core HT CPU) it made my FPS go from a dismal 29 FPS avg to pegged at 60 (my refresh rate of my monitors) in the default aircraft.   With PMDG 737NGX running my FPS on average is now 25 but because my P3D is not contaminated that 25 FPS is smooth as glass, even at payware airports in moderately craptastic weather.   SteveW and Rich really saved my bacon with their help about core contamination. 

 

Glad to hear we could help Buddy - sounds like its cranking out the FPS now - well done

Rob is right.   Process Lasso isn't about FPS improvement per say.  It's about not contaminating the cores your P3D runs on.   On my beast rig, for whatever reason, running P3D on ALL cores is bad for my FPS because the cores are getting contaminated by one or more processes my computer runs.   When I pushed all other programs away and isolated P3D on core 11, 9, 7 and 5 (6 core HT CPU) it made my FPS go from a dismal 29 FPS avg to pegged at 60 (my refresh rate of my monitors) in the default aircraft.   With PMDG 737NGX running my FPS on average is now 25 but because my P3D is not contaminated that 25 FPS is smooth as glass, even at payware airports in moderately craptastic weather.   SteveW and Rich really saved my bacon with their help about core contamination.

Cheers mate. P3Dv2 has gone back to an AM=0 just like FSX, which could spell problems for HT enabled systems.

Cheers mate. P3Dv2 has gone back to an AM=0 just like FSX, which could spell problems for HT enabled systems.

 

Well if that happens can't we just move all the P3D processes on to the physical cores instead of the HT ones?

To get smooth operation the answer is what many don't like the hear ... turn down/off graphics settings.  The world location you fly, the 3rd party installed content, the aircraft type, and the weather add-on (with many cloud layers) will make the most impact to smoothness.

 

Cheers, Rob.

 

Can you tell us your current settings? Or is the beta v2.3 your actual settings in your homepage?