I am reaching out with a question regarding poor image quality in VR. We are currently using the Valve Index headset, which is supposedly one of the best resolutions available on the market. However, when I export an .exe file and run it, the quality is quite poor. It almost doesn't matter if I set it to Ultra HD resolution - it still definitely doesn't feel like HD. It goes smooth so I assume it's not a hardware issue, but just blurry and pixelated. I don't have this issue with the same headset on other software or games. Any ideas what might be wrong?
Poor image quality in VR
- antoniovachev
- Thread is Unresolved
-
The image quality is fine - you're seeing the pixels on the screens. The resolution of the Valve Index is 1440 x 1600 per eye.
Check out the HTC Vive Pro. 2880 x 1600 at 615 pixels per inch.
-
Vive Pro is the same at the Index, 1440 x 1600 per eye
Vive Pro 2 is 2448 x 2448 per eye
You'd best have a 3080 or 3090 if you go w/ Vive Pro 2. Our 2080 Ti seemed to struggle with it w/ Enscape. The framerate tradeoff wasn't worth it.
Is the IPD adjustment on the headset set right for you? Play with the resolution/scaling settings in Steam VR. Have you tried different/simpler Enscape scenes with the same results? Enscape is doing a lot of optimization on-the-fly with heavy architectural models and honestly just never looks as good as a game or other experience designed specifically for VR.
-
Another tip - set the quality in VR to high rather than ultra. Enscape keeps rendering until the mouse stops moving. You'll notice if you look closely at something reflective while slowly moving the mouse, it's not quite fully rendered until you stop moving the scene.
The challenge is in VR your head is the mouse in your head can never stop moving. So Enscape struggles to finish rendering and you're always seeing this unfinished condition. If you drop the quality down to high, Enscape can render faster and the overall impression is better.
-
I am reaching out with a question regarding poor image quality in VR. We are currently using the Valve Index headset, which is supposedly one of the best resolutions available on the market. However, when I export an .exe file and run it, the quality is quite poor. It almost doesn't matter if I set it to Ultra HD resolution - it still definitely doesn't feel like HD. It goes smooth so I assume it's not a hardware issue, but just blurry and pixelated. I don't have this issue with the same headset on other software or games. Any ideas what might be wrong?
I know exacrly what you mean, I tend not to use it in presentations very often because of the poor quality,
I completely agree with Phil Read though your computer probably runs along quite smoothly when runnning Enscape normally doing 30-60fps, but consider that your VR headset requires min 80fps x 2 then you can understand that the image is not as good.
I personally would like to see baked textures option for VR this would vastly improve performance.
-
The image quality is fine - you're seeing the pixels on the screens. The resolution of the Valve Index is 1440 x 1600 per eye.
Check out the HTC Vive Pro. 2880 x 1600 at 615 pixels per inch.
How come whenever I run anything else (e.g. some games) on that same headset it looks crystal clear, but when I try to use Enscape it's horrible? It's surely something to do with how Enscape itself handles the rendering, rather than the resolution of the headset itself, which should definitely be better than the image I am currently getting.
-
I am reaching out with a question regarding poor image quality in VR. We are currently using the Valve Index headset, which is supposedly one of the best resolutions available on the market. However, when I export an .exe file and run it, the quality is quite poor. It almost doesn't matter if I set it to Ultra HD resolution - it still definitely doesn't feel like HD. It goes smooth so I assume it's not a hardware issue, but just blurry and pixelated. I don't have this issue with the same headset on other software or games. Any ideas what might be wrong?
When making use of Enscape VR, please also make sure that DLSS is disabled if you have a card that supports this functionality:
DLSS is great when Enscape is viewed on a normal monitor, but with a VR headset the screen is so close to the eyes that its shortcomings become too obvious.
-
I believe I can reproduce the issue if I try to connect to an unconnected VR headset. This is ultra quality on desktop, before trying to connect:
But, while trying to connect, in high or ultra rendering quality, I get this:
I'm pretty sure this is the same noise I get thru the VR display. But then it's even worse, since the noise is different for each eye and changes with every move. It's simply unwatchable for more than a few seconds.
If I lower the rendering quality to medium, the noise is gone:
But light and glass reflections drop quality significantly (glass reflects the exterior, not the interiors!) what makes the tool too expensive for the results.
It boils down to one question: Why the noise?
nVidia drivers: 528.49 (2070 Super)
Windows 10 x64
Oculus Quest 2
Enscape v3.4.4.94564.
-
It boils down to one question: Why the noise?
It probably comes down to the size/detail of the scene or geometry in combination with the amount of VRAM and render quality. If you copy/paste a portion of the scene into a new file, do you get the same noise? What about a really simple scene? (like just a box.)
-
Manolchen the noise is more visible in VR due to performance constraints: We have to trace less rays for indirect lighting and cannot use the same quality denoising. However we've completely overhauled how this work for 3.5. You might want to try and test the Preview version:
