Search Issue Tracker
Fixed in 5.5.0f3
Votes
0
Found in
5.4.0b23
Issue ID
812374
Regression
No
CommandBuffer DrawMesh not applying material keywords in standalone builds
Steps to reproduce:
1. Open project
2. Open Frame Debugger window
3. Play in editor and enable Frame debugger
4. Navigate "Camera.Render/Drawing/CommandBuffer.../Deferred pipLights/Draw Mesh" in Frame debugger
-- Notice shader's material keyword "Hidden/pipLight/Light pass #0 POINT SHADOWS_CUBE UNITY_HDR_ON" (This is expected behaviour)
5. Build a development build with auto connect profilers enabled
6. Enable frame debugger
7. Navigate "Camera.Render/Drawing/CommandBuffer.../Deferred pipLights/Draw Mesh" in Frame debugger
-- Notice that shader has wrong material keyword "Hidden/pipLight/Light pass #0 POINT UNITY_HDR_ON"
Results: CommandBuffer DrawMesh not applying material keywords in standalone builds
Reproduced with: 5.4.0b23, 5.4.0b25, 5.4/staging (0975e5a4bcaa)
Additional notes in last edit.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
Add comment