The possibility Teh Devs™ have locked something down is ever-present, and Omicron.log has been caught blowing sunshine once or twice, so all we can do is try %$@# as we think of it, and be civil to each other as gambits fall though …
You are the first time I've heard of physics_ Wait: What? I though we were talking about
sys_spec_physics
in which everybody and their brother sees a boost by setting to 1; sys_physics_CPU is one of the Twelve Placed Threads, and I strongly suspect it's also locked down, set to core one (on the 0~5 number scale). For the longest time, I thought physics running on the last core, which is the one that's always bumping up against the
sys_budget_soundCPU
limit of 15 percentage points. (If you change sys_budget_soundCPU to 5, or even 0 if you have a real sound card, that core gets even busier, and your fps has a small bump.) Now that I believe the Named subset of Placed Threads are locked, you have
;ca_thread0Affinity = 5
;r_WaterUpdateThread = 5
;sys_main_CPU = 0
;sys_physics_CPU = 1
;sys_streaming_CPU = 1
set in stone, and all you can do is move the Six Task Threads around, hoping to perk a lazy core up, and/ or get a framerate boost.
I've got six cores like you, so
sys_TaskThread2_CPU = 4
sys_TaskThread4_CPU = 2
sys_TaskThread0_CPU = 4
sys_TaskThread1_CPU = 0
sys_TaskThread3_CPU = 2
sys_TaskThread5_CPU = 1
may or may not help out around the locked placements.
That you say you can move physics_CPU I can only marvel at, the same way I'd had this one conversion where someone was telling me sys_MaxFPS does nothing, but sys_budget_fps works great. I'm glad something worked for ya', buddy, but What Is This I Don't Even …
That's "As Far As I Can Tell." :-Þ
PostAA seems to need some motion to do it's job, so there always seems a hint of jaggies in Spider cockpits.
I know jack-all about CCC, but in nVidiaLand, you'd trust nVidia Inspector to get crâp done way better then nVidia Control Panel without the extra supervision. I'd head over the the forums at guru3d.com and poke around for something to make the driver trump in-game settings.
Are you working with your user.cfg? The others ether have warning labels on them, or else never seem to do anything: In fact, I just did a fresh reinstall, chasing down some bazaar-o crâp, and only then did the two with "Property of PGI" labels change to reflect DX11.
I should point out something:
r_TexturesStreaming = 1
r_TexturesStreamPoolSize = 1024
;If r_TexturesStreaming is set to 2, this parameter is chosen automatically for PC. Default is 128
r_TexturesStreamPoolSysSize = 4096
;If r_TexturesStreaming is set to 2, this parameter is chosen automatically for PC. Default is 800
"PoolSize" is video card RAM, and the other is main memory; I guess this makes
r_TexturesStreaming = 2
a pretty good default; And durring the time between the DX11 patch and my reinstall, a setting of zero made for some really ugly pop-in (haven't retested yet;) I've got RAM to burn, so I jack up things that should increase memory usage, like what you see here, and only once has it backfired. ;-)
Keep in touch
Edited by Goose, 09 March 2014 - 10:43 PM.