Nexus
Local preview and Blender verification
A browser can check the page itself. Real windows, host integration, and input feel must be checked in Blender.
Use both preview modes for their own purposes
| Method | Can establish | Cannot establish |
|---|---|---|
| Browser preview | Layout, content, URLs, and frontend interactions | Real host hit testing, input, or Blender changes. |
| Local Blender window | Real opening, input, and host integration | Success on every other platform/version. |
| Package inspection | Manifest and packaged resource consistency | Problem-free real user interaction. |
Fix page-local issues first
- View static pages directly; build existing projects through their normal flow.
- Check main pages, expanded content, and missing resources.
- Missing acquireNexusWebUI in a browser is an environment boundary, not proof the add-on is broken.
- Label demo data as simulated. Do not silently replace failed production connections with fake results.
Reload affects only actually loaded output
web.local_app("web/index.html", auto_reload=True)Stable page changes trigger full reload. With separate source/install copies, build and synchronize to Blender's loaded location first. Editing another copy does not update the page. Disable auto_reload for release.
Save and restart Blender as needed after Python/framework changes. Repeated add-on toggling does not prove service replacement.
Follow a clear verification workflow
- Open from the real user entry and check size/content.
- Read the actual scene and verify one predetermined operation.
- Check cancellation, no-data cases, errors, and repeated clicks.
- Check transparent edges, header dragging, inputs, and dropdowns.
- Close from the page and reopen from the original entry; check toggle sequences separately.
Describe verification accurately
State platform, Blender environment, entry, steps, and actual results. Screenshots show static appearance; input methods, drag feel, repeated interactions, and animation require hands-on testing. Identify unchecked platforms/steps rather than calling everything passed.
Website Blender simulations do not connect to real scenes. Reading the site does not execute these checks for you. For further diagnosis, see Continue development and diagnose problems.