Skip to content

Troubleshooting

Truong Giang Vu edited this page May 31, 2026 · 1 revision

Troubleshooting

Build Configuration Not Found

Use .slnx and Autodesk configuration names:

dotnet build RevitDevTool.slnx -c "Debug.Autodesk.2025"

Do not use old names like Release R25. Available configurations: Debug.Autodesk.2022 through Debug.Autodesk.2027 and Release.Autodesk.2022 through Release.Autodesk.2027.

Python Dependencies Do Not Install

Check:

  • Pixi can run on the machine
  • %APPDATA%\RevitDevTool\pixi-env is writable
  • Package indexes are reachable (conda-forge + PyPI)
  • Enterprise security policy is not blocking downloads

Python Debugger Does Not Attach

Check:

  • VSCode is listening on the configured port
  • The RevitDevTool debugger port matches VSCode
  • debugpy is installed in the active Python environment
  • Firewall/security policy allows local attach

PyTest Bridge Cannot Connect

Check:

  1. The host (Revit, AutoCAD, or Civil 3D) is running with RevitDevTool loaded
  2. Named Pipe exists: ls //./pipe/ | findstr Revit (or AutoCad, Civil3D)
  3. host_name and host_version in pyproject.toml match the running instance
  4. Try explicit pipe: pytest --host-pipe=Revit_2025_<pid> -v

Geometry Does Not Display (Revit)

Check:

  • The active view supports DirectContext3D rendering
  • Visualization is enabled in settings
  • The traced object is a supported Revit geometry type
  • The geometry is within visible view range
  • The script printed the actual geometry object, not just a string representation

MCP Server Cannot Find Hosts

Check:

  • At least one host instance is running with RevitDevTool loaded
  • MCPServer.exe is at %APPDATA%\Autodesk\ApplicationPlugins\RevitDevTool.bundle\Contents\MCPServer\
  • Named Pipes matching {Host}_{Version}_{PID} exist

Clone this wiki locally