New Revit User Question: Revit to InfraWorks Workflow

New Revit User Question: Revit to InfraWorks Workflow

Anonymous
Not applicable
1,030 Views
8 Replies
Message 1 of 9

New Revit User Question: Revit to InfraWorks Workflow

Anonymous
Not applicable

New Revit user question: This might seem trivial, but I noticed that when I open my revit my model does not appear by default, only when I turn on "Show Massing & Floors". My question is if I have this preliminary model and want to place it in InfraWorks to contextualize the design, will it even show up, since by default the model does not show up unless I specify to "Show Massing & Floors"? Is there something that I need to do to the model before I can put it into InfraWorks?

0 Likes
Accepted solutions (1)
1,031 Views
8 Replies
Replies (8)
Message 2 of 9

barthbradley
Consultant
Consultant

Your Model -- or your Masses and Mass Floors -- does not appear by default?  Sounds like your Project is just Masses.  

0 Likes
Message 3 of 9

Anonymous
Not applicable

I drew everything in the Mass In-Place. I'm not to familiar with the workflow of Revit in general. Am I supposed to not draw everything with Mass In-Place?

0 Likes
Message 4 of 9

barthbradley
Consultant
Consultant

@Anonymous wrote:

I drew everything in the Mass In-Place. I'm not to familiar with the workflow of Revit in general. Am I supposed to not draw everything with Mass In-Place?


 

That's not the finality of what we do in Revit. Massing is a means to an end. What's the end purposes of the masses?  

0 Likes
Message 5 of 9

Anonymous
Not applicable

I drew with the Mass In-Place because I was following along a tutorial video for a footbridge that drew cross sections and connected them using the "Create Form" feature. I noticed that I was unable to create forms if I was not drawing in the Mass In-Place.

0 Likes
Message 6 of 9

barthbradley
Consultant
Consultant

I'm not totally following you. So you created one or more mass forms to host walls or roofs or what?  Can you direct me to the tutorial you are following?  

0 Likes
Message 7 of 9

Anonymous
Not applicable

Sure. I was following this:

 

https://www.youtube.com/watch?v=nXF2rAsp1Tk

0 Likes
Message 8 of 9

barthbradley
Consultant
Consultant

Ask your question over here.  It's not "trivial".  

 

InfraWorks Forum - Autodesk Community

0 Likes
Message 9 of 9

lucdoucet_msdl
Advisor
Advisor
Accepted solution

@Anonymous 


New Revit user question: This might seem trivial, but I noticed that when I open my revit my model does not appear by default, only when I turn on "Show Massing & Floors".

 


You can assign the default visibilty to any of your Revit views to show Mass elements in the visibility graphics settings.

 


My question is if I have this preliminary model and want to place it in InfraWorks to contextualize the design, will it even show up, since by default the model does not show up unless I specify to "Show Massing & Floors"?

Infraworks imports Revit files locally, if you have Navisworks installed, or as a cloud based translation depending on the setting in "Application Options | Data Import".

 

The Navisworks import will, by default, import the geometry based on the first 3d view prefixed with "navis" while the cloud import will use the default "3D" view in the Revit project. By setting the visibility graphics of either of those 3D views to show "mass elements", they will be imported to Infraworks.

There does seem to be a bug with the local Navisworks imported workflow as the first placement will correctly show the 3D geometry when interactively placing the model then disappear. Applying an override color will make it show up but then all material associations are lost and I can't seem to make them update.

 

When using the Cloud import workflow, the default transparent "Default Mass" materials import correctly and the geometry is immediately visible.

 

Hope this helps.

 

-luc


P.S. Image linking didn't seem to work when writing this. I've zipped screen captures of the original revit mass and the import results using both workflows (see attached file).