My googling has returned little useful information on cross product workflows.Īnyone in the Arch world face this dilemma? We want to be respectful of our consultants workflows, but this is shift in platform we're seeing has become a time suck for our teams.
I'm not certain about this Enscape based workflow, but my suspicion is that the teams are not comfortable in Lumion as they are Enscape. According to my team member this wasn't as big an issue when LA teams were working in Enscape as we could leverage the Enscape data in a different manner. Often, our teams are tasked with taking the shared Lumion data from the LA team and manually coordinating it our models so that hardscapes, entourage placement, plannings, etc look consistent across documents. I am unaware of a means of taking authored data in Lumion and bringing into Revit (or if I would want to do that). The LA teams love this as it creates rapid high quality renderings, but there's a disconnect between the authored data in Lumion and what Revit can "see".
The Landscape architects they work with are increasingly working in Lumion to produce renderings. I had a project manager approach me with a unique challenge.
0 kommentar(er)
