Make sure you installed the Game/Unity workload in Visual Studio.Try recreating projects/solution using Open C# Project or Edit / Preferences / External tools / Regenerate Project files.Try deleting all projects/solution files and the.Unity 2020.x+: Check that you are using the latest Visual Studio Editor package in Window / Package Manager.Help / About should display a message like Microsoft Visual Studio Tools for Unity is enabled at the bottom. Check that the Visual Studio plugin is installed in Unity.Check that Visual Studio is set as your external script editor in Unity using Edit / Preferences / External Tools.So, after each troubleshooting step, make sure you try to re-open the solution and try to right-click on all incompatible projects and choose Reload Project. The very important thing to know is that Visual Studio is saving the “Incompatible” state in project settings and will not try to reload a project until you explicitly use Reload Project. If you are developing your own native plugin, We recommend using asynchronous procedure calls ( APC) and especially SleepEx, SignalObjectAndWait, MsgWaitForMultipleObjectsEx, WaitForMultipleObjectsEx, or WaitForSingleObjectEx functions to properly cooperate with Unity and Mono when the debugger needs to suspend threads. This means Unity can't interrupt that thread for the debugger (or domain reload) and stop responding.įor FMOD, there is a workaround, you can pass FMOD_STUDIO_INIT_SYNCHRONOUS_UPDATE initialization flag to disable asynchronous processing and perform all processing on the main thread. It’s an issue when a plugin ends up attaching a native thread to the runtime, which then does blocking calls to the OS. Several Unity plugins like Parse, FMOD, UMP (Universal Media Player), ZFBrowser, or Embedded Browser are using native threads. In case you are still experiencing the problem, run a Developer Command Prompt for Visual Studio as Administrator and use the following command: devenv /setup Try removing the following folder to reset the MEF cache (close Visual Studio before doing this): %localappdata%\Microsoft\VisualStudio\\ComponentModelCache This issue can be due to the Visual Studio MEF cache being corrupted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |