9 hours ago, Noel said:

I think I discovered why it wouldn't launch:  I had to disable affinity assigning to flightsimulator.exe -- so just left assigned to all 8 cores.  Then, it launched!  Can't wait to see if it holds up tomorrow!

Seems like there's something to this then, if you're getting better performance this way. So to reiterate: you kept MSFS on all cores - otherwise it would CTD. And all other running processes on pairs of cores 0-1, 1-2 etc? Well let's hope the positive results continue. 

41 minutes ago, RJC68 said:

I also run MSFS from the reshade bat which is how I discovered the issue.

Basically with Bill's Process Manager you set up a series of rules that allocate specific cores & priorities if needed for individual programs. I am working on a batch file that I can launch once in the MSFS main menu that starts the Process Manager and then each other piece of software I need. The affinities will then be set automatically based on the rules.   

How did running MSFS from the reshade batch make you discover the issue? Just curious 🙂 And would you mind sharing the batch once you have it set up - so that I can have a look at the structure and try to change it to my system?

29 minutes ago, Cpt_Piett said:

Seems like there's something to this then, if you're getting better performance this way. So to reiterate: you kept MSFS on all cores - otherwise it would CTD. And all other running processes on pairs of cores 0-1, 1-2 etc? Well let's hope the positive results continue. 

Yep that's it, it held up for today exit out of LVFR's KSAN.  Right now it's really Main Thread max that is the only source of stutters.  Def looking forward to a better CPU, one well-matched to my 3080Ti which is ample GPU for my needs in MSFS.  13900K at 5.8gHz will be roughly 40+% faster than my 9900K in single-core, and this is HUGE, for my use of MSFS.  I'll look at AMD when it's time but 13900K will be fine.   

1 hour ago, Cpt_Piett said:

Seems like there's something to this then, if you're getting better performance this way. So to reiterate: you kept MSFS on all cores - otherwise it would CTD. And all other running processes on pairs of cores 0-1, 1-2 etc? Well let's hope the positive results continue. 

How did running MSFS from the reshade batch make you discover the issue? Just curious 🙂 And would you mind sharing the batch once you have it set up - so that I can have a look at the structure and try to change it to my system?

I had setup the rules in the process manager to allocate the p-cores then when I tried to start MSFS via the reshade.bat the sim CTD straight away. Then I tried the regular MSFS shortcut I had on my desktop which did the same. When I tried running it from the Xbox app it worked so I rebooted and the reshade.bat worked OK. I just thought it was a weird one off until a couple of hours later I went to start the sim but this time I started process manager then the addons I needed and of course got the CTD. After around an hour I figured what was going on and was able to determine the root cause of the CTD and find the work around by starting MSFS first.

Of course I would be happy to share the batch file once it is ready. Currently I have a line of shortcuts on my Streamdeck that I hit in sequence. I am being lazy I guess doing it from a batch file lol

11 minutes ago, RJC68 said:

I had setup the rules in the process manager to allocate the p-cores then when I tried to start MSFS via the reshade.bat the sim CTD straight away.

Ok, I get it now, thanks for explaining. Strange it would CTD from the shortcuts only though. 

12 minutes ago, RJC68 said:

Of course I would be happy to share the batch file once it is ready. Currently I have a line of shortcuts on my Streamdeck that I hit in sequence. I am being lazy I guess doing it from a batch file lol

Thanks, that'll be great. That Streamdeck doesn't seem so bad actually. I might look into it at some stage. 

Just testing with Lasso and it's working well. The Fenix apps (and other apps as well) can just be permanently assigned by Lasso. With MSFS I just set assignments per session. I.e. instead of choosing "always" in Lasso I just choose "current". Easy. 

I only have these stutters since SU11 - before with SU10 and DX11, everything on my rig was as smooth as butter for the most part.   Has SU11 changed something with DX11 and/or CPU utilization?