Exporting — Comparison Across Connectors
Every Resolver connector ships with an Export action that packages your study (CAD, kinematics, operations, targets) into a .zip that Resolver's planning engine can read. The steps are similar across tools, but the UI surfaces, prep requirements, and file layout differ in ways that matter in practice.
This page is a side-by-side overview. For step-by-step instructions, follow the connector-specific page linked in each column.
At a glance
| Visual Components | Process Simulate | MELSOFT Gemini | |
|---|---|---|---|
| Export output | .zip uploaded to Resolver | .zip uploaded to Resolver | .zip uploaded to Resolver |
| Key contents | project.yaml, queries.json, metadata.json, objects/, robot_models/ | project.yaml, queries.json, metadata.json, objects/, robot_models/ | project.yaml, queries.json, metadata.json, objects/, robot_models/ |
| Visibility matters? | Yes — only visible objects/robots are exported | Yes — only visible objects/robots are exported | Yes — only visible objects/robots are exported |
| Collision rules exported? | Via the Collision Detector Editor | Via PS collision sets → collision_rules | Via Gemini collision sets → collision_rules |
| Where to configure | VC Add-On panel → Export tab | PS ribbon → Resolver Connector → Export | Gemini toolbar → Resolver Connector → Export |
| Dummy op for idle robots? | Auto-generated | Auto-generated | Auto-generated |
| Offline / cloud export | Both supported | Both supported | Both supported |
| Detailed guide | VC Exporting | PS Exporting | Gemini Exporting |
Shared preparation steps
Regardless of which simulator you're in, you'll want to:
- Hide anything you don't need planned. Unhidden geometry is exported — hide fixtures, tooling, and scene props that aren't relevant to the motion problem. This speeds export, shrinks the
.zip, and avoids unsupported-object errors. - Give every visible robot an operation. A visible robot with no operation gets a dummy op at its current pose. That works, but explicit operations produce better plans.
- Configure collision rules. The connector converts your simulator's collision configuration into
collision_rulesinsideproject.yaml. Get this right before exporting — retrofitting rules server-side is painful. - Sign in to Resolver from the connector. Cloud upload requires credentials. The connector caches these after the first login.
When to choose which workflow
- Visual Components — Best when your team already authors layouts in VC and you want the shortest round-trip to optimized paths.
- Process Simulate — Best when the study lives in the Tecnomatix ecosystem, especially for large brownfield cells with rich kinematics.
- MELSOFT Gemini — Best when the target cell uses Mitsubishi robots and you want tight integration with the MELSOFT toolchain.
If you're evaluating connectors for a new project, the export output format is identical across all three — the decision should be driven by which simulator your team already uses, not by Resolver compatibility.
Troubleshooting exports
If your export fails or produces unexpected results, the connector-specific troubleshooting pages are the right starting point. Common issues across all three:
PROJECT_PARSE_FAILEDafter upload → usually a collision-rule or kinematics configuration issue in the source study.UPLOAD_FAILED→ check network, credentials, and that the.zipsize is under the per-project limit.- Missing objects in Resolver → they were hidden at export time. Unhide, re-export.
For full error-code coverage, see the Troubleshooting section in the sidebar.