Hi,
I just downloaded new behavior package and I started to work with it. But I encountered a weird bug. When I click “inspect script” button in the inspector, it opens a visual studio code page, but there is not any single line of code, just a blank page. I can not edit script on built-in action nodes like"talk" or “patrol”. Could anybody help me about solving this problem?
Thanks for reaching out!
Firstly, I want to mention that the built-in action nodes in Behavior cannot be modified directly. The purpose of the “Inspect script” button is to allow you to see the code behind these nodes and learn from them. This is not specified in the documentation yet, so I’ll make an internal ticket to add that details to a future release.
However, it seems that you are encountering an issue where the project file is not opening correctly in your IDE. I believe this could be related to either a project incomplete configuration, your development platform or the IDE you are using.
In order to assist you further, could you please go through the following steps:
- Check if you have the Visual Studio package installed in the package manager (
com.unity.ide.visualstudio
). This is necessary for proper integration between Unity and Visual Studio Code. - In Unity menu
Edit > Preferences... > External Tools
. Ensure that the Generate .csproj files options are enabled:- Embedded packages
- Local Packages
- Player projects
- If even after the above you still get the issue, could you let us know the version of Visual Studio Code you are currently using? Along with your current developing platform (Windows, Linux, Mac)?
Thank you for your patience and for bringing this to our attention
I see, thank you for the quick response. I checked your steps, but I can not enable “Player projects” checkbox and I do not know why.(I checked app permissions also). My developing platform is Mac, my unity version is 6000.0.20f1 and my visual studio code version 1.93.1. Also I installed “com.unity.ide.visualstudio” package.(ver.2.0.22) I updated everything related and problem still continues.
Mmmh, sounds like a bug then. I’ll share here this thread that discussed similar issue.
If the issue persist, I would recommend opening a bug report so the appropriate team can investigate.
Hope this helps
I think you need com.unity.ide.vscode
for visual studio code Although it looks like it’s no longer supported