Hi igor,

> Sat File is not generated at all by Autocad, and if you save MoI
> sat as dwg - and then import it into Revit - you get the same
> result as if you would try to import SAT directly generated by
> MoI - shreres corrupted

Ah, well that is a good thing to send to over to Autodesk then that can help to show them the problem.

Send them a DWG file that contains that sphere in it as a 3D Solid entity, and tell them that when importing that DWG file into Revit it is missing in Revit.

That should help them to decide to take a look at it. They will be able to see that the DWG was written by AutoCAD so there should be no question that the file data itself is structured correctly.


> ARCS ARE Ignored!!! - (I suppose your .3dm have them!)

No, not in the files that you sent previously anyway - note that when it says: "Other objects, such as lines and arcs, are ignored." it is basically trying to say that "wireframe curve entities" like lines, circles, arcs, - meaning objects that are curve data and not solid or surface data are ignored.


> so if sat exporter will somehow convert surface definition and
> use (maybe circles or whatever autocad uses for definition -
> see any sat by acad)?

Yeah, the method that is used to store a sphere that was drawn in AutoCAD and saved to SAT is as a special "sphere-surface" entity in the SAT file.

Revit seems to handle those special sphere entities better than spheres that are saved as a general "NURBS surface" type entity.

I've asked the author of the SAT export library that I used if it will be possible to add a feature to export spheres using those special sphere entities, which may help to get this stuff working (I mentioned that in the previous message here).

- Michael