I have just updated to Unity 2019.2.5f1 and VSCode now works perfectly!
Iām on 2019.2.5f1 and it worked for a bit but now it wonāt even attempt to load VSCode at all.
hello,
well all your problems comes while you did not update the VSCode plugin in Packetmanagerā¦
Do it and no need for other stuffā¦ the VSCode plugin is deprecated and not needed if you update via Packet managerā¦ best delete this old VSCode plugin from Editor folderā¦ it works super withoutā¦
looks like Unity is focussing more on Windowsā¦ hence the late fixes for iOS and Macā¦
iām using UE4 on my Mac tooā¦ once i get my stuff working in UE i say goodby to Unityā¦
iām user from Version 1 where it was Mac onlyā¦ iām sooooo disappointed by Unityā¦
they even donāt do good beta testing anymoreā¦ let the User do it its much cheaper
look @ the last version of 2019.2 ā¦ itās so buggy and output to Android & iOS tooā¦
since we donāt get money for the time we spent searching bugs or discovering bug and take the time to document themā¦ No Thank you nothingā¦ and maybe it get fixed mayyyyyyybeeee
Unity had much better times as you see here in the forumā¦
itās rare if you get a answer to your questionsā¦ no Unity peeps are here in the forumā¦
if you have a problemā¦ support doesnāt existā¦ you can also not mail the problemā¦
and than they ask our community whatās upā¦ why you donāt submit games and apps for our campaigns ā¦
loooool because UNITY3D doesnāt care anymore whatās up under the developerā¦
Unity3d is now too bigā¦ they lost focus on quality and functionality ā¦
they care now more for high end games that make 5% of the Unity userā¦ only for marketing LOL
they should better do there homework and focus what the mass needs ā¦
a stable working editor on all platforms that are supportedā¦!
@ Unity3d
Do your homework we pay you for this!!!
and focus on quality not on features only 1-5% of the user want !!!
M.
Iāve updated my project from 2019.1 ā 20192.6f1 and can no longer open the project from the editor (by clicking the scripts). When I open a script it openās it singularly. I have the latest VSCode package from the package manager and itās set in the preferences (external tools) but still no luck. Using Windows 10
the guy above me is an idiot
and you a noob who has no ideaā¦
just wonder if you have a license or use a illegal versionā¦
This helped me, thanks a million!
Also having this issue on 2019.2.6f1 using the 1.1.2 VS code package. Iāve tried opening the project, opening via file extension, deleting the vs code settings, reinstalling vs code, and a few other things to no effect. Currently trying to nuke my library in case thereās some weird cached state issue.
There is currently an open ticket for the 1.1.0 package:
Hopefully weāll hear more about this soon.
as annoying as it is, the easiest solution for right now if you want to use code is to open code before you start unity. now, when you click on any script inside of unity, it will open in code as usual. just put your shortcuts right next to each other. iām sure they will make a fix eventually.
Canāt open a single file via VSCode on Unity 2019.2.6 (Windows 10). Have to switch to Visual Studio for now. Updating the packages and other stuff mentioned in the thread didnāt help.
Canāt believe that could be a problem with a stable version (even after a few updates).
heres the fix for now.
This was driving me crazy on a Mac!
Edit: NOT a solution: go to the Unity>Preferences>External Tools>External Script Editor and set it to āOpen by file extensionā. Also checked is Generate all .csproj files.
Now, make sure your Mac is set to open .cs files using Visual Studio Code and it should work, opening the specific file when double-clicking in the Unity Editor.
Edit: The above works, sort ofā¦ The file opens, but now I get this error in the Editor:
MissingMethodException: Attempted to access a missing method.
Unity.CodeEditor.CodeEditor.OSOpenFile (System.String appPath, System.String arguments) (at /Users/builduser/buildslave/unity/build/Editor/Mono/CodeEditor/CodeEditor.cs:157)
UnityEditor.DefaultExternalCodeEditor.OpenProject (System.String path, System.Int32 line, System.Int32 column) (at /Users/builduser/buildslave/unity/build/Editor/Mono/CodeEditor/DefaultExternalCodeEditor.cs:117)
Unity.CodeEditor.CodeEditor.OpenProject (System.String path, System.Int32 line, System.Int32 column) (at /Users/builduser/buildslave/unity/build/Editor/Mono/CodeEditor/CodeEditor.cs:31)
Iām getting a similar error, but mine seems to be related to a faulty lock file. This is just a guess on my part. My magical, hacky workaround anytime it wonāt open vscode has been to:
- Restart computer.
- Run
git clean -fxd
since Iām in a git repo (should delete any ignored files/clear library cache) - Reopen project and wait for unity to rebuild everything.
One thing to note is that Iām on windows fast ring (18990) --so perhaps the folder permissions are bugged from my windows update.
I encountered this issue a few days ago after upgrading to Unity 2019.2.6f1 and just fixed this by removing the āVisual Studio Code Editorā package from the package manager and then reinstalling it.
It doesnāt seem to be having any issues opening different files from inside Unity anymore, so hopefully this solution works for others.
Edit - This is on a Mac, but hopefully this extends to other platforms as well
does it happen after a restart of Unity?
visual studio code 1.38.1 will no longer open my main project from unity 2019.2.8f1. it worked earlier today. but now visual studio code simply rejects it. visual studio code WILL open a different project that i saved yesterdayā¦
on the borked project, clicking on links from unity to the source or trying to manually open the project in vs code does not work any more. rebooting/closing/removing/reinstalling vs code package in unity does not help. amazing.
ā¦and it randomly started working again today. something is fishy but at least it is working again.
ā¦ and it randomly stopped working again today. i think it could be visual studio code being weird, as i diffed the slns and nothing looked visibly wonky
Have the same problem on Windows and 2019.2.8f1
This is another one of those things that I canāt believe Unity doesnāt fix or at least acknowledge immediately. code seems so much better suited for unity than vs, I donāt get it.
Hello! This issue is currently being investigated, you can find more information and a workaround on the IssueTracker: Unity Issue Tracker - [VSCode] A Script fails to open when External Script Editor is set to code.exe