Phasing out Ladybug Tools Dynamo Packages in favor of using RhinoInside Revit

Hello everyone,

Some of you might have seen my post on Twitter, LinkedIn or Facebook for the same topic. I’m also sharing it here to get your feedback if you don’t use any of the other platforms.

We have been thinking to stop the development of our packages for DynamoBIM in favor of using RhinoInside in Revit. We would like to know how this change will affect your work before making the final decision.

I should add that we are experimenting with providing a Ladybug Tools Plugin for Revit. That will make it possible to use the plugins directly from Revit or import the mode generated by the Revit plugin in Dynamo using Ladybug Tools Python libraries but you will be responsible for developing the code in Dynamo.

Let us know your thoughts.

8 Likes

For me it makes sense to focus on Rhino/Grasshopper and RhinoInside Revit.

3 Likes

I prefer the development for RhinoInside Revit.

2 Likes

Does this mean the organization would pause to look for solutions to current basic issues occurring in the nodes running on current version of Revit and Dynamo? If yes, I understand and will look elsewhere for solutions. Being a fairly new Dynamo user I don’t have much understanding in coding but do see the advantages in the possibility of using Refinery together with current Ladybug, Honeybee and other nodes to help inform the design process. I do wish that I had come across these nodes in working order two years ago instead of now though. Thanks for your community efforts in trying to bring these package accessible.

Will be unfortunate to see Ladybug tools go from Dynamo. Haven’t tried RhinoInside, does it require Rhino license on the machine? If so, that will be huge roadblock, implementing new software into an office is not easy. Aside the license, interoperability between Dynamo and Revit should work the best.
Please release final update for the tools before discontinuing support, if you decide to do so