Сообщений: 3 • Страница 1 из 1
Редактор Visual studio не показывает ошибки [решено]
NOVA 18 сен 2022, 18:05
Не показывает ошибки в коде. Типа двойное объявление переменной, грамматические ошибки, пропуски точки запятой. То есть вообще ничего не показывает, пока скрипт не откомпилируется в unity. И ошибки уже видно в консоли.
Как быть?
Последний раз редактировалось NOVA 18 сен 2022, 19:54, всего редактировалось 3 раз(а).
-

NOVA - Адепт
- Сообщения: 1673
- Зарегистрирован: 17 май 2011, 11:45
- Откуда: Дядя Саша from Mother Russia
Re: Редактор Microsoft visual studio 2019
1max1 18 сен 2022, 19:28
preferences — ex. tools. — ex. scr. editor — vs 2019
-

1max1 - Адепт
- Сообщения: 5281
- Зарегистрирован: 28 июн 2017, 10:51
Re: Редактор Microsoft visual studio 2019
NOVA 18 сен 2022, 19:52
Спасибо. Заработало.
Подробнее:
Unity -> Edit -> Preferences -> External tools -> Visual Studio Community 2019 [16.11.16]
Всё закрыть и заново открыть.
-

NOVA - Адепт
- Сообщения: 1673
- Зарегистрирован: 17 май 2011, 11:45
- Откуда: Дядя Саша from Mother Russia
Сообщений: 3 • Страница 1 из 1
Вернуться в Почемучка
Кто сейчас на конференции
Сейчас этот форум просматривают: Google [Bot] и гости: 17
Была такая же проблема при использовании VSCode в юнити 2019.2.11f, т.е. не отображались контекстные подсказки при вводе для классов, методов и т.д.
Как решил:
1) Делаем все в точности как описано в официальном мануале по интеграции VSCode с Unity
https://code.visualstudio.com/docs/other/unity
2) Если все сделали по мануалу, у вас должен быть установлен VSCode с плагинами C# и Debugger for Unity, при этом в юнити в EditPreferencesExternal tools у вас выставлен VSCode(с установленными параметрами ProjectPath, File, Line, Column) как редактор скриптов и установлен флажок Editor Attaching. Далее, открываем любой скрипт из юнити —
он должен открыться в VSCode и в окне Explorer-а должна отображаться вся структура вашего проекта( а не только файл открытого скрипта).
3)Плагин C# внутри VSCode должен выдать предупреждение в лог (консоль можно открыть в самом нижнем поле редактора VSCode слева внизу два значка — ошибка и предупреждение), что файл проекта подгружен некорректно из-за отсутствия необходимого пакета .Net Framework какой-либо версии (в моем случае это была версия 4.7.1, в вашем случае может быть другая)! Устанавливаем требуемый пакет .NET Framework с оф. сайта майкрософта (https://dotnet.microsoft.com/download/dotnet-framework) или откуда угодно, ДАЖЕ ЕСЛИ УСТАНОВЛЕНА БОЛЕЕ ПОЗДНЯЯ ВЕРСИЯ (это никак не повредит ей).
После установки .Net Framework закройте на всякий случай Unity(если изменяли состояние флажка Editor attaching) и VSCode. Откройте юнити заново и откройте любой скрипт. В этот раз при открытии файла плагин C# в VSCode больше не должен выдавать ошибок загрузки проекта и контекстные подсказки будут работать.
P.S. дополнение VSCode integration для Unity из Asset Store можно не устанавливать, т.к. если все сделано правильно, то все работает и без него.
I’ve been using Visual Studio (2017) for quite a long time now, to program mostly in C#, for Unity games. Recently though, I noticed that it was not displaying any errors in the code anymore, or at least most of them. I initially started making some small tests, for example removing variables that were being used multiple times in the scripts. Visual Studio was not showing any errors, while when going back to Unity, it was showing all the correct errors in the console (as always). Instead, if I tried to remove a parenthese, it was, after a bit, showing errors all over the place. Again, it was really strange.
After one day, I was still testing, and I noticed that if I first opened Visual Studio, and then in «recent» I clicked on the the .sln file, that opened all the scripts for one Unity project, it was immediately showing all the right errors, like it had always done and how (I think) it should always do. I started looking for some differences between what I was seeing there, and what I was seeing when opening the .cs files (in the way that wasn’t working):
- At the top, I wasn’t seeing «Debug» and «Any CPU» how I was when it was working:


-
Another thing was that, between the «Project» and the «Debug» buttons (at the top, that open the drop-down lists), I didn’t have the «Compile» button.
-
Also, under the the «Debug» drop-down many options like «start debug» were not available / disabled.
-
At the top left, under the left-most script name, I have «External files» instead of «Assembly-CSharp»
-
At the right of where there should be «Debug» and «Any CPU», I have «Connect» instead of «Start» (Or something similar, my system’s language is not english, these are translations)
Another (maybe less relevant) thing that has changed from before, when it was working:
- I have installed Visual Studio 2019, and uninstalled after a few minutes (I’ve always preferred Visual Studio 2017!).
Programming without seeing the errors realtime takes much more time, so I’d really like to fix this problem, if it is possible to do so. Is there anything that I have to activate? Did I accidentally press a combination of keys?
Thanks in advance! 🙂
I’ve been using Visual Studio (2017) for quite a long time now, to program mostly in C#, for Unity games. Recently though, I noticed that it was not displaying any errors in the code anymore, or at least most of them. I initially started making some small tests, for example removing variables that were being used multiple times in the scripts. Visual Studio was not showing any errors, while when going back to Unity, it was showing all the correct errors in the console (as always). Instead, if I tried to remove a parenthese, it was, after a bit, showing errors all over the place. Again, it was really strange.
After one day, I was still testing, and I noticed that if I first opened Visual Studio, and then in «recent» I clicked on the the .sln file, that opened all the scripts for one Unity project, it was immediately showing all the right errors, like it had always done and how (I think) it should always do. I started looking for some differences between what I was seeing there, and what I was seeing when opening the .cs files (in the way that wasn’t working):
- At the top, I wasn’t seeing «Debug» and «Any CPU» how I was when it was working:


-
Another thing was that, between the «Project» and the «Debug» buttons (at the top, that open the drop-down lists), I didn’t have the «Compile» button.
-
Also, under the the «Debug» drop-down many options like «start debug» were not available / disabled.
-
At the top left, under the left-most script name, I have «External files» instead of «Assembly-CSharp»
-
At the right of where there should be «Debug» and «Any CPU», I have «Connect» instead of «Start» (Or something similar, my system’s language is not english, these are translations)
Another (maybe less relevant) thing that has changed from before, when it was working:
- I have installed Visual Studio 2019, and uninstalled after a few minutes (I’ve always preferred Visual Studio 2017!).
Programming without seeing the errors realtime takes much more time, so I’d really like to fix this problem, if it is possible to do so. Is there anything that I have to activate? Did I accidentally press a combination of keys?
Thanks in advance! 🙂
Так как в версии 18 года любимую MonoDevelop больше не поддерживают, придется пользоваться VS. Все будет ничего, но подсказок как в моно нет, вернее есть но команд юнити там нет (Time, touch, PlayerPrefs и все остальное), как их включить? В VS code тоже их нет
![]()
Всё до банальности просто, достаточно установить расширения для Visual Studio для этого прожмите:
Средства -> Расширения и обновления. (Tools -> Extentions and Updates..)
В появившемся окне вбить в поисковике Unity.
Установить расширение. (Visual Studio 2017 Tools for Unity)
Но по идее без него должно было всё работать, вроде бы.
![]()
В Unity надо открыть: Edit -> Preferences, вкладка External Tools, в External Script Editor выбирать: Visual Studio 2017 Community.
![]()
Была такая же проблема при использовании VSCode в юнити 2019.2.11f, т.е. не отображались контекстные подсказки при вводе для классов, методов и т.д.
Как решил: 1) Делаем все в точности как описано в официальном мануале по интеграции VSCode с Unity https://code.visualstudio.com/docs/other/unity
2) Если все сделали по мануалу, у вас должен быть установлен VSCode с плагинами C# и Debugger for Unity, при этом в юнити в EditPreferencesExternal tools у вас выставлен VSCode(с установленными параметрами ProjectPath, File, Line, Column) как редактор скриптов и установлен флажок Editor Attaching. Далее, открываем любой скрипт из юнити — он должен открыться в VSCode и в окне Explorer-а должна отображаться вся структура вашего проекта( а не только файл открытого скрипта).
3)Плагин C# внутри VSCode должен выдать предупреждение в лог (консоль можно открыть в самом нижнем поле редактора VSCode слева внизу два значка — ошибка и предупреждение), что файл проекта подгружен некорректно из-за отсутствия необходимого пакета .Net Framework какой-либо версии (в моем случае это была версия 4.7.1, в вашем случае может быть другая)! Устанавливаем требуемый пакет .NET Framework с оф. сайта майкрософта (https://dotnet.microsoft.com/download/dotnet-framework) или откуда угодно, ДАЖЕ ЕСЛИ УСТАНОВЛЕНА БОЛЕЕ ПОЗДНЯЯ ВЕРСИЯ (это никак не повредит ей).
После установки .Net Framework закройте на всякий случай Unity(если изменяли состояние флажка Editor attaching) и VSCode. Откройте юнити заново и откройте любой скрипт. В этот раз при открытии файла плагин C# в VSCode больше не должен выдавать ошибок загрузки проекта и контекстные подсказки будут работать.
Как включить подсказки для кода C# в Visual Studio Code в Unity?
Как подключить Visual Studio Code и Unity? Как включить эти подсказки и автодописание значений в коде? я использую Visual Studio Code, открываю его через Unity, то есть подключение через Unity. Но когда я начинаю писать допустим «Transform» то программа не видит этого значения. Без подсказок писать там просто практически невозможно, а обычный Visual Studio я не хочу использовать потому что VS Code для меня удобнее. Я скачивал .NET Core версии, ставил пути в переменные, смотрел 30+ видео на ютубе, но ничего не работает. Даже VS Code Insider тоже не работает. Никакие установленные расширения тоже не помогают.
Единственно что я получаю: OmniSharp Error: spawn cmd ENOENT
Пишу комментарий со своего второго аккаунта.
Нужно установить .NET Framework (Dev, Targeting Pack, SDK)
В Unity поставить .NET на 4x
В Visual Studio Code установить все нужные расширения, такие как: Unity Tools, C#
Добавить в переменную окружения path путь C:WindowsSystem32 (И в пользовательскую и в системную)
Как вариант ещё можно попробовать установить Packcage (вроде так называется) «Visual Studio Code for Unity» в Unity
И ещё можно попробовать нажать Assets > Open C# Project
После этого всё точно должно заработать. Если нет, то перезагрузите пк, а после входа в Visual Studio Code подождите минут 5 чтобы всё загрузилось. (После перезагрузки пк у меня всё заработало)
Долблюсь с этим интеллисансом каждый раз, после переустановки винды. Каждый раз ошибки разные, но такой ещё не ловил.
Попробуй добавить в пользовательскую переменную окружения path путь C:WindowsSystem32. Гугл говорит что вроде помогает.
Terresquall Blog
If you are our Patreon, log in to enjoy an ad-free reading experience and access Patreon-exclusive articles.
Get in Touch
Recent Posts
- How to fix .gitignore not working on your repository
- Creating a Farming RPG (like Harvest Moon) in Unity — Part 11: Saving Farmland Data
- Bitnami phpMyAdmin: For security reasons, this URL is only accessible using localhost
Find Posts by Category
Terresquall Blog

Soil quality across the world is degrading, and this will result in 40% less food for everyone by 2045. Check out the Save Soil movement, and find out what you can do to contribute to a better world for our children.
Note: This is not an ad. We are not being paid to put up this notice.

Fixing Visual Studio’s IntelliSense (auto-complete) in Unity
If you like our article, do take some time to check out the rest of our site! We have plenty of Unity-related posts, tutorials and even some content on web development!
One of the biggest perks of using Microsoft’s Visual Studio to write your Unity scripts is IntelliSense — a code completion aid in Visual Studio that offers suggestions as you write your code, and contextually presents you with information about classes, properties and methods that you are working with.
Given Unity’s enormous scripting API, IntelliSense is a tremendously helpful feature, especially for coders who are beginning their foray into developing games and software with Unity; and while we’d love to say that IntelliSense is automatically set up and linked to Unity’s API when you install it with the Unity Editor, sometimes that’s just not the case. So, if you’ve got both Unity and Visual Studio set up, but find that IntelliSense is still not offering Unity API suggestions, then this guide is for you.
There can be many reasons why IntelliSense is failing to work properly on your device, and we are assuming that you’ve already scoured the Internet a fair bit before stumbling on our article. Hence, we’ve put together a table of contents of sorts below, so if you’ve already tried some of the solutions we have, you can skip right through them.
If you prefer watching a video instead of reading, do check out our video guide for this post too.
Article continues after the advertisement:
1. Is my IntelliSense not working?
For IntelliSense to detect and work with Unity’s API, Visual Studio needs to:
- Be linked to the Unity Editor, and;
- Have the appropriate extensions installed (read further to find out what they are)
If you’ve installed Visual Studio via Unity Hub, this can have been automatically set up, but not always. Due to the bevy of ways which you can install Unity and Visual Studio, misconfigurations can happen, and you might end up with Visual Studio not integrating itself into Unity, and an IntelliSense feature that is not properly linked to Unity’s API.
We’ve found that, when installing some versions of Unity 2019 and 2020, Visual Studio does not always integrate with Unity’s API by default. So if things are not working properly, it might not be caused by misconfiguration on your end.

If you see these things, then IntelliSense hasn’t been set up on your device.
To check if IntelliSense is properly set up, open any script from the Unity Editor, and look out for 2 things:
- Whether the top-left dropdown says Miscellaneous Files. If it does, then IntelliSense is not set up.
- Try declaring a Unity variable, like a GameObject . If IntelliSense is properly set up, Visual Studio should have an auto-complete suggestion for you before you finish typing.
2. Getting IntelliSense working
So if IntelliSense isn’t working for you, what should you do?
a. Open your scripts from Unity
Before you try anything else from here, first make sure that your scripts are opened from within Unity, i.e. whenever you want to edit your scripts, double-click on them in the Unity Editor so that Visual Studio is opened by Unity.
If IntelliSense still doesn’t work when you do this, then continue onto the steps below:
b. Setting Unity’s External Script Editor
From the Unity Editor, access the Preferences window from Edit > Preferences. Then, click on 1) the External Tools tab.

You’ll need to set the External Script Editor.
Set 2) the External Script Editor to the version of Visual Studio that you installed alongside Unity, then click on 3) the Regenerate project files button (if it’s there).
Once that’s done, restart Visual Studio and see if IntelliSense now works. If it still doesn’t, then you might be missing…
If Visual Studio doesn’t appear on the dropdown, you will have to use the Browse… option (pictured above) to find it. It’s typically under C:Program Files (x86)Microsoft Visual Studio2019CommunityCommon7IDEdevenv.exe for Windows devices.
Article continues after the advertisement:
c. Visual Studio Tools for Unity
To install this, open Visual Studio and go to Tools > Get Tools and Features.

This opens the Visual Studio Installer.
Note: You’ll need administrator permissions to open this window, as it makes changes to the Visual Studio installation on your computer.
Once the installer is open, go to Workloads and find Game development with Unity. Check the box, and then click on the Modify button on the bottom-right corner to begin installation.

Install the Game development with Unity workload.
A popup may ask you to close certain processes before beginning installation. If this happens, close your Visual Studio project and the Unity Editor application.
When installation completes, restart both Unity and Visual Studio, then check to see if IntelliSense now works.
The Games development with Unity workload actually installs 2 additional Visual Studio components — Visual Studio Tools for Unity and C# and Visual Basic. You can install both modules individually by going to the Individual components tab, and checking both components in the list that is shown.

Article continues after the advertisement:
d. Check your .NET API compatibility level
If IntelliSense still refuses to work, you can open the Unity Editor and head to Edit > Project Settings and access the Player (or Player Settings) tab. Scroll down to the Other Settings sub-tab, and find the Api Compatibility Level dropdown under the Configuration heading.
You want to set the Api Compatibility Level to a different option, and see which is the one that works for your device.

The Api Compatibility Level setting is nested quite deep in.
e. Regenerating your Unity project files
If the above solutions we’ve proposed did not work for you, you can also try this solution from one of our comment contributions.
Note: Back up your Unity project before trying this, as we are deleting some essential project files and letting Unity regenerate them.
- Close both Visual Studio and Unity on your device.
- Remove all .sln and .csproj files in your Unity project folder.
- Remove the .vs and Library folders in your Unity project folder.
- Re-open the project in Unity, then go to Assets > Open C# Project to open Visual Studio.
3. Conclusion
As with the other articles on the blog, we’d love if you leave a comment below, especially if you:
- Find any errors in this article, or;
- Find an IntelliSense fix that is not listed in this article
Your comments will add on to the information that is already here, and help other future readers!
4. Video guide
Is this post not visual enough? Perhaps our video guide of this post can help.
Article continues after the advertisement:
There are 15 comments:
This works for me! I had been trying a lot of possible solutions but nothing worked until your post, thanks!
Thank you! Mine has been broken for YEARS!
ps. I found a solution for me, and probably for a lot of Mac users too.
You have to go in VSCode into settings and search for “useGlobalMono” and then change the “Omnisharp: Use Global Mono” setting from “auto” to “always”.
here’s the video I got it from
https://www.youtube.com/watch?v=KJYrRv9cShY
I’ve tried all the proposed solutions, but it still does not work.
I couldn’t try the “Games development with Unity” because on Mac I didn’t find the tab “Get Tools and Features”.
Right click the solution explorer in visual studio, the solution also worked for me
I thought I had selected Visual Stuio as my External Script Editor – but apparently I hadn’t, and when I did it worked 🙂
Thank you very much!
I already has VS2019 16.11.1 installed and working perfectly and also the Unity tools.
I installed Unity from a download link in a tutorial which pointed to 2017.1.0f. Unity changed this to the latest free version 2020.3.16f and I had the problem described.
Even though the Unity objects did not highlight and had no auto-complete, the scripts worked fine?
All I had to do was set the external editor in Unity and then close VS.
The next time, I opened the script from Unity, which opened VS and magically everything now works.
Great tips, thanks
Thanks for the article. Point e (e. Regenerating your Unity project files) was the final step I had to do.
Thank you! Your instructions were concise, easy-to-follow, and in my case completely solved this problem. Much appreciated.
I followed this guide and about 5 others that where exactly the same and nothing worked.
what did work, was right clicking the project and clicking “reload with dependencies”.. This literally fixed it right away.
Might be worth putting this into the guide.. Because I just nearly started eating my keyboard.
Thanks for taking time out to post this. Is the “reload with dependencies” option in Unity, or in Visual Studio? I want to add your tip into the article, but I don’t know where to find this.
I figured this out taking the hint from the original poster. You right click the project in VS, and select “Load Direct Dependencies of Project” and it instantly worked for me too.
VScode plugin для unity это костыль, кривой и устаревший.
Он там не нужен.
Удали C# for Visual Studio Code (powered by OmniSharp).
Удали проекты с этим костылем VSCode (из папки юнити)
Удали все framework 4.7.x которые не для разработчика.
1 — https://dotnet.microsoft.com/d… -installer
2 — https://dotnet.microsoft.com/d… -installer
3 — https://download.visualstudio…. in-x64.exe
Ставишь все это.
Генеририруешь проект в юнити.
Открываешь Visual Code (просто, без юнити).
Ставишь C# for Visual Studio Code (powered by OmniSharp). через расширения hotkey: ctrl + shift + x
ctrl + shift + u
OUTPUT а в фильтре выбираешь OmniSharp Log.
После того, как он найдет в папке файлы .csproj и парсинга их, в output должно появиться что то вроде
[info]: OmniSharp.MSBuild.ProjectManager
Update project: Unity.VSCode.Editor
[info]: OmniSharp.MSBuild.ProjectManager
Update project: Unity.2D.Psdimporter.Editor
[info]: OmniSharp.MSBuild.ProjectManager
Update project: Unity.2D.PixelPerfect.Editor
[info]: OmniSharp.MSBuild.ProjectManager
Update project: Unity.Mathematics.Editor
[info]: OmniSharp.MSBuild.ProjectManager
Update project: Unity.InternalAPIEditorBridge.001
Если будет [fail] значит ты не ребутал машину после переустановки 4.7.x devoloper, ибо надо.