Because an image is worth a thousand words.
A video is worth a millions words.
Large-FOV is limited in render resolution by steamsettings, pls look here: https://community.openmr.ai/t/how-to-exceed-the-maximum-resolution-of-4096px-imposed-by-steamvr/16067
Yep but a lot of people was telling me here on the forum that it wasnt anymore necessary to do it because it was something old and not actual with latest pitool software. So I did a video to show they were wrong ( part 1 ) and the part 2 video show people how to do it right. The video clearly demonstrate the proof of that evidence.
Thanks. I had also heard that the setting was unnecessary. Clearly, your tests show that isn’t the case.
I KNOW I bumped this setting in the past, but it had dropped to 4096. I set it back to 8192. Now I know why I couldn’t improve the star skybox res in Elite D. (I changed the ED configuration file and saw no difference.)
Just know that as the warning in the file implies Your setting will get overwritten on every SteamVR update.
You should change it or add it to the user config instead if possible:
https://community.openmr.ai/t/default-vrsettings-maxrecommendedresolution-steamvr/21330/22?u=drwilken
There’s also a third vrsettings file which is user settings (You can search for it) probably located somewhere in Local folder, but the idea with the one shipped by PiTool is to override defaults only for aapvr driver (Pimax) compared to the default SteamVR provided file.
Thanks for the tip. I thought I tried editing that one in the past and (for one reason or another) it didn’t seem to take effect. But the overwritable file did work. Since I thought Pimax fixed the max-res issue a while back, I just ignored the setting from then on.
I will investigate your recommended settings file again, at some point. My main concern is that text in Elite D in my 8K is as readable as possible. I had noticed that the text seemed coarser and no amount of tweaking appeared to help. I didn’t have gaming time today, so I hope to test ED tomorrow.
The fix was to put the setting in that file so if it’s not read any longer that’s why the fix doesn’t work…
As a side note: If anybody is having troubles with vanishing entries, that they had added to their “steamvr.vrsettings” file, it turns out that this is because SteamVR removes as superfluous any lines that are identical to what’s already present in: “default.vrsettings”, so if, e.g, increasing: “maxRecommendedResolution” in the user settings file; Make sure it’s a different value to the default.
(Can be mildly annoying when trying things back and forth; As soon as you e.g. make the render camera “parallel” projections, in user settings, away the line goes, for the described reason, and it has to be added back in, next time setting it to “raw”. :7)