-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Truong Giang Vu edited this page May 31, 2026
·
1 revision
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.
Check:
- Pixi can run on the machine
-
%APPDATA%\RevitDevTool\pixi-envis writable - Package indexes are reachable (conda-forge + PyPI)
- Enterprise security policy is not blocking downloads
Check:
- VSCode is listening on the configured port
- The RevitDevTool debugger port matches VSCode
-
debugpyis installed in the active Python environment - Firewall/security policy allows local attach
Check:
- The host (Revit, AutoCAD, or Civil 3D) is running with RevitDevTool loaded
- Named Pipe exists:
ls //./pipe/ | findstr Revit(orAutoCad,Civil3D) -
host_nameandhost_versioninpyproject.tomlmatch the running instance - Try explicit pipe:
pytest --host-pipe=Revit_2025_<pid> -v
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
Check:
- At least one host instance is running with RevitDevTool loaded
-
MCPServer.exeis at%APPDATA%\Autodesk\ApplicationPlugins\RevitDevTool.bundle\Contents\MCPServer\ - Named Pipes matching
{Host}_{Version}_{PID}exist
- Run Code Overview
- Modern Python Scripting
- Python Debugging
- Python Ecosystems
- RevitDevTool And pyRevit
- Python Stub Generation
- Run .NET Add-ins
- Scripting Runtimes