Visual Studio doesn’t support debugging Unity Web content. Use the following tips to get your build information.
The Unity Web platform doesn’t have access to your file system, so it doesn’t write a log file like other platforms. However, it does write all logging information such as Debug.Log, Console.WriteLine or Unity’s internal logging to the browser’s JavaScript console.
JavaScript コンソールを開くには、以下の手順を行います。
For debugging purposes, you might want to make a development build in Unity (open the Build Settings window and enabled the Development Build checkbox). Development builds allow you to connect the profiler, and Unity doesn’t minify them, so the emitted JavaScript code still contains human-readable (though C++-mangled) function names.
The browser uses these to display stack traces if you run into a browser error, when using Debug.LogError, or when an exception occurs and exception support is disabled. Unlike the managed stack traces that occur when you have full exception support, these stack traces have mangled names, and contain managed code and the internal Unity Engine code.
Web has different levels of exception support, but by default, Unity Web only supports explicitly thrown exceptions. For more information, refer to Build your Web application. You can enable Full exception support, which emits additional checks in the IL2CPP-generated code, to catch access to null references and out-of-bounds array elements in your managed code. These additional checks significantly impact performance and increase code size and load times, so you must only use it for debugging.
Full exception support also emits function names to generate stack traces for your managed code. For this reason, stack traces appear in the console for uncaught exceptions and for Debug.Log statements. Use System.Environment.Stacktrace to get a stack trace string.
This is a common problem, especially on 32-bit browsers. For more information on Web memory issues and how to fix them, refer to the documentation on Memory in Unity Web.
The browser console log usually prints this error due to incorrect server configuration. For more information on how to deploy a release build, refer to documentation on Deploying compressed builds.
The browser console log prints this error when the content tries to load an AssetBundle compressed using LZMA, which Unity Web doesn’t support. Re-compress the AssetBundle using LZ4 compression to solve this problem. For more information on compression for Web, refer to documentation on Web building, particularly the AssetBundles section.