Installation
Choose the desktop installer or a checked PowerShell setup. Both install the same versioned ArcGIS Pro add-in.
Check your environment.
- Windows 11 x64 (build 22621 or later, as targeted by this add-in).
- ArcGIS Pro 3.7, installed and licensed.
- Rhino 8, installed and licensed. Historical host tests used Rhino 8.34.26223.11001 with ArcGIS Pro 3.7.1.1904; compile-time Rhino references remain pinned to 8.23.
Run each application once to complete its initial setup and sign-in. ArcGIS Pro 3.6 or earlier is outside this release's supported scope.
Installing a packaged add-in does not require the .NET SDK or Visual Studio. Building from source requires the .NET 10 SDK and the ArcGIS Pro SDK build targets.
Version 1.3.0 — candidate
This is a release candidate. Runtime validation is pending; this page does not certify ArcGIS Pro and embedded Rhino compatibility.
No stable installer or gateway download is available. See Releases for the experimental preview. Requires ArcGIS Pro 3.7, Rhino 8 and Windows 11 x64.
Experimental download: v2.0.0-alpha.1
Known issue: saving pending Rhino work during Pro shutdown can stall. Full lifecycle and interactive acceptance are incomplete. Use disposable project copies.
Download preview ZIP for Windows
Includes the bundled Grasshopper library, runnable MapDesign.ghx example, optional MCP gateway, checked PowerShell installer, checksums and instructions. No separate GHA installer or Yak package is needed. Requires Rhino 8.36.26282.15001 or newer. Individual downloads and release notes · User and agent setup · Preview metadata for agents
Each installer is pinned to a named GitHub release, with its own checksum and release notes. Do not use the GitHub “Source code” ZIP as an installer.
Install the add-in.
- Save your work and close ArcGIS Pro.
- Download the
.esriAddinXasset andSHA256SUMS.txtfrom the same release. - Optionally check the download in PowerShell:
Compare the result with the checksum supplied for that release.Get-FileHash .\RhinoInside.ArcGISPro-v1.3.0.esriAddinX -Algorithm SHA256 - Double-click the
.esriAddinXfile. Review the name and version in the Esri ArcGIS Add-In Installation Utility, then select Install Add-In. - Start ArcGIS Pro. In Settings → Add-In Manager, confirm that Rhino.Inside for ArcGIS Pro is listed.
The add-in is unsigned. If your organization permits only signed add-ins, use your normal administrator approval process.
See Esri's official add-in installation guide for installation locations and managed deployments.
Launch Rhino inside your project.
- Open an ArcGIS Pro project with an active map.
- Open the Rhino.Inside ribbon tab and its dockpane.
- Select Launch Rhino. Rhino opens in the ArcGIS Pro process.
- Confirm the earth anchor before exchanging any geometry.
- Follow the GIS-first or Rhino-first guide.
Begin with a copy of a project. Apply writes to the linked GIS data and Rhino document under your selected rules.
Update or remove.
Save the ArcGIS project and the Rhino .3dm, then close ArcGIS Pro before installing a newer version. Download the replacement from its named release, check the notes, and run the same installation steps.
To remove a locally installed copy, open Settings → Add-In Manager, select the add-in and use Delete this Add-In. Restart ArcGIS Pro. Shared folder installations should be managed by the folder's administrator.
If something does not load.
The Rhino.Inside tab is missing
Confirm ArcGIS Pro 3.7 and the add-in version in Add-In Manager, then restart Pro. Check whether your organization's add-in restrictions prevent it from loading.
Rhino cannot start
Open standalone Rhino 8 once to confirm installation and licensing. Restart Pro and try Launch Rhino again. A successful standalone launch checks licensing; the embedded launch still needs to succeed separately.
Pro crashes after Save or when closing
Stable installer publication is blocked while a native shutdown crash is investigated. Windows events on the tested system named V-Ray 6.10.0.0. The new save path is under validation; diagnostic safe mode is not a release certification. Read the current findings and reporting steps ↗.
Geometry arrives in the wrong place
Stop before Apply. Check the source coordinate reference system, Rhino units and the earth anchor. See georeferencing.
I need to report a problem
Include the add-in version, ArcGIS Pro build, Rhino version, geometry type and the exact message. Describe the smallest repeatable workflow and whether Preview or Apply failed. Remove confidential project data before sharing an example.
Install with an agent or PowerShell.
Agents can begin with machine-readable installation metadata or the agent entry point. Stable metadata reports that no stable installer is available; its experimentalPreview field links to the separate preview download and known issues.
Once the stable release is available above, download its pinned setup script, inspect it, then run it. It checks prerequisites, verifies the package identity and SHA-256, refuses installation while Pro is open, and prints a JSON result. No administrator account, GitHub sign-in or developer tools are needed.
Invoke-WebRequest 'https://raw.githubusercontent.com/nicoazel/Rhino.Inside-ArcGIS-Pro/v1.3.0/tools/Install-RhinoInsideArcGIS.ps1' -OutFile .\Install-RhinoInsideArcGIS.ps1
Get-Content .\Install-RhinoInsideArcGIS.ps1
.\Install-RhinoInsideArcGIS.ps1 -WithMcpOmit -WithMcp for the add-in alone. Use -WhatIf to preview or -DownloadOnly to fetch and verify without installing. Follow your organization's script policy. Full agent installation guide ↗
Connect your agent.
The optional MCP gateway requires Node.js 22 or later. After setup with -WithMcp, launch your project with:
& "$env:LOCALAPPDATA\RhinoInsideArcGIS\1.3.0\mcp\Start-RhinoInsideArcGIS.ps1" -Project 'C:\Projects\Design.aprx'The launcher enables the endpoint for that Pro process and prints a client configuration with its exact process ID. Copy the mcpServers object into your MCP client. Refresh the PID after restarting Pro. Open Rhino.Inside in Pro, launch Rhino, and configure your layer links.
Agents can inspect links and preview changes. Pull, Apply and Save require local review in Pro. For general ArcGIS tools, install the separate ArcGISPro.MCP companion and select the same PID.