Maybe you missed the most important point: Because pitools software updates and StemVR updates do change the standard resolutions. The only way to avoid that is to focus on vertical pixels (PP does enlarge horizontal pixels) and manually select there to around 2160. Then start the game and check with fpsvr or SteamVR performance graph the frametimes. If you have headroom you can go further up with the vertical pixel settings. Depends on the horsepower of your GPU and of course the game.
These were rhetorical questions. I understand the basics now, but not everyone will find this out before they really start trying/reading/investigating, simply because there is no single thread which would explain this. Does this means whe should blame people for trying? I dont think so. Because if they dont try - they’ll never learn.
Hopefully the Pimax Experience will largely solve the issue as really the sort of optimizations we are discussing should absolutely be automatic or at least a simple “1” click to optimize.
People should absolutely not be required to “discover” the best settings especially for fundamental improvements.
Are you sure you are clicking APPLY button when changing the PiTool settings?
And restarting SteamVR after doing changes?
The resolution in SteamVR, having PiTool 1.0 and Normal FOV (no PP) is around 3800x3100. On Large FOV its around 4500x3100. Nowhere near the 8200x4000 you get.
@Davebobman Wiki has this info I believe. To ensure once it is setup correctly a script setup to overwrite the setting file might be an idea.
It is too bad pitool cannot do this for the user but @PimaxUSA said they can’t modify this file as part of rules from Valve. So likely the pimax experience cannot breach this “rule” either.
I remember the good old times BEFORE SteamVR implemented GPU-based quality, GPU-ranking upon SteamVR start and 3 different settings for basically the same thing: supersampling. Back then, everything worked fine. Then came the updates…
Im sure, im not doing any changes with pitool anymore. I have just launched it and made a fresh screenshot, and this values are actually same as i had when first installed pitool 2 days ago.
Dear @sweviver I checked @industria s values before answering him. The values he postet are correct (or: i got the same). Pitools .261 update from .260
BUT: Some other issue: i just went through all Pitools-default resolutions, and we have a problem there (PP off, changed to 50% SteamVRSS to have proper vertical resolution)
Large: 2636x2232
Normal: 2636x2232 (!!)
Small: 2188x2232
Potato: 1892x2232
So either large mode is wrong or all lower than large setting moved up one tier. I think the latter because checking the FOV in the headset potato seams to me to be small.
And that is also the reason why i was happy to use small as my standard setting last couple of days…
SteamVR version 1.13.9
EDIT: SOME MISTAKE on MY PART! Don´t know what it was. but changing between large and normal did not change the steamVr resolution. despite closing and starting steamVR again.
I checked again after pc restart:
Potato: 100% 2676x3160
Small: 100% 3096x3160
Normal: 100% 3732x3160
Large: 100% 4882x3160
Sorry to have shocked you @SweViver
EDIT2: Do we have to reboot the HMD after each size change? because i have the impression after changing the size and additional reboot the picture with the stars do change in size, too. If so, this is a quite important fact you should tell us all. unless the picture gets just resized inside the headset?
Well, if you dont tweak your cfgs to unlock higher resolutions - this wont have any affects and you dont even need to borther yourself. It will just run in 4k with stable 75 even if its shows crazy values in steamvr. But if you do so, you will have to adjust resolution to some realistical values each time you change fov or parallel projections. In half life alyx i found its just not necessary to tune and go above 4k, it caused for me more issues than profit. But in other games it might be really necessary, like aerofly mentioned by the sweviver somewhere above.