Search Issue Tracker
Fixed
Votes
1
Found in
5.4.0p3
Issue ID
826896
Regression
No
‘Node not supported’ error when adding an enum to int cast in VS tools for Unity
Steps to reproduce:
1. open user's attached project
2. open scene "Scene"
3. open Assets/Scripts/MyClass.cs in Visual Studio
4. place breakpoint at line 18, where the Debug.Log is located
5. attach Visual Studio Debugger to Unity
6. switch to Unity and press Play
7. when the breakpoint is hit, execute in Visual Studio Debug/Windows/Watch/Watch 1
8. insert (int)Fruit to the Watch window
Expected behavior: (int)Fruit value is 1 (VSTU should be able to display an enum to int expression properly)
Actual result: (int)Fruit returns an error "Node not supported '(int)Fruit'"
Reproduced with: 5.5.0a6, 5.4.0p3, 5.3.6p2
Not reproduced with: 5.2.5f1 (for some reason breakpoint is not reached in this version)
Note:
-when run in Visual Studio as .NET Console Application (see user's attached file "ConsoleApplication1.zip") no error is shown
-please have a look at user's attached videos
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Add comment