Im gonna post this again because I think It's Important

[Michael Moe 495]

5 minutes ago, andrecarli737 said:

Do anyone know why would you have to do Step 3 every time we open the game? PL has a "Always" tab on the priority class.

Could be the fact that this action first will work when entering the MSFS menu as he wrote.

Michael Moe

[Dirk98 354]

3 minutes ago, Michael Moe said:

Could be the fact that this action first will work when entering the MSFS menu as he wrote.

Michael Moe

Not a big deal, Alt+Enter and set it at the beginning. Then stop the Console (not the service) and Alt+Enter again.

[Dirk98 354]

19 minutes ago, andrecarli737 said:

Do anyone know why would you have to do Step 3 every time we open the game? PL has a "Always" tab on the priority class.

Howeve I made my profile and that setting stays Disabled.

Edited September 1, 2020 by Dirk98

[JughedJones 214]

8 hours ago, SierraHotel said:

One question? Where do we find the .exe in the X-Box Store install? (Yes I know all about the steam version)

Theres no need to find the .exe in a folder.

 

 

You have to do this after the sim has gone to the main menu, and it just shows up on the list.  It really couldn't be any easier, just follow the steps.  

Edited September 1, 2020 by JughedJones

[SmokeDiddy 262]

Thanks for reposting this!  I messed around with Lasso for a few days, but I was still getting the stuttering, pausing and bottlenecks.  I followed this guide exactly and I'm in business.  I had all but given up on it until I could get some new hardware, but this has extended the life of my trusty, but dated rig.  Really, this needs to be a sticky because of it's importance, especially for those with dated hardware.

Thanks again!!!

[JughedJones 214]

5 hours ago, andrecarli737 said:

Do anyone know why would you have to do Step 3 every time we open the game? PL has a "Always" tab on the priority class.

The author of the tip said it caused crashing if you set it to always.  

[Dirk98 354]

1 hour ago, JughedJones said:

The author of the tip said it caused crashing if you set it to always.  

Not the case on my rig.

[Fielder 3,676]

" Start the game and wait for it to reach the main menu (Do NOT do the next step before the game has reached the main menu, trust me on this one) "

Are one of these two menus are what TessellatedGuy meant when he wrote "main menu"? Or some other menu in the game?

Thanks.

1

 

 

2

Edited September 1, 2020 by Fielder

[Luis Hernandez 570]

CTDs for me 😭

[dave2013 1,130]

I can confirm that this greatly reduced the stuttering for me.  I'm using windowed mode if that makes any difference.

Dave

[marcg11 125]

I just want to state this has been a godsend to me....no more huge stutters and mainly smooth.   I am using a pretty underwhelming setup (I5 6600 K OC to 4.3 ghz - 1660ti - 16MB ram) but at least the sim is smooth and now I can see if I can tweak up some of my in game settings.

I wish I could say I understood why I needed to do this (shouldn't the game be optimized for this kind of thing to begin with) but I guess its just my CPU and am glad theres a way to improve thats pretty painless.

 

Edited September 2, 2020 by marcg11
Added thought

[Flyfaster_MTN002 412]

Giving this a shot!

Ok some interesting stuff on an older Dell with 1060 6GB card OC'd with X1:

1) with 16GB of RAM it is using between 80-96% constantly.

2) processor is not being maxed out too hard surprisingly

3) still getting micro stutters at times and major pauses/stutters over LA basin / LAX etc however NO noticeable spike on the CPU or GPU etc? Odd?

Edited September 2, 2020 by Flyfaster

[speedbird034 14]

I am curious, because I am now tweaking my rig to operate with msfs2020 and I used Process Lasso in the past.

So far, I’ve had mixed success with it, there is an absolute bottleneck with the CPU and I know Process Lasso is the solution. I just haven’t gotten it to the sweet spot in which it will run on the rig and be stable, especially at landing.

If anyone out there has a good solution, I’d love to hear an update on the Process Lasso tweak.

My rig:

i7-3770k OC to 5.0 GHz (stable OC with water cooling)

ASUS Sabretooth Z77 MB, Corsair Vengence 32GB DDR3 1866 RAM.

Windows 10 Pro, stripped down (see Chris Tech Talk solution for debloating Win 10).

Windows on a Samsung 870EVO SSD.

MSFS on separate Samsun 870EVO SSD.

1GHZ internet connection, am running Ethernet to the router.

GTX 1060 (not overclocked...not yet).

I am open to suggestions...because I don’t want to spend money on this quite yet...not until we see the impact that the pay ware adds (think QW787 being the first) will have on the sim. Right now I’m focused on the A32NX as that is the only commercial airliner in the sim worth flying, The 787XE and Salty 747-8 fixes are still not flyable.

Thanks!

[Noel 4,502]

On 1/18/2021 at 6:25 PM, speedbird034 said:

I am open to suggestions...because I don’t want to spend money on this quite yet...not until we see the impact that the pay ware adds (think QW787 being the first) will have on the sim. Right now I’m focused on the A32NX as that is the only commercial airliner in the sim worth flying, The 787XE and Salty 747-8 fixes are still not flyable.

Thanks!

Critical to know is how you are running the sim in terms of frame rate locking, vsync, etc.  If you are not vsyncing to a 30Hz capable screen, then know you're asking your CPU to run at 100% utilization, which is akin to always seeing the CPU hit an absolute bottle neck, no matter what the environment, even if there is headroom in the CPU because you are telling it to generate as many frames as it can.  If possible, if your screen supports 30Hz which it may or may not, you can set MSFS to VSYNC, set frames at 60 in MSFS, and what you will see then is the sim locked at 30 AND, and this is the important part, your CPU will run at the lowest possible rate required to maintain that 30fps.  I understand if you have a true G-Sync monitor you can achieve the same benefits and set the frame lock wherever it can work best at for you.  

Here is a simple example w/ my 9900K, in an easy to process scenario.  This was was set un-synced to 30hz screen as I set the screen to its default 60Hz, and so ran the sim un-framelocked.  Notice the CPU load is at 52%, the GPU at 99% so is now GPU-limited:

Here is the identical scenario however vsynced to 30Hz screen.  Notice the CPU load is now at only 27% instead of 52%, there is now headroom also in the GPU, and here's the most important part of all:  comparing video animation between these two approaches it is clear vsync to the 30Hz screen is superior in terms of smoothness, freedom from stutters, so it is a clear win-win: better performance, better visuals, AND maximum headroom for 3rd party airware.  

W/ the 9900K and vsync to 30Hz I am able to run the sim at Ultra 100/200/200 everywhere and still have considerable CPU headroom in the main thread.  My RTX 2070 Super is not able to run all the GPU-dominant sliders at Ultra so in busy areas or areas w/ heavy weather I will turn down volumetric clouds to High from Ultra, and dial back shadow quality a bit as well as required to keep the GPU below maxed.

The downsides of vsync to 30hz screen:  if it can't meet or exceed the 30fps limit stuttering starts.  Also, there are some who insist they have serious physiologic reactions to viewing an LCD screen at 30Hz, for example headaches, eyesore, and so forth.  I have none of these things whatsoever, can look at the screen continuously and have no problems, and everyone who has viewed my screen while I'm flying also sees nothing but fluid, stable imagery.  The other real problem:  you prob don't have a 30Hz capable screen, but might--open up NV Control Panel, resolution and see if it's an option.

Edited January 20, 2021 by Noel

[ThomseN_inc 1,128]

The only and first thing that turned MSFS into a real enjoyable experience for me was setting and getting used to play it in 30Hz. I admit i was sceptic at first but i wouldn't run it any other way now. 4k, all settings on ultra with no stutters (except some Carenado things) and absolutely smooth. Give it a try. No need for third party "performance fixes" and stuff like that.