A few days ago talking to a friend of a group of Telegram in Spain that we have for the sponsors of pimax 8k, he told us that he saw a default.vrsettings file in the configuration of SteamVR with a parameter maxRecommendedResolution: 4096, he modified that value and now if it admits an SS greater than a resolution of 4096.
The default value is 4096. I set it to 8096. Bingo! application resolution elite dangerous at 6100x3000: super sharp @ large FOV!! In addition I set rendertarget multiplier to 2:0.
The default is 4096. Your friend probably said to add the 0 because there’s no way anyone would go that high, so there’s no need to go back in to edit it.
Also, this doesn’t seem to work for me. Tested with newest PiTool, parallel projections on, kept Steam SS at 100% and Pitool at 1.0. Normal looks good, Large FOV looks worse. I only tested in SteamVR Home. Maybe actual games show a difference?
Yep. Restarted Steam going back and forth. That’s how I knew the settings didn’t work, since the rendered resolution was worse with Large. I usually go to Normal then start SteamVR, and then go to Large. That still looks better than Large --> Start SteamVR.
The default vrsettings file seems to be written to every time steamVR is launched when pitool is running. This does not happen steamVR is launched on its own (without pi tool running)
Did you tried to revert to 4096 to see if the resolution sinks ?
I saw this setting some time ago, but deduce that “MaxRecomendedResolution” was to stop SteamVR to auto move the slider to resolutions that the Vive/VivePro display can´t render and waste GPU resources (100% diminished returns).