Search Issue Tracker
Feature Request
Votes
0
Found in [Package]
2.0.0-pre.11
Issue ID
AVPB-804
Regression
No
Polyspatial load custom shader Error from Remote Addressable bundle
Reproduction steps:
1. Open the attached “LoadProject“ from the “CustomShaderBug.zip“ archive
2. Open the “Assets/Scenes/loader.unity“ Scene
3. Enter the Play Mode
4. Observe the Game View and the Console
Expected result: The Sphere seen in the Game View is red and no errors are seen in the Console
Actual result: The Sphere is black due to shader errors seen in the Console
Reproducible with: 2.0.4 (6000.0.27f1, 6000.1.0a4)
Reproducible on: RealityKit on Editor
Not reproducible on: No other environment tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ”Last item reached” warning is thrown when no search results are found in UI Toolkit Layout Debugger
- UI Elements overlap in the Shortcuts window when docked and resized to a smaller window size
- UIBuilder DataSourcePath dropdown fails to show properties when binding to abstract classes
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
Resolution Note:
Hello,
On Vision OS we do not currently support shaders in asset bundles because shaders in VisionOS must be represented as MaterialX rather than compiled shader bytecode.
You can reference shaders that come packaged in your game build from an asset bundle. We have logged your interest but also recommend that you submit an idea here: https://portal.productboard.com/unity/77-unity-visionos-roadmap/tabs/272-mr-immersive-features as a feature request on the roadmap so others can vote for it.