9 minutes ago, Lange_666 said:

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.

Ah!  'Pref' instead of 'Perf' - a schoolboy error!     Thanks for confirming it works.

On 11/21/2022 at 6:37 AM, Noel said:

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)

Is that for everyone that MSFS runs on Core 7? If not, how do I determine where the MSFS main thread runs on my machine?

Also, how do you set all processes to run off Core 7? I have Process Lasso installed and running but haven't done much with it yet.

Do you have to keep Process Lasso running in the background or do you just need to open it to make changes and then close it?

6 minutes ago, Rob G said:

Is that for everyone that MSFS runs on Core 7? If not, how do I determine where the MSFS main thread runs on my machine?

I’m thinking (could be wrong though!) that this is more pronounced in DX11. Have a look here it’ll give some more info on how to identify one core working much harder than the rest: https://forums.flightsimulator.com/t/limited-by-main-thread-just-by-one-core/539123

1 hour ago, Rob G said:

Is that for everyone that MSFS runs on Core 7? If not, how do I determine where the MSFS main thread runs on my machine?

Also, how do you set all processes to run off Core 7? I have Process Lasso installed and running but haven't done much with it yet.

Do you have to keep Process Lasso running in the background or do you just need to open it to make changes and then close it?

MSFS runs on the highest core on your CPU, at least that was true w/ CPUs that don't differentiate "performance" core from "efficiency" cores.  So for your I9-10900 should be Core09  (10th core).  It's easy to verify just look at anything that can show you per core work loads--and Lasso does that see graph below.

You're running all other processes in your case on Core0 thru Core08, excluding 9.  You leave MSFS on all cores.

Nope, once it's initialized and changed all of your priority/affinities you can shut it down.  NOTE:  you need to start MSFS before starting Lasso.  I don't start Lasso until I'm on the tarmac.

Notice the % CPU graph to the upper right you can see the main thread is on the last core.  Also notice CPU affinity is 0-6.  The exceptions are certain Windows system processes that don't appear to let you set affinities, but under Rules it appears they might be being set.    I also set Priority Class to High for MSFS and also I/O for MSFS to Critical.  You can sort and group-select and make all changes very quickly, and it saves them for the next time you run Lasso.\

Also, I'm running DX12, FWIW.

So we have as I read intel 12s with tons of e-cores p-cores threads bored-sleeping or staring to the wall, and we need still Process Lasso? really?, is this a joke?. In my old i7 2600k I do not remember any advantage with Lasso. Is Windows 11-10 so bad managing processes then? I can´t believe it. Ok… maybe I will test again the Trial Process Lasso with my 12900k...

34 minutes ago, peloto said:

So we have as I read intel 12s with tons of e-cores p-cores threads bored-sleeping or staring to the wall, and we need still Process Lasso? really?, is this a joke?. In my old i7 2600k I do not remember any advantage with Lasso. Is Windows 11-10 so bad managing processes then? I can´t believe it. Ok… maybe I will test again the Trial Process Lasso with my 12900k...

Why do you think it's presented here as a non-joke?  Hint:  it has nothing to do with "more FPS"😧 🤣

Edited November 22, 20223 yr by Noel

I am confused because I set all active processes, using Process Lasso, to only use CPU 0-8, and MSFS to have access to all CPU processors.

When I start doing stuff with MSFS, I see lots of activity on all processors. I do not see the activity from MSFS limited to just processor 9 on my i9-10900 CPU.

So can I get a better explanation of the MSFS main thread and how to prioritize it properly using Process Lasso? I thought I did the right thing but I don't see the result looking like it.

Regiszry trick works here, MSFS runs on high priority. But, oh surprise, it has absolutely ZERO effect on the CPU induced lag spikes (e.g. stutters...) in my case. So off it goes from my registry again...

55 minutes ago, Noel said:

Why do you think it's presented here as a non-joke?  Hint:  it has nothing to do with "more FPS"😧 🤣

Who is talking here about more fps?😧 🤣

So, to run msfs in high priority I just copy pasted this together with google. Works for me. But I have to read a bit more about batch file creation. But give it a try, for free.

Create a file with the editor. Name it for example MSFSfast.bat. Please check the bold text below. It should be the name off your msfs-folder. Mine was found here: C:\Users\Rasterfahnder\AppData\Local\Microsoft\WindowsApps\Microsoft.FlightSimulator_8wekyxxxxxx

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyxxxxxx!App -FastLaunch
ping 127.0.0.1 -n 36 > nul
wmic process where name="FlightSimulator.exe" call setpriority "128"

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

It just set the priority to high if MSFS starts with in 36 seconds (you can alter the timeout to your needs) and skips the intro. This does not affect affinitymask. I will never touch those settings again with msfs. The .bat file opens a comandline window that needs to be closed manualy, but can stay open for the flight. I guess it is because there is no endline. I will google this later 🐵.

7 hours ago, Lange_666 said:

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.  

 

It works, most likely a step was missed, or you had a spelling error.  I copied and pasted the commands needed from the article to avoid any typos.  Also, did you take the last step and set the value to 3 in the registry?

LouP

Ohh and I did that purely for "smoothness" and "fluidity" and "science" 🤣 🤣🤣. Never for frames.

42 minutes ago, peloto said:

Who is talking here about more fps?😧 🤣

Geez whiz I don't know, I just asked you what YOU hoped to glean out of PL since you said you were going to test it despite it being a joke 😉🤣

16 minutes ago, Noel said:

Geez whiz I don't know, I just asked you what YOU hoped to glean out of PL since you said you were going to test it despite it being a joke 😉🤣

hahahah don´t you know read? I was asking hahah 😉🤣 , you are so intelligent showing you off since the first response to me haha.

50 minutes ago, LouP said:

It works, most likely a step was missed, or you had a spelling error.  I copied and pasted the commands needed from the article to avoid any typos.  Also, did you take the last step and set the value to 3 in the registry?

LouP

5 hours ago, Lange_666 said:

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.