(System.String importedAssets, System.String addedAssets, System.String deletedAssets, System.String movedAssets, System.String movedFromAssetPaths) (at C:/buildslave/unity/build/Editor/Mono/SyncProject.cs:165)
(`1 affectedFiles, `1 reimportedFiles) (at C:/buildslave/unity/build/Editor/Mono/VisualStudioIntegration/SolutionSynchronizer.cs:213) (`1 source, System.Func`2 predicate) (at :0) (System.String asset) (at C:/buildslave/unity/build/Editor/Mono/VisualStudioIntegration/SolutionSynchronizer.cs:224) (wrapper remoting-invoke-with-check) System.IO.FileInfo.ctor(string) System.IO.FileInfo.ctor (System.String fileName) (at :0) System.IO.FileInfo.Init (System.String fileName, System.Boolean checkHost) (at :0) System.IO.Path.GetFullPathInternal (System.String path) (at :0) System.IO.Path.InsecureGetFullPath (System.String path) (at :0)
ArgumentException: The specified path is not of a legal form (empty). A cursory glance at the diffs showed it’s something related to the way assets are copied over? Not an issue for me going forward, but I’ll paste the stack trace for reference. Editor playmode started spewing out an error every few seconds. Both release and debug (using L version of the plugin) builds seem to work fine.ĭowngrading FMOD but sticking with Unity 2019.2.18f1 brought its own issues. I downgraded FMOD to 2.00.06 and upgraded Unity to 2019.3.1f1.
Release build browser console output: ' successfully downloaded and stored in the indexedDB cache ( ' successfully downloaded and stored in the indexedDB cache ( ' successfully downloaded and stored in the indexedDB cache ( failed to asynchronously prepare wasm: LinkError: import object field '_ZN4FMODU7gGlobalE' is not a Number ( printErr instantiateArrayBuffer blob: LinkError: "import object field '_ZN4FMODU7gGlobalE' is not a Number" ( LinkError: "import object field '_ZN4FMODU7gGlobalE' is not a Number" ( printErr onAbort abort blob: instantiateArrayBuffer blob: uncaught exception: abort() at build Unity editor console output:įailed running “C:/Program Files/Unity/Hub/Editor/2019.2.18f1/Editor/Data/PlaybackEngines/WebGLSupport\BuildTools\Emscripten_Win\python\2.7.5.3_64bit\python.exe” -E “C:/Program Files/Unity/Hub/Editor/2019.2.18f1/Editor/Data/PlaybackEngines/WebGLSupport\BuildTools\Emscripten\emcc” unexpected number of arguments 1 in call to ‘_cxa_pure_virtual’, should be 0warning: unexpected number of arguments 2 in call to ‘_ZN6il2cpp6icalls8mscorlib6System6String22RedirectToCreateStringEv’, should be 0warning: unexpected number of arguments 4 in call to ‘_ZN6il2cpp6icalls8mscorlib6System6String22RedirectToCreateStringEv’, should be 0warning: unexpected number of arguments 5 in call to ‘_ZN6il2cpp6icalls8mscorlib6System6String22RedirectToCreateStringEv’, should be 0warning: unexpected number of arguments 4 in call to ‘_ZN6il2cpp6icalls8mscorlib6System6String22RedirectToCreateStringEv’, should be 0warning: unexpected number of arguments 2 in call to ‘_ZN6il2cpp6icalls8mscorlib6System6String22RedirectToCreateStringEv’, should be 0warning: unexpected number of arguments 3 in call to ‘_ZN6il2cpp6icalls8mscorlib6System6String22RedirectToCreateStringEv’, should be 0error: unresolved symbol: FMOD5_ChannelGroup_AddDSPerror: unresolved symbol: FMOD5_ChannelGroup_AddFadePointerror: unresolved symbol: FMOD5_ChannelGroup_AddGrouperror: unresolved symbol: FMOD5_ChannelGroup_Get3DAttributes A release build compiles and runs, but gets stuck 90% of the way into the loading screen, and a development build doesn’t compile at all. Hey, ever since integrating FMOD I’m unable to build for WebGL.
0 kommentar(er)
