You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During debugging in VSCode, when hovering over variables of type Node, I only see the object's ID instead of detailed information about the object. This issue seems to be inconsistent, as I created a copy of the project with a new name and removed the .godot folder, and everything worked correctly again.
However, when I removed the .godot folder in the original project and restarted both Godot and VSCode, the issue persisted.
This may be difficult to reproduce easily, but perhaps someone else has encountered a similar issue and can provide more information.
Expected behavior: Hovering over node variables should display detailed information about the object.
Godot version
v4.3.stable.official [77dcf97d8]
VS Code version
1.93.1 (Universal)
Godot Tools VS Code extension version
2.2.0
System information
MacOs 14.6.1
Issue description
During debugging in VSCode, when hovering over variables of type Node, I only see the object's ID instead of detailed information about the object. This issue seems to be inconsistent, as I created a copy of the project with a new name and removed the .godot folder, and everything worked correctly again.
However, when I removed the .godot folder in the original project and restarted both Godot and VSCode, the issue persisted.
This may be difficult to reproduce easily, but perhaps someone else has encountered a similar issue and can provide more information.
Expected behavior: Hovering over node variables should display detailed information about the object.
Actual behavior: Only the object ID is displayed.
Steps to reproduce
godotbuginstantiateexportsetter.zip
Steps to reproduce:
Open a project in Godot.
Debug main.gd script containing node type variables.
Set breakpoint on "pass"
Hover over the 'sprite_2d' variable in VSCode.
The text was updated successfully, but these errors were encountered: