In some cases, CUBE may fail to launch or may close unexpectedly on startup. Running CUBE in debug mode allows you to capture additional diagnostic information that can help identify the source of the issue. This is especially useful for troubleshooting installation problems, missing dependencies, licensing issues, or errors that occur before the graphical interface loads.

When should you run CUBE in debug mode?

Run CUBE in debug mode when:

• CUBE crashes immediately on launch
• The application opens partially and then closes
• You see unexpected error messages when starting CUBE

Debug mode forces CUBE to display additional dialogs and output messages, which often reveal what is preventing the software from starting normally.

How to run CUBE in debug mode

1. Open Command Prompt

You can do this by typing cmd in the Windows Start Menu and selecting Command Prompt.

2. Navigate to the CUBE installation directory

By default, CUBE installs to:

C:\Program Files (x86)\Citilabs\Cube

3. Launch CUBE with the debug flag

Run the following command:

cube.exe /debug

The screenshot below shows what this looks like in Command Prompt:

4. Click through any dialogs

Debug mode may display multiple popup dialogs.
Click OK on each dialog and carefully note any error messages that appear.

These messages often reveal:

• Missing DLLs
• Licensing failures
• Path or environment issues
• Corrupt configuration files

5. Review any error messages

If you are collecting information for Technical Support, include:

• The full error text from any dialogs
• A screenshot of the Command Prompt window
• A description of what happens before/after running in debug mode

This helps isolate the cause of startup issues quickly.