For those of you who are successfully using Rhino.Inside Revit in an office setting, I’m wondering, how much of a project should be driven from the Rhino side vs the Revit side? This inevitably will be an “it depends” type answer, but I’m wondering what’s working for you? And what challenges are you facing?
I’m a longtime Rhino and Revit user, but not together. I’m working on trying to lead an office in getting a RiR strategy and workflow implemented. For now, we’re mainly combining DirectShapes from Rhino with the main bulk of the modeling being done in Revit. I know we’re severely underutilizing RiR capabilities. But also most of our staff aren’t close to fluent in Rhino.
If you have successful workflows, especially in an office with a mixed bag of staff skill sets, can you please describe what you’re doing from the Rhino side vs the Revit side and how you’re piecing things together? In your mind, what are the next couple steps we should take after implementing the most basic (DirectShapes)?
I think what I see happening is that there is one person who is a good jack of all trades computational designer, and the team is heavily dependent on that one person doing everything, driving everything, and figuring things out. This doesn’t seem like the ideal scenario but maybe hard to avoid. Is this the case for a lot of you?
Like you mention, it is very dependent on workflow and culture; often users aren’t encouraged to go down paths less traveled, regardless of the potential.
Ideally they will give you enough leeway to get the job done, but this typically puts the onus on the computational designer who then has ends up working far too many hrs. This is justifiable if what they are learning and the mistakes and successes can be applied to the next project, as well as the obvious increased skillset.
Rhino.Inside.Revit seems to be most applicable to specific workflows that would otherwise be mundane and lengthy for the user to do through the Revit UI.
The smaller and more generalized the workflow the easier it is to get others involved. That said, most scripts require some knowledge of parameters, types, categories and filtering, which the average user might not be aware of and can easily cause havoc in a project.
Yup, it really does depend on the culture and the people involved.