![]() ![]() ![]() If NX writes out trimming curves for a closed surface where the trimming curve crosses right over the seam edge, MoI has to cut those particular edges up into separate pieces where they cross over the seam (because UV space ends at the seam), and that can be a kind of delicate operation and it's likely to be what is not working quite right on that particular example. The main difference between these is on surfaces that are closed and have a "seam edge" in them like that particular one. The way NX and also STEP format handles trim curves is a bit different than how MoI handles them - MoI handles trimmed surfaces by a UV space boundary in addition to the 3D edge curves, while NX/STEP can contain only 3D trimming curves. Hi sneather, it's probably happening while MoI is reading the STEP file. So, I know whatever they are doing in NX, it's working fine for their production. Or none of the above? Maybe it is, indeed, just bad geometry, or more specifically the method by which NX simple creates its files? These are real products, which are used to make the tooling and molds for the final pieces. Or is this something that is happening when MOI is reading the STEP file? So, is this something which is happening when NX is writing the STEP file? I assume this is happening inside NX, but when the designer looks, he says it looks fine on his end. There arr more instances like this, elsewhere. I'm attaching a stripped-down section of just one part, which shows the odd sweep piece, inside a rounded curve. They're using NX Unigraphics, and I have them exporting STEP 203 and 214 files (as I have no idea what the difference is.).īut I'm immediately seeing some areas of bad geometry in MOI. I'm receiving some product CAD files from a client. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |