Follow the instructions below to collect the debug logs from your pyRevit installation and submit to the developers to help identifying the problem.

Activating File Logging in pyRevit Settings

If pyRevit runs normally, and you can access the pyRevit settings, open the Settings → Reporting Levels and activate the File Debug Logging option

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/4f498f0a-4b1d-4f38-9acf-5f21d6b3b0a5/Screen_Shot_2020-05-08_at_07.55.31.png

But if pyRevit fails to run and crashes Revit for some reason, go to %APPDATA%/pyRevit directory and open the pyRevit configuration file pyRevit_config.ini. Make sure the file logging is activated (filelogging = true) under the [core] section.

If the file does not exist, create an empty text file matching the name and extension (pyRevit_config.ini) and place the content below inside the file

[core]
filelogging = false

Clearing Cache

Before collecting the debug log, we would want to clear all existing ones first. Open a command prompt window and run the command below:

pyrevit caches clear --all

Collecting the Debug Log

Now start Revit. pyRevit will take a bit longer this time to load since it is recording all the actions in a file on the disc. Once Revit is crashed or other pyRevit errors happen, go to the %APPDATA%/pyRevit/<revit version> directory that matches the Revit version you used and collect the debug log file. The debug log file name ends in _runtime.log as shown below

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/b77583e0-8f44-4e58-9cb8-8bc90c555490/Screen_Shot_2020-05-08_at_08.05.37.png