This initial setup for Process Lasso will help with the most common tuning issue facing DCS VR Pilots running SteamVR
Keeping DCS and SteamVR process on separate cores will eliminate some types of stutter and drag for VR users.
[CLICK HERE for a deeper dive video]
This does NOT apply to Oculus Rift users.
The Rift processes do not react well to Core restrictions and appear to manage to keep away from busy cores on their own.
CPU Core Binding Goals
- Lock DCS to specific cores for on-going process management.
- Ensure the VR process keep away from DCS when running.
- Setup DCS to later ensure other windows processes do not impede either of those critical process groups.
Processes Initial Focus
- (Steam) VR Compositor
- (Steam) VR Server.exe
- Other Steam Services
- A (6) Core CPU running Hyperthreading shows (12) Cores.
- Core 0 & 1 being Physical Core 0 and it’s Virtual Core 1.
- All even cores are physical, all odd cores are virtual.
Decide which two Cores to lock DCS into.
If you choose the top two Cores to lock DCS.EXE to, with Hyperthreading on, you would select Cores (8-9) (10-11).
To keep Steam processing away from DCS.exe, you would make those cores not available to the steam process. Simply by checking the boxes for all Cores and unchecking the boxes for (8-9) and (10-11).
- The best way to do this is to run the applications/SteamVR and DCS in VR mode.
- Run Process Lasso and find the processes noted above.
- Right-click on the process and select “CPU Affinity/Always/Select CPU Affinity”.
- Then walk through locking the process in or out of your chosen schema.