And watch for the exact notation of the quatationmarks, per default my editor put out different ones…
Good point. These are basics in coding most people don’t know about, especially with French/German keyboards&software, so that’d be likely too, good point.
Yes keep in mind this forum sometimes gives the wrong double quotation marks. Make sure it’s " and not the squigly double quotation. Also place the line not at the very top but after lastversiondate.
the reason you get a performance hit or “slideshow” is because now it will actually let all your other settings work. you need to bring them down to a reasonable area. start by setting steamvr to auto, to see what it think is reasonable and then work from there.
maxrecommendedresolution is a limiter, it limits the render to that number of pixels horizontally, so setting pitool to 1.5 will be trying to set the render to something like 7000 pixels wide, so limiting the render to 4096 is why performance improves when you leave the maxRR at 4096… removing the limit impacts performance because suddenly you are asking for nearly double the number of pixels to be rendered.
Set pitool to 1 and MRR to 16384 (to remove the limiter), then adjust from there
If you think setting the render resolution to 4096 gives you the best result then thats great for you, but just be aware that setting it to 4096 and then setting pitool to 1.5 has no effect because pitool at 1.5 will be a massive resolution, but steam will only let you render 4096 regardless, so pitool at 1.5 is having no effect.
Its like saying “my car drives best when I have a speed limiter set to 70mph, but then I can’t drive at 150mph, WTH!”
PiTool Render Quality 1.5 and maxRecommendedResoolution 8192 & 16384 is nothing I recommend, not even with a 2080Ti. Just put PiTool RQ at 1.0 and do the test with maxRecommendedResolution values again.
With ED I tested PT 2, SVR fixed 0.25, PP on, maxRR 17064 on SN203 5K+ and it looked amazing. maxRR was partly based on what @industria suggested hehe ![]()
Ran at 30FPS on a 2080 Ti in stations so not practical. But the visual difference was very clear to me.
Oct 2019 post: https://community.openmr.ai/t/best-quality-settings-for-steamvr-ive-found/22614/48?u=octofox
I gave up on it. Basically spedning 2 days i could finally see some changes in fps drops / hanging application and completely brocken HL:A in big FoV mod, but no quality improvements. Its possible half life is already very beautiful and there are just no improvements left for the obvious difference, or my graphic card is low (1080ti), or anything else, im just out of ideas. At this point i wont advise to anyone changing their configs and going above 4k with HL:A, as it works and looks better on defaults. For the rest of games it might be different as well. Thats why we need this ‘all in one’ configuration tool they are working on 
Its so frustrating that people do weird stuff like setting a SuperSampling to 2.0 or other similar crazy stuff. Its like running games with more than 8K resolution… and they do it with 1080 and then complain there is something wrong with the headset.
There is literally no GPU that can run that. Not even upcoming 3090TI.
No one forces you to visit this threads and read players feedback. Wait for your order, make your own conclusions and get out of this thread please. Pitool is literally forcing different and weird resolutions even with base ss of 1.0. This sh1t comes from pitool initially and we endusers just want to find out why this happens and why it has no effects, thats all. No one expects to play with 8k resolution, but we did expect to see at least 1 frame and be able to compare it with 4k.
sounds not so nice. industria, i just don´t know what there is that is so difficult to understand. sweviver and many others did explain to you the logic behind the ss settings more than once. for whatever reason you seem to dismiss all that and now you state “this sh1t comes from pitool”?
I agree that we do need easy settings for beginners or some who do not want to tweak.
But i for gods sake love to have all the options. And you do not need to be a scientist to understand it.
Good thing were not running full 8k. We are running Half. 8k UHD has been ran at 30fps on 1080ti and the old Amd Vega Frontier Edition.
I totally agree the configuration tool will be a great thing for Pimax. Ease of use is always going to be a huge factor to the success of VR. It’s the reason I believe PS5VR will do so well. They’re talking eye-tracking, wider FOV, 3d audio, high resolution screens, finger tracking, wireless, etc. All of those things in an easy to use package that you just turn on and play is what it will take for better adoption of VR. If Pimax can pull off a simple to use experience for PC users, it will definitely give it some longevity within the vr space.
Yep. 120° wide FoV I believe. This will force pcvr headsets to bring prices down.
For the reason i have mentioned before, but you missed it. When you setup your 8kx, this are defaults:
This is how it starts:
This is the resolution which you see if move the slider to steamvr recommended

If you set to ‘auto’ it will be again a different one.
And this is native resolution from native spec: 3840 x 2160
Dont you see the difference? And then you start moving these sliders up and down with no visible change, and your fps is not changing. Still dumb users doing sh1t? Or maybe its just pitool being not very userfriendly doings its own sh1t? Or maybe its steamvr with his limitations by default which not everyone knows about? It takes time understand this things and its not possible if we dont try and dont discuss this.
Nothing wrong with people being confused by resolutions, its not users fault. Im not going to tolerate people like [Kamppis] coming here and being frustrated to read our investigations. That was he being rude, not me.
This is SteamVR! Steam are stupid, or ignorant for wide FOV Headsets.
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.
Difficult?
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.
True. This is why we must have faith in @sweviver to program magic NewPitoolsExperience ![]()
the coloured DAU Interface ![]()
sorry, think only German understand…
