You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using HDR lightmaps, mipmapping gets turned off on the material (probably lack of Pemrem support?) This causes flicker in VR and rough crunchy textures at a distance on desktop.
To Reproduce
Steps to reproduce the behavior:
You can go into this scene which has samples of both types of lightmaps labelled and see the difference. If you look at the HDR versions from a distance you should see noisy textures on PC and flickering on VR. If you look at the 8 bit lightmaps from the HDR side you'll notice bleeding of the color swatches as mipmaps show up. You won't see this on the HDR side. https://hubs.mozilla.com/cFQbjE5/twin-tattered-outing
Expected behavior
Assuming it is possible to setup mipmaps for the HDR texture those should be generated at runtime so that flickering in VR does not occur. Here is an example of how that is done in Three.js. https://threejs.org/examples/webgl_materials_envmaps_hdr.html
Screenshots
Desktop (please complete the following information):
OS: PC and Meta Quest 2
Browser Chrome, Quest2 browser
Version chrome Version 106.0.5249.119 and latest Meta Quest2 Browser
Smartphone (please complete the following information):
Describe the bug
When using HDR lightmaps, mipmapping gets turned off on the material (probably lack of Pemrem support?) This causes flicker in VR and rough crunchy textures at a distance on desktop.
To Reproduce
Steps to reproduce the behavior:
You can go into this scene which has samples of both types of lightmaps labelled and see the difference. If you look at the HDR versions from a distance you should see noisy textures on PC and flickering on VR. If you look at the 8 bit lightmaps from the HDR side you'll notice bleeding of the color swatches as mipmaps show up. You won't see this on the HDR side.
https://hubs.mozilla.com/cFQbjE5/twin-tattered-outing
Expected behavior
Assuming it is possible to setup mipmaps for the HDR texture those should be generated at runtime so that flickering in VR does not occur. Here is an example of how that is done in Three.js. https://threejs.org/examples/webgl_materials_envmaps_hdr.html
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
You can see that three.js can support generating Mipmaps for HDR by checking out this example... https://threejs.org/examples/webgl_materials_envmaps_hdr.html
The text was updated successfully, but these errors were encountered: