Plant 3D™
Troubleshoot native export and bridge setup
Use the loaded connection and request outcome to locate a failure without losing diagnostic evidence or blindly repeating publication.
- Where to find it
- Export component > Advanced > Copy connection details; Check export result; Copy export diagnostics
- When to use it
- Export failure, missing component, wrong appearance or outdated bridge
On this page
Step by step
- Copy connection details and confirm the intended host, project, paths and loaded bridge version.
- If repair failed, retain the newly written last-repair.log from the launcher folder.
- For an export failure, copy its diagnostics and record the request ID and last completed stage.
- If the outcome is unknown or timed out, choose Check export result before retrying.
- When publication succeeds, inspect the target spec and place a new instance rather than expecting an old drawing instance to update automatically.
- For wrong geometry/colours, include the saved JSON, newly generated Python and placed-result evidence.
Catalogue/spec staging
Size-identity, null-reference and NominalDiameter errors identify different native staging failures. Preserve the receipt and diagnostic package. Do not rewrite GUIDs or mark a version file to bypass a native guard.
Loaded old bridge
A running host keeps its loaded DLL. Install the matching package with hosts closed and restart once, then read the loaded version again.
Published versus ready
A late palette/registration failure can differ from a prepublication staging failure. Read actual file/publication status; never assume all failures published nothing.
Missing content
Check the selected spec/family/size, fresh placement, supported inputs and generated geometry. A script file on disk or a successful Live preview alone does not establish native spec readiness.
Keep in mind
- Send the current request diagnostics, not a folder from an earlier failure.
Documentation reviewed