Nexus
Runtime download or installation failed
Distinguish network, package matching, installation locks, and post-installation status problems.
Distinguish add-on packages from runtime packages
Runtime components run web pages locally and ship separately from add-ons. An add-on ZIP cannot install the runtime; Mac and Windows packages are not interchangeable. Showing the card does not start networking or installation.
Choose the correct recovery path
- With network access permitted in Blender, use Download & Install.
- Offline, choose Local Package… and select the provider's matching runtime ZIP. Local installation still validates structure and compatibility.
- For an incompatible package, choose Choose Another Package…. Do not rename, splice, or edit identities to bypass checks.
- After download reaches 100%, wait for validation and installation. Runtime components ready is different from download complete.
For detailed steps, see Install and check runtime components. Use a compatible package confirmed by the project provider.
Follow the actual message
| Observation | Diagnosis and response |
|---|---|
| Network failure or online access disabled | Check connectivity and Blender's online access setting. Retry after fixing them or use a matching offline package. |
| Insufficient disk space | Allow space for download, extraction, and installation, not just compressed size. |
| Components in use or another installation active | Save work and close Blender instances using the runtime, or wait for the active job. Do not force-overwrite programs or start concurrent installations. |
| Damaged or incompatible package | Obtain matching materials again from the provider. Repeated clicks cannot fix package identity or platform mismatches. |
| Installed but failed to start | Preserve the exact message to distinguish system blocking, native bridge, and program failures. Existing files do not prove availability. |
Closing the card and managing cache
Closing the card neither resolves the issue nor uninstalls anything. Confirm successful add-on enablement and binding; a new missing-package event can show the card again. If needed, save and restart normally, then reproduce from the add-on entry point. Do not repeatedly toggle all add-ons.
Clear Cache affects download data and is not a general repair button. Do not manually delete the shared directory during installation. The installer manages the active runtime; do not substitute arbitrary executables from source caches.
Return to the real add-on after installation
- The card no longer reports installation or startup errors.
- Open the real web window from the add-on entry point.
- Perform an existing operation, verify its result, then close normally.
If it still fails, report installation method, platform, exact message, and package source. Do not publish unrelated personal paths or credentials from logs.
If unresolved, follow Provide useful diagnostic information to prepare a minimal reproduction and original messages for the add-on author.