Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0b8
Issue ID
1006282
Regression
No
[VSTU]: Using enum flags displays "Node not supported
How to reproduce:
1. Open user attached project and open Scenes/SampleScene.unity
2. Execute "Assets > Open" C# Project
3. Add breakpoint to NewBehaviourScript.cs at line 19 (Debug.Log)
4. Attach Visual Studio to Unity, switch to Unity and press Play (Visual Studio should now hot the breakpoint and halt)
5. Execute in VS "Debug > Window > Watch > Watch 1" to open the Watch window
6. Add "flags" to Watch window (without quotes)
7. Add "MyFlags.A | MyFlags.B" to Watch window (without quotes) (Observe the Watch window displays the value of "flags", but does not display the value of "MyFlags.A | MyFlags.B".)
Actual result: Using enum flags displays "Node not supported
Expected result: Using enums in the Watch window should properly display the value.
Reproduced with: 2017.3.1p2, 2018.1.0b9, 2018.2.0a2
Tested on: VS 15.5.7, VSTU 3.5.0.3
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note:
This is an issue with Visual Studio / Visual Studio Tools for Unity (VSTU). Please report the bug to VSTU team at vstusp@microsoft.com