if you guys are playing with processor affinity a lot, you might be interested to know that the game has a cvar that grants proper affinity control ... unlike disabling the job system, or assigning 'threads' to 'cores' .... it goes into a user.cfg file, BEFORE anything else ... and cannot be changed within software after rendering has begun ...
--;---- AFFINITY MUST BE SET BEFORE ANYTHING ELSE IN ORDER TO WORK
--; variable: sys_affinity
--; type: int
--; help: CPU affinity, which cpu's to run on
--; this is a proper control for which 'cores' to run on, IT USES DECIMAL INPUT
--; dont forget, that counting starts from 0
--; 254 : last7 (1,2,3,4,5,6,7)
--; 252 : last6 (2,3,4,5,6,7)
--; 170 : odd (1,3,5,7)
--; 128 : last (just core 7)
--; 85 : even (0,2,4,6)
--; 84 : back3 (3,5,7)
--; 80 : back2 (5,7)
--; 64 : just7 (just core 6)
--; 1 : first (just core 1)
sys_affinity = 252
recently, I had a game, where I locked the affinity to a single core, wondering if that was enough oomph to play .... and apparently it is ...
https://youtu.be/bAM_xUoTCjs
so I wouldn't really expect that giving it more power will solve all underlying issues
Edited by NARC BAIT, 21 March 2017 - 01:03 AM.