Currently, there is NO publishing process control, going from Revit to DWF to SVG by the HTML publishing process in ARCHIBUS. ARCHIBUS does not allow the user to control the colors or layers of where Revit elements are put, it’s very roughly done based on the default OOTB AIA Standard Template in Revit. As an example, publishing from other tools we can use a DXF template to publish from Revit and have the graphics almost identical to those published from CAD. So what happens with that is colors and or layers can come into ARCHIBUS that are not our client's standard, thus incorrect and confusing. It also causes items to be one color one time when published, and another when published the next time. I even have a project that has the layer a different color for all six floors based on this haphazard process
Allen Angle
shared this idea
·
Currently, there is NO publishing process control, going from Revit to DWF to SVG by the HTML publishing process in ARCHIBUS. ARCHIBUS does not allow the user to control the colors or layers of where Revit elements are put, it’s very roughly done based on the default OOTB AIA Standard Template in Revit. As an example, publishing from other tools we can use a DXF template to publish from Revit and have the graphics almost identical to those published from CAD. So what happens with that is colors and or layers can come into ARCHIBUS that are not our client's standard, thus incorrect and confusing. It also causes items to be one color one time when published, and another when published the next time. I even have a project that has the layer a different color for all six floors based on this haphazard process