Search Issue Tracker
Active
Under Consideration for 1.2.X
Votes
0
Found in [Package]
1.2.3
Issue ID
XRVOSB-49
Regression
No
[visionOS] Assertion failed errors are thrown in Xcode when Spatial-Temporal Post-Processing is enabled
Reproduction steps:
1. Open the attached “Repro“ project
2. Build the project on “visionOS” platform (File > Build Profiles > visionOS > Build)
3. Run the build on an Apple Vision Pro device or visionOS simulator
4. Observe the Xcode console
Expected result: Build runs fine, no errors in the Xcode console
Actual result: Build doesn’t run (black screen) and a failed assertion error is present
Reproducible with: 1.2.3, 2.0.0-pre.3 (6000.0.11f1)
Reproducible on: VR on visionOS 1.1 Simulator - built using M1 Max MacOS 14.5
Not reproducible on: No other environment tested
Notes:
- With the Spatial-Temporal Post-Processing on, and GPU Resident Drawer with GPU occlusion off, the error is:
”validateComputeFunctionArguments:1132: failed assertion `Compute Function(computeMain): Non-writeable texture format MTLPixelFormatRGB10A2Unorm is being bound at index 4 to a shader argument with write access enabled.’”
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