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
- [Quality Hackweek] Activated Terrain Inspector is active only until the terrain GameObject is deselected when two or more Inspectors are open
- Physics Used Memory keeps growing when GameObject colliders are enabled and disabled
- Errors are thrown and Inspector's UI element is not drawing when a GameObject with script component using a List<T> attached is selected
- ConfigurableJoint's parameters are not saved in the Prefab after Runtime Prefab baking
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
Add comment