I had a similar problem, showing a free-form 3D-object from a construction program. I tried to import the model from a VRML file, but the appropriate VI "Load VRML File.vi" couldn't handle the complexity of the the file. I suppose this is also true for the other file loading VIs.
My steps were:
Exporting the 3D- Object as a VRML- file. I checked the correct export with the free VRML viewer/editor "
White_Dune". Since my object was a free form object, it didn't consist of geometrical forms, such as cylinders or cones but a great number of points, describing the surface. In the .wrl soucefile this is to be seen as a long row of numbers, surrounded by [ ] brackets. These numbers are the x-y-z coordinates of the points. I copied them to another file and made a VI to translate them to an array of <x;y;z> - clusters. These clusters could be used to view the points in a 3D Parametric Surface Control. I used this to determine the points, which are necessary to describe the object with adequate detail level.
Next step was to translate this cloud of points in a form suitable for the mesh- functions used by the 3D- Picture Control. I chose the easy way and projected all points on one plane (e.g. the x-z-plane) and determined the hull points of the resulting 2D geometry. This I could easily feed into the Mesh- VI. But this is not the solution for every problem.
If you have some questions or need explanations in more detail, please ask.
greets, Dave
Greets, Dave