I don't know if this is a factor as I haven't used the tool, but when snapping to points or objects to align things, be aware that if the objects have elevations then the Z values will influence the alignment and cause a skewing effect in the results. If you use a Z point filter at zero when snapping to the objects you can eliminate the skewing effect.
I was snapping to 2D points. Unless your telling me that OSNAP doesn't work anymore, I don't see why snapping to 2D points is a problem.
Jack/All. Firstly I'm not a Revit user and am only following the input from others here so any pointers would be usefull.
We have been using the BIM Coordinator between Civil3d & Revit for a while now and we seem to get problems in positioning the data after importing the MXL into Revit on most projects requiring manual positioning and rotation of linked drawings.
Obviously I (in Civil3D) always use true coordinates in my models based on 0,0. Most of our models are located either in OS Grid or Site Local grid.
The first time we used this it worked fine apart from the Elevation being incorrect (My fault), the second time with the corrected level it didn't seem to update the level in revit but since we imported the architects model into Revit the coordinate system seems to have gone wrong.
Could the architects model coordinate system be effecting / overwriting the Structural coordinates without human interaction?
We also seem to get issues when we import the system more than once. Can this only be done only once in the project cycle or can a coordinate system be changed at anytime?
Simmilarly, when a project has been already modeled in RevitS and we import the information the model comes in rotated, we have tried project / true north and shared/centre to centre to no avail. Any Ideas here?
I have read online for manualy doing this creating a master file for the coordinate system and importing the coordinate system from this to the other models in Revit. Is this a prefered method to fix the corrdinate system and syncronising to the master document, does it make a difference?
I am wondering if we should be importing the Coordinator file prior to any modelling but it is highly possible that most of the above is actually caused by improper import process of the drawing etc. into revit or points which Revit won't like from civil3D.
Can we have a step by step guide in PDF format for the process as well as some do's and don'ts if there are any for the setting of points in Civil3d / Revit.
I am trying to import a Civil 3D surface in to Revit Structure 2013. I have tried the 'Integration with AutoCad Civil 3D extension' and importing contours. The Civil 3D surface contains numerous breaklines for kerbs etc none of which are reflected in the Revit toposurface. The only accurate way I have found to import the surface is to form an Autocad 3D Solid from the Civil 3D surface and import this via a modelled in place mass component. Am I missing something?
Nope sadly you are not missing something, Revit will not hold the surface data from Civil3D. It rebuilds based on the imported information and its own program logic.
Whether you use points, contours or Triangles it will only generate a surface using points from these objects.
I think you have found the only way of obtaining a true object model from the Civil3D surface, we have tried numerous methods and have not obtained a suitable result to date.
For my intrest as we just gave up on surfaces in revit..
What workflow are you using for 3d solid and import to revit, can you section and aquire true level data from the imported solid?
The technology preview will end on January 12. Thanks to all who participated.