For use with SMS's Nlib. Allows reading and writing of VDAFS files to/from simple C++ data structures which leverage the Nlib library to represent all the geometry data in the VDAFS file.

Major features:
• Resistant to faults in the physical format of the VDAFS file.
• Reads all VDAFS geometry entities.
• Imports and exports points, curves, surfaces, and trimmed surfaces. TOP shells are read as independent faces only. BReps can be output as TOPs.

VDAFS/NLib requires Basic NLib. If necessary, we will work with SMS to provide an Nlib VDAFS booster pack to make these functions available without purchasing the full Advanced Nlib library.

For use with IntegrityWare's TSLib. This combines VDAFS/NLib with a sophisticated tool for creating proper trimmed surfaces from flawed real world data.

Major features:
• Everything listed above under VDAFS/Nlib.
• Sophisticated cleaning tools: eliminating minor self-intersections and gaps, improving singularities, etc.
• Supports conversions of IwBrep entities to and from VDAFS FACEs and TOPs.

VDAFS/TSLib requires TSLib and some functionality from Basic Nlib. HarmonyWare has an agreement with SMS which allows us to bundle the needed functions at no extra cost to the user. Ruled surfaces, offset curves, and offset surfaces require functionality from Advanced NLib. If necessary, we will work with SMS to provide an Nlib VDAFS booster pack to make these functions available without purchasing the full Advanced Nlib library.

For use with Solid Modeling Solutions' SMLib. SMLib is built around a core of Nlib and TSLib. Thus VDAFS/TSLib works perfectly with SMLib. VDAFS/SMLib, then, is VDAFS/TSLib plus the full support of Solid Modeling Solutions.

VDAFS/SMLib requires SMLib. All the needed Nlib and TSLib functions are included there, making the logistics much easier for all of us.

In their current form, we hope the translators should be able to handle most correct VDAFS data. Testing has thus far been more limited than we would have liked, but has been favorable so far. The good news is that once the file is read, the core conversion routines are shared with the IGES translator, and so are well-tested.