You can also set it manually in steamvr.settings (but it resets all the time), or let Pimax Experience do it for You.
All You have to do is change the value (set it to 5000) as @arminelec mentions here:
https://community.openmr.ai/t/starting-to-have-problems-after-latest-steam-update/33115/13?u=drwilken
Hi,
today I received the Steam VR 1.15 update and afterwards the steam overlay resolution (e.g. the steam vr overlay or the OVRdrop interface) are very low res. I’m using the settings from the Pimax Experience and even raised to GPU Speed to 15000 w/o affecting the overlay quality. Did anybody face the same issue and found a solution?
Fixed render scale issue affecting Pimax and some other headsets (e.g. Quest2 via Virtual Desktop).
Maximum automatic render resolution is now additionally limited based on total dedicated gpu memory. This limit can be configured by headset manufacturers in their OpenVR hmd driver once the SDK is updated. In the meantime, users can override the automatic value in Settings if needed (e.g for Pimax 8KX).
Last two posts were merged from this topic:
https://community.openmr.ai/t/bad-overlay-resolution-after-recent-steam-vr-1-15-update/33144
The correct location of steamvr.vrsettings may vary depending on your environment.
C:\Program Files (x86)\Steam\config
Or
C:\Users\ username \AppData\Local\openvr
If the value you set is not reflected, you may be referring to a file in a different location.
So looks like switching to SteamVR beta fixes it 
yep the steamvr beta has fixed it with update today
I also checked the updated SteamVR beta.
Ver. 1.15.11 reverts the calculation of gpuSpeed to its original value.
5000 is not needed.
2000 is fine for gpuSpeed.
Right-click on SteamVR in the Steam library and select Properties.
Then select the SteamVR Beta Update from the Beta tab.
@Yata_PL can you comment it? Why did you need to use 5000? Did you try 2000, yes I saw seems steam scale is changed & now we need bigger values, but just to be sure didn’t 2000 worked? I guess I will update guide accordingly
I have not tested new steamvr beta. In my case 2000 was too low and picture was still low res.
5000 is perfect and I have noticed even sharper text than before
Note , that I did rapid tests only in ACC and steamvr home enviroment.
I just make the settings file, read only and dont have any problems like that weirdly.
That might work as a short-term solution, but I’m sure making the main steamvr configuration file read-only will get You into trouble down the line… 
It’s kinda where it stores it’s configuration You know…
Weird, I got it since over a year now like that. Even after the update the vr.settings working fine.
All I’m saying is You’ve made it impossible for SteamVR to write to it’s configuration file.
Just keep that in mind if something weird starts happening down the line.
That’s all…
I have the same problem but only if i use 1.25 render quality in Pitool. Every other render qualitiy setting in Pitool is working fine.
problems also solved with BETA version which I rarely use
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
