Tuesday, October 23, 2007

Revit Grids in NavisWorks

I've been struggling to find my bearings in NavisWorks because the grids from Revit are not 3d so they do not come into NW. I've come up with a pretty good solution in the meantime.
I created a 2-Pick family in Revit that I creatively called 'Grid.rfa'

image

The grid bubbles and the grid line are extrusions 1/4" high, I tried using Model Lines but they are just too hard to select in NW. The grid name/number are tied to a 'Grid' parameter.

I created an empty project that I linked the structural model into and proceeded to Copy/Monitor the grids into the project. From here I can use the pick option for creating the 2-pick family grids with 'Lock' checked.

image

Then all you have to do is set the 'Grid' parameter in the newly created grid.

image

Now what happens if the grid changes? That never happens so we don't have to worry about it....oops had a moment of insanity.

Since we copy/monitored the grids we can simply do a coordination review (look in help if you don't know what this is) the grids will automatically be updated and since we used the lock option to place the new 2pick grids they will move right along with the monitored grids. The only coordination you have to do is check the grid names and make sure there are no new grids, coordination review will not currently tell you if new grids have been added.

Now here's the cool part, when you select the grid in NavisWorks you can look at the properties and you instantly know what grid you're looking at. No need to track down the grid bubble.

image

I also found it useful to group the grids in Revit and then copy the group to each floor, that way it's always easy to find the grid in NW.

I anyone would like my Grid family just leave a comment or shoot me an email and I'll be happy to send it to you.

image

Wednesday, October 3, 2007

Autodesk's Negative Effect on NavisWorks

Although Autodesk pledged to not change NavisWorks the effect of Autodesk is hurting the program unfortunately. It's not Autodesk that is doing the damage though, at least not directly.

This was posted on the NavisWorks site today

"PLEASE NOTE THAT SOME THIRD PARTY VENDORS MAY ELECT TO NOT PROVIDE FILE FORMAT SUPPORT FOR NAVISWORKS PRODUCTS AS OUTLINED BELOW FOLLOWING THE SALE OF NAVISWORKS TO AUTODESK. WHILE WE INTEND TO WORK TO PROVIDE CONTINUED DIRECT THIRD PARTY FILE FORMAT SUPPORT WHEN POSSIBLE, IN SOME CASES, SUCH SUPPORT MAY BE DISCONTINUED DESPITE OUR PREFERENCE. WHEN FEASIBLE, A WORKFLOW CHANGE MAY ADDRESS SOME CUSTOMER’S NEEDS (E.G., EXPORT OF FILES FROM AN UNSUPPORTED THIRD PARTY CAD PRODUCTS INTO A FILE FORMAT SUPPORTED BY NAVISWORKS). PLEASE COME BACK TO THIS WEB PAGE FOR FURTHER UPDATES ON FILE FORMAT SUPPORT AVAILABILITY."

It's unfortunate that the 'other' vendors are taking away support for native file format, this coincides with a previous post regarding file exporters,  If more vendors pull native support because they would be supporting Autodesk then we have to have the originating program to export from to get quality models. Again this forces us into the position of requiring subcontractors to purchase NavisWorks. A free exporter would alleviate a lot of my concerns.