Getting started
Connect your software
Move from a detected installation to a fresh connection with the exact host and document you chose.
Before you begin
- An eligible Vector OS build and a separately licensed, exactly supported Rhino or Revit installation.
- An eligible connector package for that exact app/host/runtime lane.
- Save important work and be ready to close affected host instances when configuration requires it.
Follow the steps
Choose how to find the host
Open bundled Connect. Use its disclosed local detection, choose Manual locate for an executable you installed, or defer setup. Detection does not scan your projects or start the host.
Checkpoint: You see no host, an unsupported candidate, or uniquely labelled version/path choices.
Select one eligible installation
Choose the intended host/version explicitly. Read Requirements for an unsupported candidate; selecting a file path alone is not compatibility proof.
Checkpoint: Connect identifies the exact eligible installation rather than guessing between versions.
Review and install the connector
Read the package publisher, version, size, permissions and compatibility. Use the built-in verified installation flow.
Checkpoint: The package receipt confirms installation. If the host is absent, the state remains installed/configure later, not Connected.
Configure and restart normally
Follow the host-specific configuration plan. Save and close all affected host instances when requested, then perform the normal restart. Do not change unrelated plugins or add-in files yourself.
Checkpoint: Configuration is read back and any restart requirement is satisfied.
Open the intended document
Use the explicitly offered host launch action or open your host normally, then open your document in the host. Choose the exact live process and document in Connect.
Checkpoint: The selected document label, units and current host identity match your intended work.
Test the fresh connection
Use Connect/test and wait for an authenticated handshake and current capability result.
Checkpoint: Connected is tied to that live process and document. A running process, installed package or successful restart alone is insufficient.
Check the result
- Connect reports a fresh authenticated connection for the selected host/document with the capabilities it actually exposes.
- No native model change is needed to establish the connection.
If something goes wrong
No host is detected or more than one version appears.
Refresh after installation or manually locate the intended executable. Select a unique eligible candidate; do not use an unsupported Configure workaround.
Resume from: Exact host installation selection.
The package is tampered, its metadata expired or installation response is lost.
Stop. Keep the package identity and original lifecycle reference. Inspect the installation journal/inventory before another attempt.
Resume from: Known package/registration state.
The host starts but the plugin is missing or trust is blocked.
Inspect the stated runtime/trust/configuration problem. Keep host protections enabled and use repair guidance for that build.
Resume from: Verified registration followed by a fresh handshake.
Connection drops during a write.
Pause affected document writes and reconcile the original operation. Reconnect refreshes identity; it must not replay the edit.
Resume from: Original outcome, then fresh document binding.
Need help?
Include your step and this reference.
Vector OS guide: /tutorials/connect-software
Guide updates
Connect your software
Revision 357cf1b1e18ce460d8a25aa04682b5c10cc51fe522bb6376161eb18c5114d742 ·