Troubleshooting

Error messages, bottlenecks and how to resolve them.

10 articles
Tools in this category
Articles
The Thundercad tab does not appear in Inventor
  1. Open Inventor and go to Extra β†’ Add-Ins.
  2. Find Thundercad Toolkit and enable both Loaded and Load Behavior β†’ Load on Startup.
  3. Close Inventor and reopen it.
  4. Still no tab? Reinstall Thundercad using the most recent installer.
My license key is not accepted

Check that the key was copied exactly (without spaces), that your subscription is active, and that the license is not linked to another PC. If it still does not work, contact Cadkunde with your account details.

Batch Publish skips documents

Possible causes:

  • The document is in an excluded folder (see Publish settings β†’ Exclude folders).
  • No drawing exists for the part.
  • The file is read-only or locked by someone else.
Export PDF / DWG ends up in the wrong place

The output folder for PDF/DWG/DXF/STEP is set on the Publish tab in the settings. A different path can be set for each format. Export Folder always opens the folder that belongs to the format you last used.

Model Cleaner leaves work features in place

Open the Model Cleaner tab and enable the appropriate checkboxes for work planes, axes, points, surfaces, 2D and 3D sketches. By default only some of them are enabled.

Get Drawings cannot find my drawing

Get Drawings searches for .dwg, .idw and the variants -SW.dwg, -EV.dwg and -EV.idw. If your drawing is named differently, it will not be recognized. In that case, open Vault directly or adjust the naming rule.

The settings screen closes immediately

This can happen after an upgrade when old settings are no longer compatible. Delete the Thundercad settings folder in %APPDATA%\Thundercad (or Cadkunde) and restart. The settings are then recreated with defaults.

Where do I find the error logs?

As of this version the add-in writes errors to a log file again. For years this did not happen, which left problems invisible. The logger is now active again and records everything that goes wrong, so you (or we) can trace a fault.

You will find the log file at this location on your own computer:

  • Folder: %LocalAppData%\{brand}\Logs (where {brand} is the product name of the add-in)
  • File: AddinLog.txt

Paste %LocalAppData% into the File Explorer address bar to jump straight there. The folder is created automatically as soon as there is something to log. Each entry contains the time, the date and the error message, neatly separated by dashes.

If the file grows beyond 5 MB, the add-in automatically moves the old content to AddinLog.old.txt and starts a fresh AddinLog.txt. This keeps the file manageable and stops it growing without limit. The logging itself is fully shielded: if writing fails for any reason, it does so silently in the background and never disrupts Inventor. Running into a problem? Include the contents of AddinLog.txt with your report so we can help much faster.

Fixed problems in this version

This version focuses on stability. The biggest gain is under the hood: the SettingManager that manages all settings is now thread-safe. The settings cache had come to be read from background tasks as well, and an ordinary list can become corrupted in that case. All access now runs through a lock, so reading and writing at the same time is safe.

There is also a new GetBool helper. In 167 places an on/off setting was previously read with an unchecked bool.Parse. If such a value was empty, corrupted, or held "1" or "0" instead of true/false, it would break. Now the add-in falls back neatly to a default value, so a corrupt setting can never again block a Save or a document switch.

Also fixed in this version:

  • Entering a licence mid-session: duplicate events are gone, one click now performs exactly one action.
  • SupportForm: no longer crashes Inventor when there are network problems.
  • Find Item: works as intended again.
  • Place Article: when overwriting you now get a clear Yes/No prompt.
  • Article Manager: now saves atomically; a corrupt file is kept as .corrupt.bak instead of losing your data.
  • XML storage: is written atomically and read read-only, so it also works safely on network drives.

Didn't find what you were looking for?

Our team is happy to help.

Contact us