Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.1.1f1
Issue ID
1044030
Regression
No
PostProcessing V2 artifacts when changing renderViewportScale
The Ambient Occlusion effect within the PostProcessing Stack (V2) shows visual artifacts when changing the XRSettings renderViewportScale or eyeTextureResolutionScale.
Reproduction Steps:
1. Download the smaller project (see comments, below)
2. Power-on your VR headset
3. Build & Run, and experiment with the options:
- Press Fire1 to change renderViewportScale
- Press Fire2 to change eyeTextureResolutionScale
Observations:
Ambient Occlusion shows 'ghosting' issues with renderViewportScale changes, and causes big artifacts when eyeTextureResolutionScale is changed. This primarily happens under the Multi Scale Volumetric Obscurance mode, rather than Scalable Ambient Obscurance.
Reproducible in versions 2018.1.3f1, 2018.2.0b6.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment