Search Issue Tracker
Fixed
Fixed in 2.0.12
Votes
8
Found in [Package]
2.0.12
Issue ID
VS-62
Regression
No
Fixed-size Buffer values in debuggers are incorrect
Fixed-size Buffer elements in the Visual Studio and Rider attached Unity debuggers are incorrect, except for the first Buffer value
Reproduction steps:
1. Open the attached project "FixedBufferTest.zip"
2. Open Project Settings -> Player Settings -> Other Settings and allow 'unsafe' code
2. Notice that "12 34 56 78" is being logged repeatedly in the Console
3. In the Assets folder open "FixedBufferTest.cs" script
4. In the Visual Studio top menu select Debug->Attach Unity Debugger and select the Unity Instance
5. Go back to Unity Editor and in the pop-up click "Enable debugging for this section"
6. Go to the script again and in Debug window local variables select foo->Buffer
7. Notice the Buffer values
Expected result: The Buffer values in the debugger are the same as logged to the Console ("12 34 56 78")
Actual result: The Buffer values in the debugger are different than in the console (except the first Buffer), for example - "12, 12260, \[...]"
Reproducible with: 2019.4.32f1, 2020.3.32f1, 2021.2.18f1, 2022.1.0b14, 2022.2.0a9
Reproducible with:
Visual Studio Editor package 2.0.14 with MS Visual Studio 17.1 (with the latest Visual Studio Tools for Unity installed)
JB Rider editor package 3.0.13 with JB Rider 11.0.12
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
- Win64 CPU is set to None when applying changes to plugin where the meta has the serializedVersion 2
- Sprite Atlas textures from all included build scenes persist in Editor memory when building the Player
- Disabling all columns in Light Explorer throws “ArgumentException” error in the Console window
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
Resolution Note (fix version 2.0.12):
This issue is fixed in Microsoft Visual Studio 17.6.4