Compatibility
Compatibility and feature limits
Use the release-specific support matrix and the limitations below when choosing a modelling or export workflow.
- Where to find it
- Documentation reference
- When to use it
- Understanding the boundary between an editor feature and a validated host result
On this page
Step by step
- Check the supported desktop/host versions for the actual released build.
- Distinguish a Designer feature from native Python export or Live Link support.
- Validate the source parameter combinations and dimensions used by your component.
- Run a fresh placement and connection check before sharing a new family.
Known boundaries
Native Python Intersect export is not supported. Arbitrary non-mm imported-source conversion is not established. Imported table discovery covers recognised patterns, not arbitrary runtime data.
Publishing and updates
Family export does not automatically regenerate existing drawing instances. Global Library is documented as simulated/preview. Host-specific deployment, connected fitting behaviour and parameter effects need their own verified scope.
Recent repairs
Verify colour-region export and first-use graph Focus in your installed release and Plant host. Report differences between Designer and Plant with diagnostics.
Do not infer
Use the compatibility matrix and release notes supplied with your installed version. Do not assume that another host or script variant behaves identically.
Keep in mind
- Use release notes for changes and status; keep the main tutorials focused on the approved workflow.
Documentation reviewed