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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment