I’d like to bump this topic.
We have encountered similar problem with Rhino inside Tekla.
With current solution as is.
Currently we are developing solutions where Rhino/GH is launched independently, we have scripts, that automatize workflow for the whole model. 15 licenses are enough to cover ~20-30 engineers, that need to use these scripts once a month for 10minutes.
Rhino inside Tekla opens large possibilities to develop things in a new way.
Instead of 15-30 “once a month” users, we could develop things for all detailers - possibly 100-150 users.
But still, most use cases for these users possibly will be ~10minutes a day for specific things.
Restarting Tekla is not an option. (For very large detailed models, it can take 30-40minutes to open).
With current approach, we would have to evaluate before developing a new workflow tool - how many users will use it per project. If it’s single user. It could possibly be developed for the project’s “dedicated” Rhino inside Tekla user.
If it’s more than 1 person, it would most likely be better then to develop the workflow with more time consuming C# api plugin/application approach.
The technical capabilities of Grasshopper for engineers are amazing. However current approach makes it hard to switch to even better abilities with Rhino inside Tekla.
I understand business reasons. We have steadily acquired additional licenses basically only for Grasshopper functionality - to develop automated workflows, occasionally use them once/few times per project.
But with current approach, developing and using a little 10-20mins rhino inside Tekla each day for each user would require too steep mountain in license increases.
I hope, there will be some changes in future.
P.S. Would like to mention again, that Grasshopper is such an amazing tool, I’m not saying it enough. Good job guys!