New Release: pyRevit 4.8.12

Tools
1

Downloads

:small_blue_diamond: See Assets section below for all download options

pyRevit

pyRevit CLI (Command line utility)

Highlights

  • Revit 2023 Compatibility
  • Added “Wipe Selected Families”
  • Resolved #1480: Exporting with the Make Pattern tool will work with some patterns but not others

Changes

Python API

  • Resolved #1481: pyRevit double-digit patch version does not show up correctly in UI

:yellow_heart: Thank you to all the contributors for this release!
@ejs-ejs @perrylackowski @onomou @dvdgnz @Jean-Marc @sanzoghenzo @alexdaversa @dagz214 @dosymep @MatthewBoynton

12 Likes
3

thank you!
and is it going to support using pyrevit.forms in cpython in the future?

4

Most probably not since doing that means supporting WPF in cpython. I haven’t seen any libraries for that. I’m hoping IronPython 3 would show up before that

5

Thanks for the release! Installing it straight away

6

Is anyone having an issue whereas pyRevit is not working for 2020/2021 with this new version but installed for 2022/2023?

7

Not that I know of. Are you having issues?

8

Ehsan, yes, I am having issues with pyRevit not working in 2020/2021 which is why i asked if it others are having that issue. I did have 4.8.11 installed prior to the availability of 4.8.12 and both were installed after installing 4.8.12.

9

What’s the problem? Any errors? Would you mind sending *.log files inside %APPDATA%/pyRevit/20XX folders?

10

Sent what I found via email.

11

I haven’t had any issues nor have seen any on my colleagues computers (25+)

12

You could check what revit plugins are installed for 2020/2021 and not installed for other versions.
It may be a dll conflict or the loading sequence of revit bypassing the pyRevit loader @SH-MEP_BM

A clean uninstall/ pyrevit doctor command /install might fix it.

13

I can’t wait for the 2024 compatible release. It’s painful using Revit now without the PyRevit extension. Any idea when we’ll see the 2024 release?

14

Hi @brenTRON
You can get the latest wip installers
See how here Notion – The all-in-one workspace for your notes, tasks, wikis, and databases.

Most of the tools i have used so far work fine.

15

Hi Jean-Marc

Thank you for your link to the WIP. I have followed the instructions to the Summary section and the pyrevit-installers at the bottom, but I cannot seem to download a ZIP file you mention for the latest build to install to work with Revit 2024 - am I missing something?

Thank you so much!
Tim

16

Hi, I have downloaded the latest WIP installer, but before i go a head and install it.

Will this overwrite the version of pyrevit im using in 2023? Im assuming it will. Will it break anything?

As i will still mostly be using 2023 until we upgrade later in the year when some of the other addins we use have been updated to 2024.

Thanks :slight_smile:

17

@shane_au
It will replace it.
But to be thorough, what needs to be done to install a new version is the following:

  1. Uninstall the previous version
  2. Install the new one
18

i uninstalled pyrevit and installed the WIP version. Revit 2024 would crash during loading.

Revit 2023 would still opened fine.

Journal file has a bunch of API errors in it.

' 0:< API_ERROR { : Assembly version conflict in some references in pyRevitLoader.dll assembly
'Addin's module RevitAPI of version 22.0.0.0 conflicts with same preloaded module of version 24.0.0.0
'Addin's module RevitAPIUI of version 22.0.0.0 conflicts with same preloaded module of version 24.0.0.0 } 
' 0:< ::50:: Delta VM: Avail -14 -> 134178663 MB, Used +9 -> 371 MB; RAM: Avail -2 -> 3224 MB, Used +12 -> 623 MB, Peak +1 -> 624 MB 
' 0:< GUI Resource Usage GDI: Avail 9712, Used 288, User: Used 197 
' 0:< API_ERROR { : Assembly version conflict in some references in pyRevitRunner assembly
'Addin's module RevitAPIUI of version 22.0.0.0 conflicts with same preloaded module of version 24.0.0.0
'Addin's module RevitAPI of version 22.0.0.0 conflicts with same preloaded module of version 24.0.0.0 } 
' 0:< ::50:: Delta VM: Avail -24 -> 134178639 MB, Used +12 -> 384 MB, Peak +13 -> 387 MB; RAM: Avail -28 -> 3196 MB, Used +22 -> 645 MB, Peak +24 -> 649 MB 
' 0:< GUI Resource Usage GDI: Avail 9711, Used 289, User: Used 197 
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.WindowsAPICodePack assembly
'Addin's module mscorlib of version 2.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module System of version 2.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module System.Windows.Forms of version 2.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module System.Core of version 3.5.0.0 conflicts with same preloaded module of version 4.0.0.0 } 
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.WindowsAPICodePack.Shell assembly
'Addin's module mscorlib of version 2.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module System.Windows.Forms of version 2.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module PresentationFramework of version 3.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module System of version 2.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module WindowsBase of version 3.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module PresentationCore of version 3.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module System.Drawing of version 2.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module System.Core of version 3.5.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module WindowsFormsIntegration of version 3.0.0.0 conflicts with same preloaded module of version 4.0.0.0 } 
' 0:< API_ERROR { : Assembly version conflict in some references in MadMilkman.Ini assembly
'Addin's module mscorlib of version 2.0.0.0 conflicts with same preloaded module of version 4.0.0.0
'Addin's module System of version 2.0.0.0 conflicts with same preloaded module of version 4.0.0.0 } 
' 0:< ::50:: Delta VM: Avail -12 -> 134178628 MB, Used +4 -> 388 MB, Peak +1 -> 389 MB; RAM: Avail +0 -> 3197 MB, Used +7 -> 653 MB, Peak +4 -> 653 MB 
' 0:< GUI Resource Usage GDI: Avail 9711, Used 289, User: Used 197 
' 0:< API_ERROR { : Assembly version conflict in some references in System.Memory assembly
'Addin's module System.Numerics.Vectors of version 4.1.3.0 conflicts with same preloaded module of version 4.1.4.0 } 
' 0:< API_ERROR { : Assembly version conflict in some references in System.Reflection.Metadata assembly
'Addin's module System.Collections.Immutable of version 1.2.3.0 conflicts with same preloaded module of version 1.2.5.0 } 
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.CodeAnalysis assembly
'Addin's module System.Collections.Immutable of version 1.2.3.0 conflicts with same preloaded module of version 1.2.5.0 } 
' 0:< ::50:: Delta VM: Avail -11 -> 134178617 MB, Used +2 -> 390 MB, Peak +1 -> 390 MB; RAM: Avail +0 -> 3198 MB, Used +3 -> 656 MB, Peak +3 -> 656 MB 
' 0:< GUI Resource Usage GDI: Avail 9711, Used 289, User: Used 197 
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.CodeAnalysis.CSharp assembly
'Addin's module System.Collections.Immutable of version 1.2.3.0 conflicts with same preloaded module of version 1.2.5.0 } 
' 0:< API_ERROR { : Assembly version conflict in some references in pyRevitLabs.Common assembly
'Addin's module System.Collections.Immutable of version 1.2.3.0 conflicts with same preloaded module of version 1.2.5.0 } 
' 0:< ::50:: Delta VM: Avail -22 -> 134178596 MB, Used +1 -> 391 MB, Peak +1 -> 391 MB; RAM: Avail 3198 MB, Used +1 -> 658 MB, Peak +1 -> 658 MB 
' 0:< GUI Resource Usage GDI: Avail 9711, Used 289, User: Used 197 
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.CodeAnalysis.VisualBasic assembly
'Addin's module System.Collections.Immutable of version 1.2.3.0 conflicts with same preloaded module of version 1.2.5.0 }
19

@shane_au please create. Anew topic and go through issues in the repo on GitHub (solved ones and unsolved) to see if one fits your problem. Or gives you the solution.
If not: New Issue and follow the process for new issues