Help...
I am hoping to draw together a number of fragmented contributors from previous threads regarding the inter-operability of Revit and Viz, in order to clarify a system by which one may introduce a Revit model to a viz scene, and thereafter efficiently update that scene from the contiunously evolving Revit base model.
i.e. The architect is designing away, adding and removing things, and every second day wants a fancy viz render of their wildly altered revit model. How do I do this most efficiently?
THE BIG, TIME-HUNGRY PROBLEM (for us) IS EFFICIENTLY GETTING THE APPROPRIATE VIZ MATERIALS ONTO ANY NEW OBJECTS WHENEVER THE REVIT MODEL IS CHANGED AND RELINKED INTO THE SCENE.
There appears to be a couple of manual solutions to this problem, the most promising of which is based on the 'select by material' function of the Material Editor in Viz. This allows one to - upon each relink - select all instances of a particular (revit/accurender) material with a click of a button, and apply the appropriate viz material to these instead.
So the process becomes:
1. Export as polymesh to AutoCAD .dwg from a 3D view in Revit
2. Link said .dwg into the Viz scene via the file link manager, using a revit preset
3. Import all the (now retarded, non-bitmapped) accurender materials from the scene into the material editor (one by one, what a pain)
4. Create the Viz materials one plans to use
5. Using the 'select by material' button in the material editor, select all instances of a particular material and apply the new Viz material to them
Every time the Revit file is updated (say another window has been added to a house):
6. Re-export the model from Revit, over-writing the same .dwg as previously used
7. Re-link the file into Viz via the file link manager, checking the 'Use scene materials on reload' option
8. Go through step 5 all over again
This is retarded. Does anyone have a more efficient process than this? Or even a slight tweak to add? I would l o v e to hear a faster/simpler alternative...
My apologies for the long winded post, but this is driving us nuts and eating soooo much time.
Many thanks in advance,
Nathaniel Cheshire