Importing IGES NURBS Patch (entity 128)

Can anyone shed some light on the fact that the simple IGES file below does not import? It has only one surface entity, a #128 NURBS Patch.

Relevant part of import report:

================================================================= Precision analysis of IGES file: ================================================================= Most prevalent number of significant digits: 2 Highest number of significant digits: 7 Average number of significant digits: 1.66154 Maximum distance to origin: 18484.9 Minimum distance to origin: 0 Effective number of significant digits: 7

================================================================= Entity Summary =================================================================

----------------------------------------------------------------- Type Name Count Converted

---- ---- ----- ---------

128 Rational B-spline surface 1 0 314 Color definition 1 1 406 Property 3 3 _________________________________________________________________

The IGES file: (cut below line) _________________________________________________________________ S 1

1H,,1H;,, G 1 61HC:\Documents and Settings\System Admin\Skrivbord\Untitled.igs, G 2 26HRhinoceros ( Jun 6 2005 ),31HTrout Lake IGES 012 Jun 6 2005, G 3 32,38,6,308,15, G 4 , G 5 1.0D0,2,2HMM,1,0.254D0,13H060418.115057, G 6 0.01D0, G 7 18000D0, G 8 , G 9 , G 10 10,0,13H060418.115057; G 11 314 1 0 0 0 0 0 000000200D 1 314 0 1 1 0 0 0 COLOR 0D 2 406 2 0 0 1 0 0 000000300D 3 406 0 -1 1 3 0 0LEVELDEF 0D 4 406 3 0 0 7 0 0 000000300D 5 406 0 -1 1 3 0 0LEVELDEF 0D 6 406 4 0 0 0 0 0 000010300D 7 406 0 0 1 15 0 0 NAMETXT 0D 8 128 5 0 0 7 0 0 000000000D 9 128 0 -1 11 0 0 0 Ns_0 0D 10 314,0.0,0.0,0.0,20HRGB( 0, 0, 0 ); 0000001P 1 406,2,1,7HDefault; 0000003P 2 406,2,7,12HIGES level 0; 0000005P 3 406,1,4HNs_0; 0000007P 4 128,3,3,3,3,0,0,1,0,0,0.0D0,0.0D0,0.0D0,0.0D0,1.0D0,1.0D0,1.0D0, 0000009P 5 1.0D0,0.0D0,0.0D0,0.0D0,0.0D0,1.0D0,1.0D0,1.0D0,1.0D0,1.0D0, 0000009P 6 1.0D0,1.0D0,1.0D0,1.0D0,1.0D0,1.0D0,1.0D0,1.0D0,1.0D0,1.0D0, 0000009P 7 1.0D0,1.0D0,1.0D0,1.0D0,1.0D0,18000.0D0,0.0D0,0.0D0,12000.0D0, 0000009P 8 0.0D0,-600.0D0,6000.0D0,0.0D0,-600.0D0,0.0D0,0.0D0,0.0D0, 0000009P 9 18000.0D0,1900.0D0,0.0D0,12000.0D0,2800.0D0,-600.0D0,6000.0D0, 0000009P 10 1300.0D0,-600.0D0,0.0D0,0.0D0,0.0D0,18000.0D0,2100.0D0, 0000009P 11 1333.333D0,12000.0D0,3700.0D0,1333.333D0,6000.0D0,1600.0D0, 0000009P 12 1333.333D0,0.0D0,0.0D0,1333.333D0,18000.0D0,2200.0D0,2000.0D0, 0000009P 13 12000.0D0,3700.0D0,2000.0D0,6000.0D0,1700.0D0,2000.0D0,0.0D0, 0000009P 14 0.0D0,2000.0D0,0.0D0,1.0D0,0.0D0,1.0D0,0,1,7; 0000009P 15 S0000001G0000011D0000010P0000015 T 1
Reply to
Chebeba
Loading thread data ...

This question has come up before from probably the same hull out of Rhino3D? Anyhow, looking at it in Rhino3D (where it came from), it seems ok but at the base of the bow, the surface moves in to fast and creates a error in SW. BTW, I'm able to import this file into SW using the free *.3DM add-in. Still, the surface has problems in SW... here it is..

formatting link
..

Reply to
Paul Salvador

Thanks for your efforts! I have also discovered that placing two control points on top of each other (which is OK in many other apps) is apparently not OK in the SWX IGES importer.

/C

Paul Salvador skrev:

Reply to
Chebeba

Just for laughs, I saved the file as an IGES, and then opened it in SW...no more errors....

Reply to
cd

Hmm,... exporting the 3DM imported surface, using either 2005 or 2006, you should be getting this error,.. IGES-out complete. 1 face(s) failed to translate.

What you did was save all the bodies and you exported my lofted surface and you received the above error.

So, it did not export that 3DM imported surface.

..

Reply to
Paul Salvador

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.