IEGS export duplicate curves #278
Comments
|
I was experimenting with STEP export as well, and there I found that I've only got the surfaces, and no curves. That's a problem, because I want the surfaces to be lofted as native Creo objects, not imported bspline surfaces, so that the Creo model is simpler and more native, even if it's driven off of curves from OpenVSP. |
|
Can you please screen shot and attach the exact settings you used when exporting the IGES file? |
|
Settings:
The log: To be clear, I don't find that the curves are wrong per se, just that they are duplicative, and I'm wondering if this on purpose, accidental, etc. |
|
Thanks for the clarification. Most importantly, you're using the trimmed surfaces feature (not the un-trimmed feature available under the file-export menu). When two surfaces meet, we calculate a curve of intersection. That curve exists in XYZ coordinates, but also in UV coordinates of surface A and UV coordinates of surface B. If it is a boundary curve, it can be expressed as a set of control points along the boundary of surface A and also along the boundary of surface B. These boundary curves apply along feature lines -- the Geom as a whole is split into separate surfaces along feature lines. In OpenVSP, the SurfA and SurfB representations of these split-line boundaries will always have identical control points, but this is not true for all forms of CAD. In general, it is possible for a curve to have two different representations that are approximately equal in XYZ. It may be possible for us to recognize this situation and re-use curves more intelligently. However, figuring that out will take a deep dive into the code for writing out intersected STEP and IGES files. This kind of activity might be in the plan of work in the coming months, but it won't be a near-term thing. I will keep this issue open to document this question, but don't expect any movement in the short term. |
In dupcurve.zip, there are two sections in the wing. In the IEGS export for the wing, there are more curves than strictly necessary to define the wing (screen cap from Creo's "import data doctor", which gives detailed info on what data is coming in during an import):
There are 24 objects of type curve:
For example, each surface has 4 curves around it's outside. But that causes duplicate curves at the end caps, and on each "bulkhead" in the wing profile. My ideal number of curves here would be 10: 2 for the leading edge, 2 for the trailing edge, and 2 each for the 3 stations. Having the chord curve in the end caps is annoying, but manageable.
I don't know if this is expected behavior, accidental expected behavior, or a bug.
It came to my attention because when importing into Creo in order to get a very clean, simple, native-to-Creo structure, I needed to get rid of all of these extra curves. (There are built-in simplification algorithms in Creo, of course, but I don't want them moving my splines around and messing up my aero surfaces.)
The text was updated successfully, but these errors were encountered: