Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.2p2
Issue ID
968271
Regression
No
Custom Shader breaks on Player with mixed lighting
To reproduce:
1) Open attached project and "test" scene
Optional: Rebake lighting (it should be already done)
2) Build and run
Expected vs Actual: Compare Editor and Player. Player is heavily corrupted.
Doesn't happen if Baked Data is cleared
Reproduced in 2017.1.1p2, 2017.1.2p3, 2017.2.0p2, 2017.3.0b9
Not reproduced in 2018.1.0a1
Tested on Win Standalone and WebGL, corruption happened in both platforms
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