DWG 2 Revit

I have been running into a small issue with linking dwg (2013) files into revit 2013 with the setting: 'current view only' unchecked. So far it seems that if you have setup shared coordinates like I have been describing in several blog posts you can get a wandering dwg file in you revit project. With wandering I mean it seems to ignore where it's supposed to be. 


If you have linked a dwg with the setting that you want to view the dwg in all views (the current view only is unchecked) and you save the project with a view open that has been set to True North than you can get a misplaced dwg file the next time you open the project. 


So far the trick seems to be to set the view to project north and reload the dwg from the managed link dialogue box.


It seems that when a drawing has been linked to current view only it does not happen. Or at least not for me... yet


Disclaimer
http://danielgijsbers.blogspot.nl/2012/08/disclaimer.html

Navisworks 2013 and revit files

In Navisworks 2013 you can now append rvt files straightaway. Your rvt files still get converted to a nwc file. Bear in mind the following if the rvt file is of a lower version than 2013 the file get's updated to 2013 first and next it's being converted to a nwc file


Important: the original rvt file is not upgraded!!! Don't worry! I am merely writing this to let you know that the conversion process will take a long time if you are appending big rvt files. You might want to consider creating the nwc file  in revit if you are using a older version than 2013 release.


Also you want to create a 3D view in revit called Naviswork. If you append rvt files you can set the rvt file reader in Navisworks to search for this view and only export those elements that are visible in this view.

Notice that my export settings are set to export in feet. Of course I work in the  metrics system but Revit itself runs on an imperial engine... If you set it to millimeter or meter your properties / quantities will be wrong.


Perhaps sometime we should let Autodesk know that the majority of the revit users work with the metric system and they do not want their units converted to imperial.


Disclaimer information
http://danielgijsbers.blogspot.com/2012/08/disclaimer.html

2013 releases

Small blogpost:

So far I haven't seen any differences yet in the main workflow of getting stuff from civil 3D 2013 to revit 2013 and vice versa. But I still have much to test.

more later



Disclaimer information
http://danielgijsbers.blogspot.com/2012/08/disclaimer.html

Geomarker Civil 3D

In an earlier blog http://civil2revit.blogspot.com/2011/09/coordinates-again.html I already mention the geomarker and how the revit extension seem to use the geomarker to exchange date between Civil 3D and Revit. 


I do not think that that is a good point to use. Specially when you look at the following:


I have recorded a screencap from Civil 3D. I only have a surface in and I'll do the following:

1. turn on the geomarker
2. edit the geomarker
3. put the geomarker to another position
4. save the dwg

screencap

What you will see in the movie is that when you invoke the save command the geomarker jumps back to center of the site. I don't think that the center of a site is a handy point for exchange since if the site changes size the center point and so the exchange point changes...


A bit of googling on geomarker on got me this: http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=11729142&linkID=9240697

It would be really great if the geomarker would behave the same as the project basepoint does in Revit. Funny knowing Revit's problems with large coordinates I never thought I would suggest another system to use some of Revit's techniques.

If anyone else can shed some light on the geomarker and how to keep it fixed I would be very gratefull!



Disclaimer information
http://danielgijsbers.blogspot.com/2012/08/disclaimer.html

True North it is

So once in a while you run into something that is completely obvious when you look back at it.


I have written before about the true north and project north issues with Revit. (It gives problems with linked files) I have asked myself before why bother with project north at all. Probably because of working in Autocad before. I tried to to the same in Revit. In Autocad you want lines to be horizontal or vertical, if possible.


But with all the nice tools in Revit it's not really necessary. Section are easy to draw, parallel to grid lines and elevations orient themselves perpendicular to walls. The only thing that's left are the floor plans. Some projects will probably look stupid if you don't rotate them. Some things might become difficult to read.


If you work solely in Revit and you have no need to link in other files than do use project north it's easy to setup. If you do need to link in site plans or something similar see if you can get away with it not setting up project north.



Disclaimer information
http://danielgijsbers.blogspot.com/2012/08/disclaimer.html

exchanging surface between civil 3D and Revit

Today we ran into another oddity in the whole coordinates story...


I like to set the project base point manually. I do this in civil. I choose a point with nice numbers and put a little x there. To get surfaces from civil 3D into Revit I like to use the Integration with Civil 3D extension. In order to exchange surfaces between Civil 3D and Revit I create an extra surface that has it's center spot exactly upon the project base point. This is a dummy surface for which I am sure that it will not move or change shape! (see previous post why I do that)


Today I had to check something and I didn't bother to setup my project basepoint on a nice round number. And guess what, it turns out that Revit didn't put the project base point where it is in Civil 3D but it moved it to a nice round number...


In civil 3D the ID of center of the surface is: (meters)
X = 235013.1029     Y = 580515.5750     Z = 0.0000

Revit creates a project base point at n/s 580515500.0  and e/w 235013500.0 (Millimeters)

You can also see that the project base point is off center. 


I redid the whole thing but then I used nice numbers in civil and then Revit did use the same coordinates....
So instead of these  X = 235013.1029     Y = 580515.5750     Z = 0.0000
I create the point at X = 235000.0000     Y = 580500.0000     Z = 0.0000


Recommendation: Create your own project base point in Civil 3D and put it on a round nice number! Create a dummy surface that has it center on your created project base point. Get only that surface into revit first and CHECK the project basepoint numbers!



Disclaimer information
http://danielgijsbers.blogspot.com/2012/08/disclaimer.html

More coordinates again

In revit 2011 release I thought we finally had this shared coordinates thing fixed. 2012 proved me wrong. If you also want to use the bridgemodeler extensions you are really in for some puzzling. This video will not cover that. This video will cover setting up shared coordinates and the true north project north rotation. In you want to use the integration with civil3D extension don't use this method.


After a recent project I ran again into trouble with Revit and keeping a dwg on the right position. After quiet some testing I produced a system that seems to work.


I chose to do it manually so I am much more aware of what is happening. I am still experiencing that reloading a dwg gives weird results. Closing the revit file and reopening seems more stable for the position of the dwg.


I captured a video showing the steps that work for me. I hope it will help you out. Please let me know your experiences.

 (watch it on youtube and set it to 1080p)

Disclaimer information

http://danielgijsbers.blogspot.com/2012/08/disclaimer.html