OK, my point about all of this is...yes STL are for RP machines. I have two Zcorps machine. Now every now and then we get a model that was done in something other than SW. There are certain tolreance issues when it comes to our RP machine. Now if I cant measure these files to see what kind of dimensions that I am looking at, what good does it do me to just "look at it"?
So this leavs you with the follwing work arounds...
1) Either 3rd party add-ons, another "file" data translator program to buy and load and use and figure out the proper settings to get from one program to the next with out losing too much in the process.
2) Get it as another format and translate it into the STL later.
Maybe I am just asking for too much. It would just be nice to have all of these software companies get off that high horse of "this my software" and i am not willing to share my data code. Not asking them to open up everything. Maybe someone truly needs to come up with a 100% neutral format (ie IGES) that can really take what you have in one program and bring it to another with out having it be "dumb" or some visual reference that I am just looking at.
And yeah Mike, I knew about your STL importer. I was actualy trying to get the department to purchase it, but no luck. I guess you were a bit peeeved when you saw that. I do stilll like the NURBS based surface add-in that you have. Questions it what will you do when SW adds it into their program natievly?