The .3dm converter is embedded in many products in addition to Okino’s PolyTrans|CAD.
Ten years after releasing their first Rhino/OpenNURBS .3dm file format support t0ol, Okino Computer Graphics announced today it is now shipping a rewritten, revised and optimized import/export converters compatible with McNeel’s Rhinoceros v5.
For more than 20 years Okino’s PolyTrans|CAD has been been allowing cross conversion between all major MCAD, DCC/Animation and VisSim 3D file formats + programs. Okino’s revised .3dm import/export converters work within the stand-alone PolyTrans & NuGraf products, PolyTrans-for-3dsMax, PolyTrans-for-Maya, PolyTrans-for-Softimage and within many third party products such as: 3DCreate (by Visual Components), Cinema-4D and its “Engineering Bundle” (by Maxon Computer), EON Reality, NGRAIN military training products, Pytha (by CATS Software), Quest-3D (by Act-3D), VirTools (“4DC” .nmo pipeline by Realicon) and others.
The newly released .3dm converters provide support for the following core aspects of the .3dm file format:
- Full cloning of Rhino’s recursive instancing of block definitions + its nuances during import,
- Recursive layer recreation,
- Trimmed NURBS surfaces,
- NURBS curves (single, composite and multi-segment),
- Polyline curves,
- Mesh geometry (with vertex normals, vertex uv texture coordinates and vertex colors),
- Import of child render meshes of Breps,
- 3D point clouds,
- Import of 2D vector text annotations,
- Viewport cameras,
- Ambient/spot/point/directional light sources,
- Materials and diffuse+bump+environment texture maps.
Okino started working on the Rhino format 14 years ago, and shipped its first native Rhino .3dsm import and export January 2001. With the new v5 release, Okino says complex Rhino files with recursive ‘block’ usage, alpha-textured objects and full scene attributes can flow out to export formats including SketchUp, U3D (for 3D PDF), Collada, FBX, OpenFlight, 3ds Max, Maya, Lightwave, and C4D with proper retention of the original Rhino scene data.