I heard about this program for the first time in some threads here dealing with Affinity Masks and I very briefly checked it out.  It looks like it may be useful.  Does anyone have some opinions of it and what settings are best used with P3D.  Is having an Affinity Mask setting still relevant if using this?  Thanks!

Very short (and little guessing): Process Lasso allows you to manually assign your software to certain cores/threads of your CPU. This means: with the corresponding affinity mask entry, you could stop P3D using for example core0 and in turn tell process lasso, that all other software running in parallel to P3D (e.g. Weather Software) exclusively uses this free core0. If you run a lot of additional software along with your P3D, this might help. In my case for example, I am fine with only the AF setting, as I do not run a lot of other software in parallel to my P3D.

PL is great tool and I use icw my Fs addons.

Do not use it with the P3D.exe file ! Use an AM in the P3D.cfg file for that.

This software has great reviews and the dev is very active on his forums. 

If you get it avoid the urge to start tweaking, it works great out of box. The only option I enabled was the smart trim that takes care of your RAM, best to Google it. 

It's an exceptional program 

No tweaking huh?  That will be a hard to resist that urge as I often spend more time tweaking than flying!  OK, good information - thanks!

With PL I manually have assigned the Fs addons to the free cores...

All other processes are done by PL itself.

18 minutes ago, GSalden said:

With PL I manually have assigned the Fs addons to the free cores...

All other processes are done by PL itself.

Thats interesting, you have six cores so can see the benefit in doing that. I only have 4 and they are pretty busy

The more cores the better for PL by the looks

12 minutes ago, Venturi said:

Thats interesting, you have six cores so can see the benefit in doing that. I only have 4 and they are pretty busy

The more cores the better for PL by the looks

Yes more cores gives you more options, if you cant sacrifice any core, then just take care that anything do not run at first core (and thread for that core if applicable) used by P3D and it will be fine.

My 6 core uses AM=340 : 00,01,01,01,01,00

My addons I have devide with PL over 0,1,10,11. Each addon uses 0 or 1 icw 10 or 11, so 2 per addon.

I have tried without AM let the system handle itself but I got small stutters in heavy scenery.

 

PL is great, built-in power profiles that also unparks cores, does a better job at managing problematic processes so they don't interfere with your simulator, you can see easily if your AM is working and even set it inside PL. 

I have been using it (the paid version) for some time but didn't try it in Prepar3d4 (and with my new machine) yet. I agree it is powerful and the developer is very active, but I was a bit lost in-between the host of options and settings (and suggestions by various people on how to exploit them - just take core unparking named above as an example).

Sometimes it's better to keep things simple, at least for a layman like me.

Kind regards, Michael

I have been using it for some 3 years now and when P3Dv4 came out I contacted the developer to find out if he could recommend any specific settings for this new version of the sim. His reply was that it was unnecessary to tweak any settings. Have to confess that since adding this program to my Windows 7 64 on previous FSX and 32 bit versions of P3D an currently on V4 the system has always run very well and CPU bottlenecks are a thing of the past.

I concur with Joaquin.

I bought the paid version (pro version) after watching a video on youtube where it was recommended.  The youtuber recommended the following settings :

- priority class -> always -> high

- cpu affinity -> always -> uncheck core 0 and 1 (so in my case, leave 2-7 checked)

- enable 'exclude from probalance restraint'

- enable 'exclude from smart trim'

- enable 'disable idle saver when running'

- enable 'classify as a high performance process'

 

I dutifully tried them as well as combinations of them.  I tried using this for Chaseplane, active sky, pro atc and p3d (the addons I always run when flying).  My result was rather interesting.  I kept getting serious stutters (macro-stutters...not micro ones).  HOwever anytime I would click on a window outside p3d, the stutters would go away and the sim would run smooth like butter.  I even posted a video (and a forum post here) on this problem:

 

So...after reading the above, I tried disabling lasso tweaks for p3d....and boom....smooth like butter.  

Note this is with a fresh (45minute old P3d install w hotfix + pmdg 777 / 747 + TFDi 717.

 

37 minutes ago, Hilkiah said:

I concur with Joaquin.

I bought the paid version (pro version) after watching a video on youtube where it was recommended.  The youtuber recommended the following settings :

- priority class -> always -> high

- cpu affinity -> always -> uncheck core 0 and 1 (so in my case, leave 2-7 checked)

- enable 'exclude from probalance restraint'

- enable 'exclude from smart trim'

- enable 'disable idle saver when running'

- enable 'classify as a high performance process'

 

I dutifully tried them as well as combinations of them.  I tried using this for Chaseplane, active sky, pro atc and p3d (the addons I always run when flying).  My result was rather interesting.  I kept getting serious stutters (macro-stutters...not micro ones).  HOwever anytime I would click on a window outside p3d, the stutters would go away and the sim would run smooth like butter.  I even posted a video (and a forum post here) on this problem:

 

So...after reading the above, I tried disabling lasso tweaks for p3d....and boom....smooth like butter.  

Note this is with a fresh (45minute old P3d install w hotfix + pmdg 777 / 747 + TFDi 717.

 

Lots of pointless settings and settings that work against you there. 

First, you should never really mess with the priority class as Windows does a mighty fine job of handling job priority itself. When you start forcing applications to run at a much higher priority, maybe over processes, services or addons the simulator relies on, you could end up seeing adverse effects to the performance or introduce stutters.

Also, set your affinity with the AM settings in the config for the simulator, not through PL. Use it just to confirm the mask is working. Secondly, don't remove the simulator from the main core, as that will often cause terrain to stop loading completely.

So this was more a case of a bad configuration rather than process lasso not doing its job. In fact, just focus on setting the Bitsum Highest Performance for whatever you are running and then let it do its job in the background. Stop messing around with it :)

Agreed Michael.

Quick question though:

- where you go to set the AF for P3D?  

- what AF should I have in my case (I have a 4790k)?

 

Thanks.