RevitBatchProcessor Versions Save

Fully automated batch processing of Revit files with your own Python or Dynamo task scripts!

v1.9.0-beta

1 year ago

Updates:

  • Adds support for Revit 2023
  • Adds support for non-standard Revit installs. Thanks to @maciejwypych for the code for this

Notes:

  • This release has undergone testing at BVN side but due to the multitude of functions that Revit Batch Processor can perform we can't test for everything. We also don't have access to Revit versions 2015 - 2017 so cannot test these. Please log any bugs that you find in issues

v1.8.0-beta

1 year ago

Updates:

  • Adds support for Revit dialogs that are displayed in Spanish. Thanks to @jsrubianoj for adding this functionality.
  • Target .NET Framework version to 4.8 across all projects. See this link for .NET APIs effected by migration to this version. Thanks to @kraftwerk15 for adding this functionality
  • Modifies the default Revit failure handling to try to detach or skip before deleting elements. Thanks for @jchristel for adding this functionality

Fixes:

  • The processing of cloud models in Revit 2022 where there is an additional parameter for region of the hub. Thanks to @dimven for this bug fix

Notes:

  • This release has undergone testing at BVN side but due to the multitude of functions that Revit Batch Processor can perform we can't test for everything. We also don't have access to Revit versions 2015 - 2017 so cannot test these. Please log any bugs that you find in issues
  • Update to accommodate Revit 2023 should be in the coming months

v1.7.0-beta

2 years ago
  • Adds preliminary support for Revit 2022
    • Thanks to Nicklas Oestergaard (@NicklasOestergaard) for upgrading RBP to support Revit 2022!

Please note this version (and any future versions) are provided as is (I have not and cannot test RBP these days). Please reach out to the Dynamo / Revit community for any support and / or fixes.

v1.6.0-beta

4 years ago

Updates:

  • Adds support for Revit 2021
  • Adds basic support for processing BIM360 cloud models.
    • Requires Forge Project and Model IDs (Guids) to be specified in the Revit file list. These IDs can only be obtained via Forge API which is beyond the scope of RBP. So it is left to the user to obtain these IDs for their BIM360 project models.
    • The format for specifying a cloud model in the Revit file list is:
      • <Revit version> <Project Guid> <Model Guid>
      • Note: these three components must be separated by space(s) (not tabs!).
      • e.g. 2020 75b6464c-ba0f-4529-b049-0de9e473c2d6 0d54b8cc-3837-4df2-8c8e-0a94f4828868
      • RBP is not able to detect the Revit version of cloud models hence why the Revit version is specified explicitly.
    • Special thanks to Dimitar Venkov (@dimven) for investigating ways of processing BIM360 cloud models for RBP!
  • Internal Revit process error messages (ones that appear as [ REVIT ERROR MESSAGE ]) are now hidden by default. This is because they're mostly useful for advanced troubleshooting. To re-enable these types of errors logged to the console, look in the settings file for the setting showRevitProcessErrorMessages. Set this to true.

Fixes:

  • Disables the Revit session option in the UI when using a Dynamo task script. This is because Dynamo scripts always use a separate Revit session per file due to a technical Revit API limitation (see Issue #38)

v1.5.3

4 years ago

Updates:

  • Adds CSV support (thanks to @RyanSchw)
  • Data from any additional columns in the Revit file list can now be accessed from the python task script using revit_script_util.GetAssociatedData(). This function returns a list of strings representing the cell values that were adjacent to the Revit file path currently being processed.
  • The Revit file scan now has the option to ignore Revit backup files (thanks to @vinnividivicci)
  • Support for Revit installations on D: drive (thanks to @vinnividivicci)

Fixes:

  • Improved UI layout algorithm (thanks to @RyanSchw)

v1.5.2

4 years ago

Updates:

  • Changed the (internal) Revit session initialization time-out to 5 minutes (it was previously 10 minutes; an upper bound of 10 minutes waiting for the Revit session to initialize was a bit excessive!)

Fixes:

  • If the Revit session terminates before ANY file processing has begun (e.g. if the initialization time-out kicks in, or if Revit crashes on startup), then DO NOT skip processing of files that would have been processed in that session. Process the files in a new Revit session. (Previously the files that would have been processed in a Revit session that terminated before initialization was completed would be skipped under this scenario.)

v1.5.1

5 years ago

Updates:

  • Add support for newer JSON Dynamo workspace file format (Dynamo 2+ scripts) (Issue #34)
  • Add --per_file_timeout command-line option for setting the per-file processing time-out from the command-line. (Issue #33)

Fixes:

  • Dynamo 2+ workspace files in JSON format no longer fail to execute. (Issue #32)

v1.5

5 years ago

Updates:

  • Support for Revit 2020 (Issue #31)

v1.4.7

5 years ago

Updates:

  • Ignores (does not log output) 'Load Link' dialog box (as this dialog box goes away on its own after a link is temporarily upgraded)

Fixes:

  • Fixes command-line --audit option not working (Issue #29)

v1.4.6

5 years ago

Updates:

  • New Workset Configuration option for Central file processing (Issue #27):
    • Close All Worksets
    • Open All Worksets
    • Open Last Viewed
  • Audit option (Issue #28)
  • Improved command-line --help (includes command-line examples for the above options)