I do this now using process lasso and it works no problem….I haven’t done formal testing with lasso on and then off, but I can see that the workload is more evenly spread out across the entire cpu so I do think it helps avoid any one of the p-cores running the sim. I may do formal testing but it would require using cap frame ex which is a great tool to capture frame times, 0.1% lows, etc in a data driven way to compare results in a controlled flight plan. I first used lasso to force my varjo headset software to run on p-cores along with MSFS as that seemed to eliminate some micro stuttering and I put many other tasks on e cores only (hardware monitoring, navigraph, etc).
1 Like