On my AMD 5800x3D, using native openXR, it makes a tangible and measurable difference, consistently, no matter what maps, planes, mission or view I use. OK, then it seems safe to assume using Process Lasso to set the affinity for DCS is not recommended for Intel CPU's.īut something is different: it looks like you are using Steam VR, is this correct?Īlso, did you force all other processes to other cores than DCS.exe? I'm basically seeing worse performance in CPU heavy scenarios with the E-cores disallowed for DCS. I still see the same results even after restarting DCS with the different affinities applied, just without being able to see the difference, immediately, in the graphs. MSI Afterburner CPU E-core usage is shown on the right. where the core affinity is changed from allowing E-cores to disallowing E-cores for only DCS. When I use process lasso to disallow DCS to run on E-Cores (force DCS to run on P-cores), I actually see my CPU frametime go UP by a margin of 2-3ms with higher averages and more peaks. The mission used for results is mission, F-16, Nevada, Cold and Dark. One interesting thing that I've found is that for some reason, DCS loves to use my E-cores when allowed to, while using one P-core, probably as the rendering thread. My PC is a 12600k (all P-core OC 4.9 GHz, E-core 3.6 GHz), 3080, on a Reverb G2. Wait for frame times to stabilize before comparing/screenshotting 'rdr CPU' and 'app GPU' values. Make it easy by enabling screenshots in the OpenXR toolkit companion app, enable the Advanced OpenXR FPS counter, and select CTRL + F12 to create a screenshot create before and after with the exact same view in VR. But really validate your frame times when trying. I can easily imagine your CPU to a bottleneck and fixing Affinity does not work for you. Good question: I would only assign 1 thread for all and 3 for DCS.exe. In my situation would be enough to asign the affinity for all cores for DCS? I have an old 2500K with 4 Cores 4 Threads. Screenshot before and after enabling Process Lasso, making sure you have the exact same view angle in VR. Always test and validate these settings yourselves.Įasy way to validate frame times yourself:Ĭhoose a stable, non-moving, scene (while being parked) in the external view (with loads of objects) that has high but relatively stable 'rdr CPU' frame times.Disable 'Game Bar' - as it easily conflicts with Process Lasso settings.This also works with other Simulators and games in VR.I always manually start Process Lasso before I start DCS: I do not want Process Lasso to be enabled during startup and interfere with normal usage. Enable performance mode in Process Lasso.I also forced 'Always - high priority' on DCS.exe.Do not worry about excluding system processes, when setting affinity: if it is not possible to change affinity, nothing happens.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |