Run MSFS process as high priority

[cianpars 1,231]

It's a bit of a pain having to set the priority every time I uses MSFS but I'm finding it's running more smoothly in this configuration.

Is it possible to start the process as high priority via a batch file?  If so, would anyone mind posting the text to do so, bearing in mind that most of us would probably need to edit the location of flightsimulator.exe, but that wouldn't be too difficult.

Thanks to anyone who can provide the text for me to insert into a .bat file.

Whilst on the subject of batch files, could anyone supply the text they might be using to launch several processes, e.g. littlenavmap, fsltl and flightsim.exe.

I guess most of us would be able to edit the location for each process and if a .bat file could be written to do both, that would be fantastic.

Thanks to anyone who responds, whether they create one to do the job specifically or just copy and paste the text from the .bat file they are using themselves.

[bobcat999 8,548]

All good questions.  I have recently bought Process Lasso, which I believe can do this (high priority) plus more, but I haven't started using it yet.  The free version may do it.

[cianpars 1,231]

Thanks Bob, I will take a look.

[JimBrown 596]

Here's another third party program to set priority levels. And affinities. And all sorts of other stuff. And it's free.

https://www.bill2-software.com/processmanager/

And here's a video on how to use it to set the priority level.

 

[Noel 4,580]

Process Lasso is an excellent program, easy to use and definitely does what it's supposed to including retaining affinity/priority including I/O priority.  I have all processes running off of Core7, where MSFS' main thread runs, have changed MSFS process priority and I/O to High.

It is one of several actions taken recently that have yielded best ever flight performance (meaning smoothest, most stutter-free and it is, etc)

[RJC68 824]

On 11/20/2022 at 9:39 AM, JimBrown said:

Here's another third party program to set priority levels. And affinities. And all sorts of other stuff. And it's free.

https://www.bill2-software.com/processmanager/

And here's a video on how to use it to set the priority level.

 

I use this and it works well the only caveat I found is I need to start the addons I need (Spad.next, FSLTL etc) then MSFS and once I am in the aircraft at the gate I start Bill's process manager which will take care of all the affinity's and the priorities. If I start the process manager first MSFS will CTD every time. For some reason MSFS does not like it if the affinity is changed before it is fully loaded. If I have to quit the sim a simple reboot is required then I repeat the process. I have all my addon apps on my E-Cores and just leave MSFS on the P-Cores

[LouP 119]

I have it starting up on high priority with no issue with a simple edit to the registry.  Take a look here:  736: Set MSFS Priority to High at All Time #3 – FSX TIMES (wordpress.com)

LouP

[Andre92 38]

Also used Lasso, but after upgrading my PC with an AMD CPU, MSFS always crashed with Lasso activated.

Now i’m using dAffinity, a small tool to set the CPU Core Affinity and CPU priority for each program running. You can try and use it for free; with the paid version you can save your preferences so it’s setup automatically each time.
I run FSUIPC, FSLTL, Fenixsim, etc all on the last 4 (HT) Cores and leave the rest for MSFS and windows. 

https://www.d7xtech.com/daffinity/

Maybe something you can use.

Kind Regards,
Andre

Edited November 21, 2022 by Andre92

[Noel 4,580]

40 minutes ago, Andre92 said:

Also used Lasso, but after upgrading my PC with an AMD CPU, MSFS always crashed with Lasso activated.

Now i’m using dAffinity, a small tool to set the CPU Core Affinity and CPU priority for each program running. You can try and use it for free; with the paid version you can save your preferences so it’s setup automatically each time.
I run FSUIPC, FSLTL, Fenixsim, etc all on the last 4 (HT) Cores and leave the rest for MSFS and windows. 

https://www.d7xtech.com/daffinity/

Maybe something you can use.

Kind Regards,
Andre

Thanks Andre, did you ever contact Justin of Bitsum, the developer of Lasso on AMD?  I'm contemplating moving to AMD CPU next year.  At least there is dAffinity you are saying.

[Andre92 38]

No, i didn’t. Just happened to find this alternative and never bothered with Lasso again. Lasso is also a great program (if it works).

Regards,

Andre

[Lange_666 171]

16 hours ago, LouP said:

I have it starting up on high priority with no issue with a simple edit to the registry.  Take a look here:  736: Set MSFS Priority to High at All Time #3 – FSX TIMES (wordpress.com)

Did set this but where can i see that it actually runs in high priority now (Win 10 Pro)?
Not in Task Manager anyway...

[cianpars 1,231]

14 minutes ago, Lange_666 said:

Did set this but where can i see that it actually runs in high priority now (Win 10 Pro)?
Not in Task Manager anyway...

Does it not show in task manager when you click on details, then right click on the flightsimulator.exe process Lange?

[Lange_666 171]

With the registry hack set (double checked again just now) the priority still stays at "Normal". So the register thingy doesn't work.
Then i used this: https://fsxtimes.wordpress.com/2021/08/15/726-set-msfs-priority-to-high-at-all-time-2/ (set High and Save for FlightSimulator.exe)
If i then check Task Manager again, the priority is on "High", however, if i quit FS and rerun, it's again at "Normal" so it doesn't stick. It's not permanent.
If i run ProcessHacker again it's still set to High but in fact it's back to Normal if i pull up Task Manager along side. If i then confirm it again in Process Hacker, it changes in Task Manager to High until i quit FS.  

 

Edited November 22, 2022 by Lange_666

[tgsweat 146]

1 hour ago, Lange_666 said:

 So the register thingy doesn't work.
 

 

It definitely works for me everytime i load the sim. 

[Lange_666 171]

After a triple check it does for me now to. Made a (easy overlooked) typo in the reg edit. 
Made a subkey named PrefOptions instead of PerfOptions which doesn't make it work.
Overlooked on the double check but nailed on the triple one.