![]() Also, textures are stripped out, but some colors come through for example, none of the glass has transparency. The solution is to simply rotate all of the Revit IFC geometry -17deg every time we update the reference. We did a screenshare to check that his model was not rotated, and we couldn't find anywhere this odd rotation was coming from. ![]() However, everything is coming in rotated about the origin by exactly 17degrees. All geometry comes in to VW cleanly, and layers and classes map nicely. There have been some weird things happening, though, and I'm curious if anyone has encountered something similar before.ฤก) we get the building shell from the Architect as IFC. Just read this and thought I would chime in, as I'm modeling a project with an architect in Revit, and we have been able to send the project back-and-forth with some success. This is a lot easier in a program like Lumion but is not a reasonable endeavor in VW. As it is now we can't use either IFC or Revit, without essentially going into every object to assign classes and textures. The architects (EYRC) are using the standard AIA layer/class naming convention in Revit so I doubt there's anything more they can do. If you could point me to a resource that will will explain a better way to do this I would appreciate it. We therefore cannot apply textures to this file in any way to make it a useful tool for visualization as it would take many hours to convert everything to proper classes to assign textures etc. Even after requesting the architect properly calls all object what we get are a bunch of IFC entities with groups and symbols inside all on class '0' or 'none' with no texture applied and attributes not assigned by class. ![]() The problem we have with Revit as well as IFC is the way objects are grouped and classed. You wrote at a great time as we just this morning are trying to import a 550mb Revit file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |