Hello Amitabh,
Consider adding filtering along your loops, here are some ideas, i'm not sure they are valid for your case:
1. Iterate only Solid bodies
2. Iterate only Planar faces
just in-case your application is a dll attached to NX session consider replacing it with exe, you'll get better...
There are 3rd parties software that have a solution for your problem.
here is a link to one of them http://www.transcendata.com/solutions/proficiency/index.htm
If you do not need features information, you can export/import the file using Parasolid. it will create you dumb geometry in a correct assembly structure.
Writing code to do that is possible, though can be tricky if you have internal dependencies like expressions.
The way you are accessing the file looks ok (i don't think it is the cause of the performance problem). Having said that, i think my suggestion is more a style issue.
I think the suggestion about UF_DISP_set_display is very easy to implement and can boost your application.
For better...
There are 3 Things you can do to improve the performance of this program( well 3 that I can think of ):
1.This is a general programming advise, not specific to NX: You can store all the data you are collecting during the while loop in a data structure. Only when the loop is done, creating/...
Mark,
You can have any Microsoft compiler with the windows SDK for free, so you don't realy need Visual Studio at all.
The free express Visual Studio is good enough for developing applications, having said that, if you need connection to some kind of source control and/or would like to enhance...
What is your definition for nonparametric feature/body? if your data is from STEP/IGES/PARASOLID than all the bodies are not parametric. But if you have a body that is build from 2 non parametric bodies and unite between them is it non parametric? I think the answer to this is not so clear...
But GTAC did mentioned NX8, I just didn't mentioned it before, from GTAC : In NX8, where pattern feature has replaced instance feature, selecting the move object feature for a pattern results in the following message:
Move Object(20) is not supported and will be ignored.
‘Instanced Body (18)’...
To make a long story short, here is what we are doing:
The project I’m working on is a software project. Its goal is to read CATIA V5 parts/assemblies/drawing and using NX Open API create “identical” parts in NX, or in other words “feature base exchange from CATIA V5 to NX”. A 100% success...
