@scott.tomlinson are you able to provide me with the family to check ? Feel free to upload here if you are comfortable, or direct message me.
Just by way of an update, I’ve tested further, and the problem appears to be setting a family parameter which requires an Integer value. I created a simple Generic Annotation family with an integer based instance parameter, and the same error is returned. No error is returned on number, yes/no (etc…) parameters only those requiring an integer.
Would you know the cause / solution to this. If it is a Dynamo v2.13 (+?) will this be resolved in future releases?
Hello @scott.tomlinson - This has now been resolved for
Revit 2023.1 and
Dynamo 2.15, and will also be hot-fixed back to
Revit 2023.0.1 along with a bunch of other bug fixes in Revit.
Unfortunately I cannot gives dates on this, but the hotfix should be coming out relatively soon So sorry for the frustration on this one.
As rightly noted, it’s a generic problem that had to be remedied inside the Unit Converter class: fix the issue revit-191624 (#2826) by wangyangshi · Pull Request #2846 · DynamoDS/DynamoRevit · GitHub
Ah… good to know that it wasn’t user-error on my behalf
Thanks again for the prompt feedback - much appreciated.
Hello @scott.tomlinson - as per 📢 Dynamo 2.13 - Revit 2023 Set Parameter Issue(s) - Hotfix Out Now you should now be able to download the hotfix and have this resolved
Hello @solamour … unfortunately even with the Hotfix installed, the problem persists (unless I’m doing something wrong).
Oof, ditto. Assume this works in the developer’s tests for Dynamo build, so maybe something got missed in the hotfix deployment?
Have a look at the solutions above.
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?