Running Your Game Directly From the PC

Running Your Game Directly From the PC

This only works with the CAT-DEV. There are two ways to do this. Using Build and Run is more convenient, but if your game crashes while you are testing it, the output log window will close, and your output will be lost. If you want to save your output, follow the steps in Using run.cmd instead.

Using Build and Run

  1. Turn on your CAT-DEV (using the switch on the side of the devkit). You don't need to start it up with the "cafex on" command since Build and Run will start up the devkit automatically.
  2. Open your project in Unity. If this is your first time building on this PC, we recommend first testing with a new project (see Verifying Your Environment is Setup Right).

  3. From the menu bar, select File > Build Settings.

  4. Under Platform, if Wii U is not already selected, select Wii U and then click Switch Platform.

  5. Set the Build Debug Level to Development. If you are using networking features in your game, or if you are using the Unity profiler and/or script debugging, set the Build Debug Level to Development[With Network]. If not, use Development[No Network].

  6. Set the Build Output to Unpackaged.

  7. Set the Boot Mode to PCFS.

  8. Click Build and Run.

  9. You will be prompted to select a build directory if you haven't selected one already. We recommend you choose a location outside of the project folder. Specify the location and click Select Folder.

  10. If your environment is set up correctly, the project should start building. Once finished, it will automatically load on your CAT-DEV, and a command prompt window will open up and display the output log. If it didn't load, or your build failed with other errors, please see the section on common Unity Editor errors and solutions for additional troubleshooting.

Note

If any application (other than System Config Tool) is running on your devkit, your game will fail to load. To cancel a running application, open cafex_env.bat and enter the command "cafex stop" (with no quotes).

Using run.cmd

First you must build your game. If you have already done this (for example, when using Build and Run previously), you can skip the steps to build your game.

Build your game

  1. Open your project in Unity. If this is your first time building on this PC, we recommend first testing with a new project (see Verifying Your Environment is Setup Right).

  2. From the menu bar, select File > Build Settings.

  3. Under Platform, if Wii U is not already selected, select Wii U and then click Switch Platform.

  4. Set the Build Debug Level to Development. If you are using networking features in your game, or if you are using the Unity profiler and/or script debugging, set the Build Debug Level to Development[With Network]. If not, use Development[No Network].

  5. Set the Build Output to Unpackaged.

  6. Set the Boot Mode to PCFS.

  7.  Click Build.

  8. You will be prompted to select a build directory if you haven't selected one already. We recommend you choose a location outside of the project folder. Specify the location and click Select Folder.

  9. If your environment is set up correctly, the project should start building. Once finished, it will open a file manager window for your build folder. If your build failed, please see the section on common Unity Editor errors and solutions for additional troubleshooting.

Running your game

Once your game is built, go into your build folder. There will be a file called run.cmd. If you double-click this file, it will run on your devkit, but the output log information will be lost if your game crashes. Instead, we recommend the following steps.

  1. Turn on your CAT-DEV (using the switch on the side of the devkit). You don't need to start it up with the "cafex on" command since it will start up automatically when run.cmd executes.
  2. Open an MS-DOS terminal window.
  3. Drag and drop run.cmd on the terminal window.
  4. Press enter.

Only the most recent lines from the output log will be displayed in the terminal. If you want to save the entire log file, you must export it to a text file. You can do so by typing ' > ' after run.cmd followed by the name and location of the text log you'd like to create. For example, the full command on step 3 above would look like this:

D:\unity_build_folder\run.cmd > c:\outputLog0001.txt

 

Note

If any application (other than System Config Tool) is running on your devkit, your game will fail to load. To cancel a running application, open cafex_env.bat and enter the command "cafex stop" (with no quotes).

 


CONFIDENTIAL