Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2018.4
2019.4.1f1
2020.2
Issue ID
1264605
Regression
No
CommandBuffer.EndSample Intellisense comment is identical to CommandBuffer.BeginSample
How to reproduce:
1. Download the user-submitted script(FloorCutoutCommandBuffer.cs)
2. Create a new Unity project, import and open the script
3. Hover over the CommandBuffer.BeginSample(line 55) and then CommandBuffer.EndSample(line 67)
Expected result: CommandBuffer.EndSample tooltip comment is unique and describes its functionality
Actual result: CommandBuffer.EndSample tooltip is identical to CommandBuffer.BeginSample
Reproducible with: 2018.4.26f1, 2019.4.7f1, 2020.1.1f1, 2020.2.0a20
Comments (1)
-
mariah9xx
Sep 28, 2022 07:18
Thanks, I got it back. There are some problems, you should leave the video will be more convenient.
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a3