Hi Travis,
I smacked into that wall pretty hard with my own smoothing code tonight - 3963.dat uses a mix of hand-positioned faces and sub-part line rings to build the nozzles and the result is inexact vertices. The problem can be resolved in code by (1) also using a crease angle to catch the case where we 'lost' our line or (2) snapping the geometry to a grid.
Is there a minimum precision to the library (e.g. 1/16th of an LDU or something) that would allow programs to quantize part positions to catch such floating point problems without breaking small details? Or is there a minimum tolerance that library parts are checked to?
Cheers
Ben
I smacked into that wall pretty hard with my own smoothing code tonight - 3963.dat uses a mix of hand-positioned faces and sub-part line rings to build the nozzles and the result is inexact vertices. The problem can be resolved in code by (1) also using a crease angle to catch the case where we 'lost' our line or (2) snapping the geometry to a grid.
Is there a minimum precision to the library (e.g. 1/16th of an LDU or something) that would allow programs to quantize part positions to catch such floating point problems without breaking small details? Or is there a minimum tolerance that library parts are checked to?
Cheers
Ben