Search Issue Tracker
Duplicate
Votes
0
Found in
5.5.0a3
Issue ID
813719
Regression
Yes
The Courtyard project displays two shader errors in 5.5.0a3 on import, project cannot start
The Courtyard project displays two shader errors in 5.5.0a3 on import, project cannot start.
1. What happened
Imported The Courtyard project and saw that it has (in addition to missing textures) two new errors that prevent it from starting.
2. How we can reproduce it using the example you attached
- Download/import The Courtyard (or open the attached) project;
- Load the scene and notice that due to the Shader errors the project cannot start.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
This is a duplicate of issue #803295