Howver, my real complaint is that why did any of this happen in the first place - why have a Revit 2019 installer that doesn’t warn you it is about to screw up your 2016 Dynamo install, and that you’ll have to manually fix it all some way? 1.3.2 and 1.3.3 are almost the same so you’d probably be able to share all your graphs etc between the two however, I’ve heard some people say that it doesn’t work if you try to install both those (unlike 1.3.2 and 2.0, which it lets you install in parallel as you describe). The thing is that Dynamo 2.0 is not backward compatible, and is very much different under the hood to 1.3 - I am not sure exactly what the implications are, but I’d say it would mean you’d have to maintain two entirely different sets of everything (your graphs, custom nodes, packages etc). That is what the developers recommend over of GitHub. I can’t promise it will work for you and please be very careful messing around in the program Files folder (I wouldn’t normally recommend it). The folders are:Ĭ:Program Files\Dynamo\Dynamo Revit\1.2\Revit_2016Ĭ:\ProgramData\Autodesk\Revit\Addins\2016Ĭopy those folders and files back to the equivalent place after the Revit 2019 installer has done its stuff. Much to my surprise it worked, and I now have Dynamo 1.2 on Revit 2016 and Dynamo 1.3.3 on Revit 2019. In my case it was too late, so I found the installed dynamo files on another computer and copied them to the computer where they’d been blitzed. I found a post on GitHub where some service pack for Revit 2017 did the same thing - someone suggested copying the Dynamo install files for 2016 to a safe place before installing the new version of Revit/Dynamo - then copying them back afterwards. While Autodesk decide whether to do anything about this issue, I have found my own dodgy workaround.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |