Search Issue Tracker
Fixed
Fixed in 2.0.4
Votes
0
Found in [Package]
2.0.0-pre.11
Issue ID
XRVOSB-61
Regression
No
[AVP] Bloom is not applied when Foveated Rendering is enabled on visionOS
Steps to reproduce:
1. Open the attached user's project "MetalSampleVisionOS.zip"
2. Switch to VisionOS Platform
3. Open XR-Plugin Management and Apple VisionOS plugin settings
4. Make sure App mode is in "Metal Rendering with Compositor Services" and Foveated Rendering Enabled
5. Build Xcode project and to a AVP device
6. Observe Bloom is not applied to the cube
7. Disable Foveated Rendering and build again
Expected results: Bloom is applied
Actual results: Bloom is not applied when Foveated Rendering is enabled on visionOS
Reproducible with: 2.1.2 (6000.0.35f1, 6000.1.0b2)
Could not test on 1.3.11 (2022.3.56f1) due to errors in the project after downgrading
Reproducible with these devices:
Apple Vision Pro on VisionOS 2.2
Testing Environment: macOS 14.5
Not reproducible on: No other environment tested
Notes:
-Foveated Rendering is not supported on visionOS Simulator
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