The same issue applies to the Helix mesh. The issue is with the discernment on what geometry was modeled that should not have been modeled. These large families can be composed of strictly native geometry. This is an existing problem with bad families that can be found online from random sources. We could add a feature that automatically places these models in a linked Revit model instead of the main model! This way designers don’t need to switch models for sending the mesh objects over. With the current Helix offering, it’s easiest for designer to just load these models in the main Revit project. If users would want to load high poly contextual models in Revit, they should be in a linked file to keep the project file nimble. …and don’t get me started on the family name that was auto-generated…Īs a former BIM manager I have the same concerns! As a developer on Helix, I see opportunities to address these issues: Revit ArcViz Model Link If you wanted 100 cars for reference, you are potentially looking at a 500MB Revit file (you know those designers want every car to be unique). Now imagine a parking lot full of these cars. This particular Porsche model results in a 5MB revit family. I would be ok if these types of render assets were loaded into an ArcViz model that links in the main model, but when will designers take the time to do this right when a manager is standing over their shoulder waiting for a render? This sort of workflow has me equal parts terrified and curious at the same time. Steve Bennett from Taylor-Design had some great criticisms for this workflow posted on LinkedIn, copied below:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |