![]() ![]() VScode now recognizes Unity Namespaces, and Intellisense offers suggestions. In my case, I changed the VSCode package in both from 1.2.4 => 1.2.3. ![]() After making the changes and restarting Unity, it will load the listed package version. Just make sure Unity and Unity Hub are closed. The files are Packages/manifest.json and Packages/packages-lock.json. I would caution people from quickly jumping in there and playing around of course, and it probably shouldn't be the first tactic to solve an issue, but if you're mindful and know which packages you need, it's fairly simple. Today, though, I remember that you can actually revert Unity Packages manually, by editing two json files Unity uses to keep track of which packages are in the project. So, as I implied, I was suspecting that Unity's Package for VSCode was likely behind the issue, but I was thinking I was unable to revert to the previous version because it's not possible through the Package Manager. I doubt this will be the solution to many others who may be dealing with similar issues, but just in case, or to get you thinking about different solutions, I'll mention it here. HOWEVER, I did manage to finally nail down, and solve, the problem. Thank you, Kurt, but yes, I also tried these, and to my surprise, they also weren't the solutions. Unity Package: Visual Studio Code Editor 1.2.4
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |