I think my question is related to this topic (or maybe not) so I will post here.
I periodically write this into to the steamvr VRSETTINGS file:
“GpuSpeed”: {
“gpuSpeed0”: 2000,
“gpuSpeed1”: 2000,
“gpuSpeed2”: 2000,
“gpuSpeed3”: 2000,
“gpuSpeed4”: 2000,
“gpuSpeed5”: 2000,
“gpuSpeed6”: 2000,
“gpuSpeed7”: 2000,
“gpuSpeed8”: 2000,
“gpuSpeed9”: 2000,
“gpuSpeedCount”: 10,
“gpuSpeedDriver”: “27.21.14.5206”,
“gpuSpeedHorsepower”: 2000,
“gpuSpeedRenderTargetScale”: 1.5,
“gpuSpeedVendor”: “NVIDIA GeForce GTX 1080 Ti”,
“gpuSpeedVersion”: 2
One of the “2000” speed numbers used to be over-written with a smaller number each time SteamVR was run. So it was necessary to periodically redo the “2000” over-writes.
But now, the very first time I run SteamVR after pasting all those 2000s the section looks like this:
“GpuSpeed” : {
“gpuSpeed0” : 995,
“gpuSpeedCount” : 1,
“gpuSpeedDriver” : “27.21.14.5751”,
“gpuSpeedHorsepower” : 995,
“gpuSpeedRenderTargetScale” : 0.47999998927116394,
“gpuSpeedVendor” : “NVIDIA GeForce GTX 1080 Ti”,
“gpuSpeedVersion” : 2
So is the old method of writing all those 2000s in order to keep SteamVR from handicapping me obsolete. And if I manually set a Resolution Per Eye in SteamVR does it make this whole gpuSpeedDriver / Horsepower / TargetScale a non-issue?
PiTool 1.0.1.269
FW 2.1.255.296