3D Solid DXF

[rnowak]

Hi,

want to make 3DSolid in DXF from Code. Tried to read what Autocad does but it seems not readable. Need some tips or example how to make 3DSolid in DXF to make it read in Autocad. Want to be able to export solids from one application to Autocad.

[hgasty1001]

Hi,

ACIS 3DSolids information is encoded (by Autodesk in a proprietary way) in DXF, so it seems very difficult or maybe impossible to generate manually or by code a correct DXF list from scratch, Owen Wengerd has made some effort trying to decode the mess, but I'm not sure the state of his effort so far. Sure your software (what's the name?) has some export tools, check if AutoCAD or a vertical can read it.

Gaston Nunez

[rnowak]

Thanks for Yours opinion. But this is really strange, because all other types like Lines, circles etc. are really easy to code by hand inside DXF. Want to Autodesk to answer this. Like You said the code inside DXF for 3DSolids it is non readable. Thought about using ACIS *.sat instead of DXF but it seems that there is no specs of their documentation and making such exports need buying licence from them? It is strange for me that 3DSolids are such big problem for AUTODESK to handle normal way... It could be some short code for vertices and their interaction or just some planar shape with extrusion details and after that some solid operations.

[artc2]

The others are correct, the data is encrypted and even if you unencrypt it, the data is still not in any format that we document.

[rnowak]

Hi,

but please explain why it is so? It seems that You don't support 3D Solids in Yours file exchange formats. So what is the best documented way to import Solids into Autocad? ACIS *.sat I think that it is not free and there is no documentation available on the web, found sth but is not complete: https://www.google.pl/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=0ahUKEwiLxeCg493RAh...

[dgorsman]

There is no "simple" method for encoding 3D solids as ASCII data as they can be anywhere from simple boxes and spheres to very, very complex.  Just look at all the options available: IGES, STL, SAT, STP... and those are just the common neutral-language files, without getting into proprietary formats such as Rhino, Pro/E, or CATIA.

You might have better luck getting traction with the FBX format.  It is well documented and in common use, especially among the game and visualization development community.  You'll still probably end up having to purchase a pre-built module in order to work with the data though - building one from scratch based on the FBX standard is way too much work.  Kind of like reverse engineering MSXML or System.XML for working with XML data.

[artc2]

The decisions about how to do solid data in dxf were made over 20 years ago and I don't remember the details. Since that time there has not been enough demand to justify the time and resources it would take to come up with a public format, implement it, and document it.

[kerry_w_brown]

---

artc2 wrote:
The decisions about how to do solid data in dxf were made over 20 years ago and I don't remember the details. Since that time there has not been enough demand to justify the time and resources it would take to come up with a public format, implement it, and document it.

---

Art,

What would constitute "enough demand" ??

Regarding time and resources  required:

Does Autodesk have internal design documents on the format .. and internal documentation on the format ??

 Regards,

[artc2]

>>What would constitute "enough demand" ??
I don't know. I don't think anyone could answer that in a general way. For any given development cycle there has to be a prioritization of what is wanted to be done, and then the available resources are applied to that prioritzed list until they run out. So, what demand is required will depend on what other features are on the list for any given development cycle since that determines the prioritization.

>>Regarding time and resources required:
>>Does Autodesk have internal design documents on the format .. and internal
>>documentation on the format ??
I can't say.