Greetings,
i would like to know if you got the same weird recommendation as me (I have a pimax 8K with large FOV).
For a render quality set to 1 in Pitool (beta 121_R211), i can’t believe Steam vr is recommending only 58% with an RTX2080Ti and the latest drivers (nVidia 419.67).
Is that normal ?
Yep it is normal.
Large FOV have Large requeriments (and anything above 4096 pixels will be wasted).
It depends on your PiTool Render Setting, FOV size and Hz the Pimax headset is running at.
Latest Nvidia driver is 425. 31 wqhl, maybe give it a shot
Yes, that’s obvious but i was expecting a more solid SS with that hi end card. Was wondering if that was the expected range. Regarding resolution, above HMD resolution (4096) will produce a crisper/sharper image (far distance and textures details).
Thanks i’m downloading
That’s right. refresh rate is set to 80Hz and other values are in my first post:
Pitool Render scale : 1
Fov: large
Depends of the game engine too.
Unreal Engine for example, HATES anything above 4k (unlocking the 4096 limit will only make it erratic) and will crash at startup (something related to texture resizing).
While Unity Engine games scales very well.
But the 2080ti is a monster. It´s not her fault.
Could you check your vrcompositor.txt log file and post the GPU speed section? It should look like this:
****************************************** Begin GPU speed ******************************************
MeasureGpuMegaPixelsPerSecond(): Returning 875 MP/sec. Total CPU time 0.10 seconds.
GPU Vendor: "NVIDIA GeForce GTX 1080 Ti" GPU Driver: "25.21.14.1771"
GPU speed from average of 6 median samples: 882
HMD driver recommended: 3202x2633 90.0Hz HiddenArea(8.73%) = 1385 MP/sec
Raw ideal render target scale = 0.64
New render target scale = 0.64 = 2562x2106. Total CPU time 0.10 seconds.
******************************************* End GPU speed *******************************************
Ghanth
“That’s right. refresh rate is set to 80Hz and other values are in my first post:
Pitool Render scale : 1
Fov: large”
Given your settings - then the recommended render target would be about right. Remember, it is only SteamVR trying to suggest what would work at 80Hz - not that you might care for that speed given the low resolution to achieve such.
Try Normal FOV with PiTool at 1 or if you want speed fps/ then try Normal with Pitool at 0.75
Strange that at 100% in SteamVR Video, with PiTool at 1 you are getting that render target. Mine gives 7996 x 3904 with FOV at large, 4432 x 3904 at FOV Normal.
Using SteamVR Build 1.3.22, latest Hotfix Nivida Driver and latest PiTool.
Fri Apr 12 2019 13:56:42.017 - ****************************************** Begin GPU speed ******************************************
Fri Apr 12 2019 13:56:42.142 - MeasureGpuMegaPixelsPerSecond(): Returning 1011 MP/sec. Total CPU time 0.13 seconds.
Fri Apr 12 2019 13:56:42.167 - GPU Vendor: “NVIDIA GeForce RTX 2080” GPU Driver: “25.21.14.2511”
Fri Apr 12 2019 13:56:42.168 - GPU speed from average of 6 median samples: 1012
Fri Apr 12 2019 13:56:42.170 - HMD driver recommended: 4432x3904 64.0Hz HiddenArea(8.73%) = 2021 MP/sec
Fri Apr 12 2019 13:56:42.170 - Raw ideal render target scale = 0.50
Fri Apr 12 2019 13:56:42.170 - New render target scale = 0.50 = 3134x2761. Total CPU time 0.15 seconds.
Fri Apr 12 2019 13:56:42.170 - ******************************************* End GPU speed
Sure. Here it is:
****************************************** Begin GPU speed ******************************************
MeasureGpuMegaPixelsPerSecond(): Returning 1371 MP/sec. Total CPU time 0.10 seconds.
GPU Vendor: "NVIDIA GeForce RTX 2080 Ti" GPU Driver: "25.21.14.1967"
GPU speed from average of 6 median samples: 1361
HMD driver recommended: 7996x3904 80.0Hz HiddenArea(1.75%) = 4907 MP/sec
Raw ideal render target scale = 0.28
New render target scale = 0.28 = 4231x2066. Total CPU time 0.11 seconds.
******************************************* End GPU speed *******************************************I guess you have parallel projection on. I had it off. Just pointing out that we all forgot to mention that parallel projection option also have an impact on the final resolution.
It does but I need it on for Il2 so that could be it. Silly me.
it seems that the GPU speed section do not update itself accordingly to the current Pitool/SteamVR settings. Is that normal ?
That’s ok dude ! 
You helped in some ways. Regarding this thread, my initial confusion came from my intuitive personnal assumption that with Pitool’s render quality set at 1 and SteamVR’s SS set at 100%, we should get native HMD resolution (x2 4K). 
It’s not this way. 
Thanks for your detailed post. I learned something !
You are welcomed.
It took me a while to realise that we didn’t get native 4K resolutions per eye with the headset myself. Combinations of factors that I hadn’t considered but Lens distortion profiles wasn’t quite the culprit that some others thought.
Parallel Projection Compatibility (Stereo Image overlap) and IPD image adjustment keeping the image aligned with the lenses IPD adjustment though did though chew into available horizontal resolution.
Case crack issues aside, I think Pimax has really raised the bar for VR headsets.
Along the lines of this does any one know the ratio we should be looking for with the 5k+ when manually setting the steamVR SS settings. I notice when I was fooling with this setting that I would get major jaggies in fall out 4 VR with most resolutions since they were not at the proper size.
Wait, when did this start? I’m pretty sure the cap is at 8096. What’s up?
The cap is actually 4096.
We can go beyond, but it is bugged/experimental
