I understand this is a key parameter to control the sharpness of the 8KX and so far I haven’t been able to set it and keep it to 1.5 so have never seen the 8KX in high res mode. I’ve followed the instructions very carefully for both manually changing the values and using the WFOFix program. I took a backup of the original steamvr.vrsettings file so whenever I re-try I ensure any mistake that may have been made is not carried through. I check always that I don’t use ‘pretty’ double quotes. But steamVR always sets the value back to something close to 0.5 EVERY time I restart it. Anyone any ideas?
That is not entirely correct. the gpuSpeedRenderTargetScale controls the sharpness of the steam menus as they appear in VR.
But not the resolution of the games.
Anyway we expect steamVr to slowly change the gpuSpeedRenderTargetScale by updating the gpuSpeed entries one at a time to a lesser number so your experience does sound weird. I’ll try and test it on my machine in a bit, it is always possible that steamVr has changed behavior.
2 Likes
To elaborate a little on what BNP said: Yes, that value is calculated on startup, every time, and that is its normal behaviour.
It is based (…among other things, such as the HMD base resolution, I have to presume) on the mean results from the last ten runs of a small benchmark (…or something), that is executed every SteamVR startup – these are what is stored in the gpuSpeed0-9 queue of keys.
What we have been doing to indirectly get the gpuSpeedRenderTargetScale up, is to spoof those ten numbers higher, putting our proverbial thumb on the scales.
An added complication is that current SteamVR betas, at this moment in time, are tweaking the algorithm that produces the fresh render scale, looking at one’s gmem situation in some way I am not quite clear on, and this messes things up for that workaround, making it not work the way it used to; I e.g. right now get a really sharp image in the dashboard menus when using large FOV mode with the p8kX, without touching the numbers at all, but terrible undersampling with any of the others, even if I push them through the roof.
I suppose we can either opt out of SteamVR beta, to revert to the last stable release, or wait for Valve to hopefully sort it out – maybe some feedback to the developers could help… :7
(Patch notes suggest that new API features puts some of the power to affect the matter in the hands of the HMD makers, so maybe Pimax will come up with a solution…)
2 Likes
You could try changing/saving the profile settings in Pimax Experience. Then, AFAIK, the settings should get applied every time you launch something with that profile (ie SteamVR Home uses the SteamVR profile).
EDIT: Every time you launch something through PE with that profile
2 Likes
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.