however, the fount is not changing for “using UnityEngine.UI;” or “’ public Slider[ ] val;” and the auto fill is not finding them ether
not sure what broke.
any one know were i should look to fix VS ?
(using VS 2022 and unity 2022)
This may help you with intellisense and possibly other Visual Studio integration problems:
Sometimes the fix is as simple as doing Assets → Open C# Project from Unity. Other times it requires more.
Other times it requires you also nuke the userprefs and .vsconfig and other crufty low-value high-hassle files that Visual Studio tends to slowly damage over time, then try the above trick.
Barring all that, move on to other ideas:
Also, try update the VSCode package inside of Unity: Window → Package Manager → Search for Visual Studio Code Editor → Press the Update button
“Other times it requires you also nuke the userprefs and .vsconfig and other crufty low-value high-hassle files that Visual Studio tends to slowly damage over time, then try the above trick.”
that is looking to be the case, I guess i want to delete the files with unity closed and let the editor remake them when opening the project ?
lol no to note pad, I still want convenance futures like right clicking a object and selecting “go to definition” to jump to the CS file with the script
that said i can open new project to find VS is just fine, so my problem is pacific to my project
(if that helps narrow down things to try)
well now i know the problem is constant with any new script i make, but all old scripts are fine
notice start is not recognized on the new script I don’t know how to fix this
Once the solutions linked to by @Kurt-Dekker have failed you’re largely in uncharted territory. If you haven’t tried it already I’d delete the Library folder. If that fails and you’re using version control you could try checking out previous versions until you reach the most recent functioning one and determine what changed.
You mentioned that new projects work so if none of that works or if you’re not using version control the worst case solution would be to export the assets from your project and import them into a new project.
those parts I tried, moving them almost seemed to work but i may have moved too much as it stoped after the fact
i my double check that soon, maybe import my stuff as a package instead of using file explorer
I am using version control with plastic but i went a while with out looking at scripts so that could set me back a lot
one thing I thought about is that I had this project as a 2019 project that was updated to 2022. looking at that it is likely that any script i made in 2019 works and any new script made in 2022 is messed up.
one asset requires project setting import, import fails due to searching the file path of the original project.
so I re import that from the package manager (VS works)
then I import its project settings replacing 3 files it successfully imports (VS stops working)
so yeah i don’t know what would brake the link to VS in those files (I dint remember what they are called now lol )
but now I know were the heart of the problem is, I will contact the asset creator and see if we can fix the problem in the original project (so i do not have to reset up plastic lol)