Docs / Reference
Troubleshooting
Resolve common launch, graphics, modeling, sign-in, and copilot problems.
The desktop app does not start
All native builds are 64-bit and need a graphics driver capable of a modern hardware-accelerated 3D context; update the GPU driver first if the app exits at launch. Reinstalling from the download page replaces a corrupted install. The browser workspace requires no download and is the quickest cross-check.
The viewport is blank or slow
Update the GPU driver, then restart Chudware. Avoid remote-desktop sessions that do not pass through hardware-accelerated 3D graphics. If the interface appears but geometry does not, switch display style and fit the view before assuming the model is empty.
A feature fails
Return to the first failed feature in the tree. Check its sketch state and references before editing later features. Fillets commonly fail when the radius is larger than a neighboring face; cuts fail when they no longer intersect a body.
Sign-in or license check fails
Check system time, internet access, and whether app.chudware.com is reachable. A paid desktop license has an offline grace period, but initial activation requires sign-in.
The copilot cannot run
Open Settings → Providers and confirm that a supported provider account is connected or that your API key passes its connection test. Check the selected provider’s plan, API billing, and usage limits. Read the concrete error in the copilot feed before retrying, and inspect the feature tree for any tool actions that completed earlier in the turn. Enter provider credentials only in Provider settings, never in chat or project notes.
Using Chudware from macOS
The macOS build is downloaded from your account like the others; on Apple silicon the Intel build runs through Rosetta 2. If you prefer not to install anything, use the browser workspace from your Mac. Do not download an unofficial installer.
For account help, email support@chudware.com without including passwords, provider keys, or private project files.