Yes the problem is now that the fix was meant to have been patched. Doesn’t seem to have been unfortunately, or we’ve both installed incorrectly. Autodesk app was my method, so figure it was correct.
I also installed via the AD Desktop app.
Hello all - I just installed the update myself and am seeing the same issues you guys are seeing I’ll reach out to the team in question and investigate. The PR was merged (code fix) and the case I just tested that failed, was working at that point in time.
hi Scott, which Revit 2023 hotfix version are you using? Is it Revit 2023.0.2 (build 20220726_1500), released on Aug. 3rd?
Hi @gina.liu, I believe so…
We’re looking into a proper fix now - it appears, as Gavin mentioned above, to be an installer build issue. We’re working on properly identifying how to resolve this issue
WARNING: Dangerous approach to use at your own risk below...
If you want to be adventurous and live on the edge, you can replace the DynamoNodes.dll attached here inside your DynamoRevit installer.
This comes with a few caveats:
- We take no responsibility for any problems that occur should you choose to take this action.
- If something goes wrong and breaks, it may cause you to have to reinstall Revit. Theoretically it shouldn’t.
- This didn’t blow up my install and worked perfectly fine, but there have been issues in the past.
- Take a copy of your existing RevitNodes.dll just in case and place it somewhere safe, so that you can put it back if needed.
- To attach to the Dynamo Forum the .dll file been renamed into a .txt file, so you’ll need to rename it back to simply RevitNodes.dll for Dynamo to recognize it.
- The attached RevitNodes.dll contains the fix, and will unblock the problems in this thread.
- After downloading the RevitNodes.dll make sure to right-click on the file, go to Properties and unblock it so that Windows will trust the file and allow it to be read.
- Your RevitNodes.dll will live under
C:\Program Files\Autodesk\Revit 2023\AddIns\DynamoForRevit\Revit
RevitNodes.dll.txt (386.5 KB)
Thanks @solamour …Works great, the only thing i just will mention is
8. remember unblock the file
Good shout! I’ll add that to the steps
Thank you Mr. Wizard. I followed your instructions and it works perfectly! My best wishes to you.
Thanks for this
Any idea if this is going to make it into the 2023.1 release?
I’ve installed the update… I’ll let you know. Fingers crossed
There is an update?
Revit 2023.1 which includes Dynamo 2.16 was released late yesturday.
Therefore it should be on your Autodesk management portal to download and install. Or speak to who ever looks after this within your company to get them to sort it.
Didn’t show up in the desktop app. I guess I’ll just have to log in to the site and…oh right all of autodesk is broken. lol. Maybe tomorrow.
It looks like it’s been fixed. All working well for me
For everyone watching this thread, this has now been resolved in the following builds:
- Revit 2023.1
- Revit 2023.0.2
- Revit 2024 (Upcoming release)
Good day, I am wondering in the Revit 2022 that bug will not be fixed? Cause I have the same issue when trying to set a certain workset to the elements
Hi @viktornrozalite - we would need the Revit team to issue a hotfix for DynamoRevit to be able to resolve this, and in older versions these are slower and typically based around a push sequence of Security/Trust.
Have you tried this? Error - specTypeId is not a measurable spec identifier? as the second post in this thread shows a workaround today.