Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.3.0a10
2019.3.0b3
2020.1.0a1
Issue ID
1183762
Regression
Yes
[URP] [Regression] CommandBuffer name is always CommandBuffer.Execute on FrameDebugger
Steps:
1. Open attached project
2. Open repro scene
3. Hit play
->Game View is black, which is expected
4. Open frame debugger, enable it
->At the bottom of the list, find CommandBuffer.AfterEverything
->Observe the item name under CommandBuffer.AfterEverything
Expected: The name is myTest
Actual: The name is CommandBuffer.Execute
Reproducible: 2020.1.0a4, 2019.3.0b3
Not-reproducible: 2019.3.0b2, 2019.3.0a11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment