Search Issue Tracker
By Design
Votes
14
Found in
2019.4
2020.2
2021.1
2021.1.0b6
2021.2
Issue ID
1318622
Regression
No
No lighting is received when Mesh is drawn with CommandBuffer.DrawRenderer in Build
How to reproduce:
1. Open the user's attached "Missing lighting.zip" project
2. Go to File -> Build And Run
3. Observe the Character's lighting in the Player
Expected result: Character drawn with CommandBuffer.DrawRenderer receives lighting
Actual result: Character drawn with CommandBuffer.DrawRenderer doesn't receive any lighting
Reproducible with: 2020.3.0f1 (10.3.2), 2021.1.0b10 (11.0.0), 2021.2.0a7 (12.0.0)|
Could not test with: 2019.4.22f1 (7.5.3) - Due to errors downgrading
Note:
- The issue is not reproducible in Play Mode
- The issue is reproducible with Direct3D11, Direct3D12, Vulkan Graphics API
-
PatrickBrightrock
Mar 08, 2021 11:18
Yes, please!
-
strich
Mar 08, 2021 11:05
This is a showstopper for our project. :(
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
CommandBuffer.DrawRenderer does not interact with any lighting, by design.