3D Interoperability

[rln]

Hi all,

Developing an ACIS writer I am using several viewers to verify how resulting files are being processed. This is not trully reliable as these viewers seem to be sensitive to some data (either missing or presenting). So I would like to ask a few questions on expected contents of the ACIS files.

I would appreciate any feedback on the following issues.

1. Storing pcurves

When should coedge's pcurves be stored ? Does this depend on underlying surface type (e.g. for splines only but not for spheres or cones) ?

2. Degenerated edges (i.e. those correspond to surface singularities, like sphere poles)

a. Should they be always stored / always skipped / depend on surface type ? For the latter for which surface types (spheres, cones, splines) are they recommended ?

b. If a degenerated edge is stored what are recommended (or mandatory) values for start and end parameters of the curve as there is no actual curve ?

c. Should degenerated edge's coedge always refer to pcurve ?

3. Intcurve (spline) curves.

a. Are there any preferences regarding which type the curve should have (e.g. exactcur vs surfintcur) ?

Any other recommendations, pieces of advice would be very appreciated.

Thank you very much in advance.

Roman

[ybiyani]

Hello Roman,

We recommend that you license ACIS to read and write into SAT format and that should address all the questions raised here as we will handle that for you. With InterOp we provide a Connect SDK to enable reading and writing from any formats that we do not support.

Regards,

Yogesh

[rln]

Yogesh,

Thank you for your prompt response. At this moment, this does not really look as a viable option for me as it would imply upfront expenses which I cannot afford. Also source code is an important factor. Anyway, if there is anyone from your sales team willing to contact me I am available to discuss available approaches.

Roman