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. Do not rename the main Unity executable, as VSTU is only monitoring "Unity.exe" processes.
Unity visual studio debug not working software#
You can try to temporarily stop any extra software to see if it changes something.
In this section, you'll find solutions to common issues with Visual Studio Tools for Unity, descriptions of known issues, and learn how you can help improve Visual Studio Tools for Unity by reporting errors.
0 kommentar(er)
