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
- Render Pipeline Converter selected asset counter reports one fewer item when using manual selection
- [Android] [Adreno] [WebGL] A light cookie is not rendered with shader compile error when WebGL build is launched on a device with Adreno GPU
- Rigibody sliding over a flat surface that is made of several GameObjects detects false collisions when Collision Detection is set to "Continuous" or "Continuous Dynamic"
- UI Toolkit Label height is incorrectly calculated when using max-width with percentage value
- Visual Effect Material causes Scene view to update continuously when both Scene and Game views are open, despite "Always Refresh" being disabled
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