Unity Editor Error Troubleshooting

Common Unity Editor Error Messages and Troubleshooting

If you get a build error with your regular game project, we recommend troubleshooting using a new, empty project since it is easier to identify the cause. If you can get the empty project to build without problems, it means your development environment is set up correctly.

One problem in your development environment can produce different errors depending on the PC and the project you are working on. The errors given below are sample errors. The actual output on your system might be slightly different.

Type of Error Sample Error Message Possible Cause
Namespace error error CS0234: The type or namespace name `WiiU' does not exist in the namespace `UnityEngine'. Are you missing an assembly reference? Your platform is not set to Wii U. See here for how to set this.
Never progresses beyond "Attempting to launch"

You get the following message, but even after waiting a few minutes, your build is never launched on your devkit:

Attempting to launch in C:/<BUILD_DIRECTORY>

Your CAT-DEV is off or not connected, or you are using Build And Run, but only have a CAT-R. CAT-R cannot use Build And Run. Just use Build, and install your game to your devkit via SD card.

If you are using a CAT-DEV, try using cafex_env.bat to see if you can find your devkit with that. If you cannot, try setting up your CAT-DEV network settings again. You may first want to reinitialize the network settings.

GHS_ROOT not found Exception: Environment variable GHS_ROOT not found. Add it to the program environment or assign it in Editor preferences. You must set the GHS_ROOT environment variable. See the first section in Troubleshooting GHS MULTI for how to do this.
Compilation error

Exception: Failed to compile C into .o (C:/<BUILD_DIRECTORY>\_Intermediate\WiiUMain.cpp) UnityEditor.WiiU.PostProcessCafePlayer+CafeUtils.CompileCC...

Your CAFE_ROOT system variable is not set to point to your Cafe SDK installation. If you used the NDI client to set up your environment, it installed a script called SetupEnvironment.wsf to automatically set up the system environment variables. Run that if you have not already, then restart your machine.

It also could be due to your variables not being set in the Unity Editor. See here for more details.

If that does not work, try troubleshooting GHS MULTI.

Also, be sure there are no spaces in your Cafe SDK or GHS MULTI install path, and no spaces in your build directory.

Any error with "ghs" in the text. Win32Exception: ApplicationName='c:\ghs\multi5326\cxppc.exe', CommandLine='-G -Ogeneral -cpu=espresso -c99 -kanji=shiftjis -sda=none -X332 --no_implicit_include -dbg_source_root ".

 There is a problem involving GHS MULTI. See here for troubleshooting GHS MULTI.

Also, be sure there are no spaces in your Cafe SDK or GHS MULTI install path, and no spaces in your build directory.

Cross compilation errors

UnityException: Cross compilation failed.

at UnityEditor.WiiU.PostProcessCafePlayer.CompileAOT (BuildTarget target, BuildOptions options, WiiUBuildDebugLevel variant, System.String codeDir, Boolean allowDebugging, System.String stagingAreaDataManaged, System.String targetDir)

There is most likely a problem involving GHS MULTI. See here for troubleshooting GHS MULTI.

It also could be due to your variables not being set in the Unity Editor. See here for more details.

Be sure there are no spaces in your Cafe SDK or GHS MULTI install path, and no spaces in your build directory.

Assembly conversion error

UnityException: Assembly conversion failed.

at UnityEditor.WiiU.PostProcessCafePlayer.CompileAOT (BuildTarget target, BuildOptions options, WiiUBuildDebugLevel variant, System.String codeDir, Boolean

There is most likely a problem involving GHS MULTI. See here for troubleshooting GHS MULTI.

It also could be due to your variables not being set in the Unity Editor. See here for more details.

Be sure there are no spaces in your Cafe SDK or GHS MULTI install path, and no spaces in your build directory.

"Failed to Move" errors

IOException: Failed to Move File / Directory from 'Temp/StagingArea/Data' to C:/<BUILD_DIRECTORY>/content/Data'.

Error building Player: IOException: Failed to Move File / Directory from 'Temp/StagingArea/Data' to 'C:/<BUILD_DIRECTORY>/content/Data'.

 

 

 

 The build directory is either in use, or is not accessible.

  • If you are still running a program on your devkit, close it by opening cafex_env.bat and typing "cafex stop". 
  • Your computer might have an active lock on one of the files. Restart your computer, or just make a new build directory.
  • If you are using a network or shared drive, try locating the build directory on another local drive.
There is no Wii U build option  

This could be one of two things:

Any other error  

Verify you are using the correct SDK version for your Unity for Wii U version. See the Middleware Version Table to find what SDKs correspond to your version of Unity.

After doing that, try the above methods (especially restarting your PC), as they most likely will resolve the error.

If none of the above methods have resolved your issue, something may have gone wrong when setting up your environment. Uninstalling the development environment (including Unity) and reinstalling it (with all virus/malware protection software removed or disabled) might fix the problem. Also try looking for a solution on the forums.

Topics in This Section

 

 


CONFIDENTIAL