Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
Issue ID
1274452
Regression
No
[Crash] Color space uninitialised can be set via C# script but built standalone player will crash
Steps
1.Switch to color space uninitialised (using C# editor script, like attached example)
2.Save project (to ensure serialized changes on disk)
3.Build project
Expected:
- No build
- Error or auto-switch away to Gamma or Linear color space
Actual:
- Build starts and finishes
- Built player crashes on start
Repro: 2020.2.0a21
Workaround: do not set color space to uninitialised via C# script
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment