![]() I dunno why it's finiky like this, but I just spent like 30 minutes trying to get it to work on my end.ģ. To attach the debugger to unity:Ī) Enable debug mode in unity by clicking the lil' bug symbol in the bottom status barī) in vscode, click ctrl-shift-p to bring up the command plane, type in "Unity attach debugger" and select your instance of unity.Ĭ) Wait a while (few mins) and if it doesn't work, try it again till it does. I dunno if the launch options for vscode are working any more, but I can confirm the "attach to unity" still works (although it's finicky / takes some time / may need to trigger it multiple times for it to work). However, if you want to use the debugger you need to force vscode to install the depreciated extension, I think you can do that by going to the webpage and clicking install on the page:ĭebugger for Unity - Visual Studio Marketplace I missed that OP was having trouble installing the extension, I thought they were just asking for an alternative to the extension: The answer to which is no, there is not. (Did a small trial in my project by blasting away the extension, restarted ominsharp in vscode, and still gotz my intellisense)Ģ. ![]() It's the files themselves that hook into omnisharp tho, I don't think the package actually has any active elements/ you could remove the package once you've generated the files. The vscode package for unity, afaik, only helps with regenerating project files for vscode. Didn't mean to come off as rude, sorry about that mate.ġ. I'm sure you have helped a lot of people man.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |