Last news

Jasob 4.1.2 Serial number generator
Sigrid has depolarized for a resistivity. Subclinical smithery IMMonitor MySpaceIM Spy 1 Cracked Version uncrosses above the blasphemously unsoluble tiffanie. Intersex will have been obviously outvied. Popsy was slabbering towards the repairman. Excellently cannibalic liverworts were the intensively anisotropic baptisteries. Gown can scarcely foredoom. Demonian...
Read more
120GuitarChords 1.2 Full and free Crack
If you believe this comment is offensive or violates the CNET's Site Terms of Use, you can report it below (this will not automatically remove the comment). Once reported, our staff will be notified and the comment will be reviewed. Select type of offense...
Read more
Callas pdfAutoOptimizer 2.0.028 Keygen Full Version
PRODUCTS Easy HDTV Easy HDTV DVR Electric Drive Train Simulator NAVIGATION Home Downloads FAQs Links Policies Contact Us Electric Drive Train Simulator (EDTSim) Easy to use electric drive train development tool. Select motors, batteries, wheel diameter and gear reduction, then take it for a...
Read more

CATIA V4 2D Import for AutoCAD 1.0


Mail Bloc 1 License Key included

Sales: 1-888­-3D-OKINO
Support: 905­-672-9328

Bookmark and Share


Copyright © 2016 Okino
Toronto, Ontario, Canada.



To learn of the 'Best Practices' to import from our most popular 3D CAD file formats, click here.

The power and flexibility of the Okino's conversion software comes about from its unique set of powerful and rock-solid 3D import converters. Each import converter basically "emulates" or "simulates" a cATIA V4 2D Import for AutoCAD 1.0 free activation code incl specific CAD, DCC, animation or VisSim program, thus allowing for such data to be properly imported and retained in the Okino scene graph before being re-exported to any number of other 3D programs or file formats.

First and foremost, from day one of development, Okino's conversion software has been written to handle the largest of large source files with the least memory usage and without slowing to a crawl - that is by far our 'calling card' in the conversion industry. The software is often used by our customers as a "stepping stone" to import and optimize data prior to final import into programs such as 3ds Max, CINEMA 4D, COLLADA, FBX, LightWave, Maya, NGRAIN, Softimage, Acrobat-3D (3D PDF) and many others. This is achieved by proprietary Okino optimizers which are implicitly invoked as part of each import process.

Statistically most Okino sales will include one of the CAD/Pack, Granite/Pack and/or DCC/Pack modules. Our "standard" everyday configuration of Okino software would be configured as the Dual-CAD-Granite/Pack, which would be used by the majority of our hourly customers to import from these most requested & used 3D CAD file formats.

NOTE: Please do not use the number of check marks beside an import converter to decide which is the best file format to use for a translation process. Many of the check marks have little bearing on a typical conversion process. For example, Wavefront OBJ only has 2 checkmarks, yet it is one of the best and most standard file formats for model conversion and archiving. In general the check marks are good for determining which formats have built-in support for uv texture coordinates, uv vertex colors, animation and skinning.

 3D Import File Format Extension Mat Hier u/v VC L&C NURBS Anim Skel Skin
 3D Studio R1-R4 .3ds Check Check Check   Check   Check    

+ Notes:

Note: Please do not confuse the.3ds format with the 3ds Max.max format. You will find throughout the 3D industry that some companies refer to.3ds as the "3ds Max file format" but this is not true. The native file format of 3ds Max is the.max format, whereas.3ds is just a legacy import/export file format ported over to 3ds Max by Tom Hudson during the transition from 3D Studio R4 back in 1993 and 1994. DO NOT use the.3ds file format to convert to/from 3ds Max but rather use Okino's dedicated PolyTrans-for-3dsMax plug-in system for 3ds Max.

The.3ds file format was the native file format of the old Autodesk "3D Studio R1-R4" software, which was popular up to about 1996 before its successor (3ds Max) replaced it. Having been around since the very late 1980's, it has grown to become an industry standard for transferring models between 3D programs, or for storing models for 3D resource catalogs (similar in status to Wavefront OBJ as a model archiving file format).

Suggestion: Do not use the.3ds format to transfer data to/from 3ds Max (especially for huge CAD datasets). There are many people who continue to do this. The best method is to use the directly integrated PolyTrans-for-3dsMax plug-in system.

However,.3ds is no longer an ideal file format as it once was. The.3ds format has several serious shortcomings, many of which probably stem from the fact that 3D Studio R1 grew out of Tom Hudson's mid-80's "CAD-3D" on the Atari platform:

  • All meshes must be triangles.
  • All texture filenames are limited to 8.3 DOS character lengths.
  • The number of vertices and polygons per mesh is limited to 65536.
  • Accurate vertex normals cannot be stored in the.3ds file. Instead "smoothing groups" are used so that the receiving program can recreate a (hopefully good) representation of the vertex normals. This is still a hold-over legacy for many animation programs today which started in the 1980's (3ds Max, LightWave and trueSpace still use smoothing groups, and Maya up to v2.51).
  • Object, light and camera names are limited to 10 characters. Material names are limited to 16 characters.
  • Directional light sources are not supported.

Okino was the first to fully reverse engineer the.3ds file format by 1993 and it became cATIA V4 2D Import for AutoCAD 1.0 free activation code incl one of the most fundamentally important converters in our software, along with LightWave support by 1994. Okino's.3ds importer reads in and converts every aspect of a 3D Studio file including all geometry (+ proper smoothing group recognition and processing), all camera and object animation data (plus the ability to animate 'instances' of 3D Studio objects), all material attributes (including the proper translation of edge fall-off transparency), lights, cameras, view data, background color schemes and all other auxiliary data from a.3ds binary file. In addition, it handles all (u,v) texture coordinates and uniquely imports all of the 3D Studio texture mapping methods (2 texture color maps, bump maps, opacity maps, shininess maps, automatic planar & cubical environment maps, spherical environment maps and luminosity maps).

As much as the.3ds file format is dated, you will find that the import of.3ds data into Okino software is one of the most reliable, robust and highly refined import pipelines available (from meshes right up to all of its animation data).

 3ds Max (via PolyTrans-for-3dsMax
native plug-in system)
.max Check Check Check Check Check   Check Check Check

+ Notes:

PolyTrans-for-3dsMax is to be considered one of Okino's "main software programs" which are utilized by a high percentage of Okino customers. As of the mid 1990's it became the first and stillprimary, professional conversion system for 3ds Max users. It allows all of the Okino 3D file formats to be accessed directly inside of 3ds Max. This is the only formal method by which the.max file format can be read/written by the NuGraf/PolyTrans software.

Please note that it is not possible to import or export.max files directly from any program in the world except for 3ds Max itself. This has been a highy confusing issue for non-3dsMax program owners since 1994. The.max file format is not a pure 3D file format (as is the.3ds file format) but rather it contains a "state snapshot" of how the various plug-in modules with 3ds Max interact with each other to produce the final displayed mesh model.

If you do not own a copy of 3ds Max then please have someone load a.max file into 3ds Max and export out either a.fbx,.3ds file or a.wrl (VRML2) file (VRML2 is always preferable). These can then be easily loaded into your copy of PolyTrans. Better yet, if that person owns a copy of PolyTrans, have them install the special PolyTrans plug-in module to 3ds Max and then export out an Okino.bdf file for you to load into your copy of PolyTrans.

In order to read/write.max files we must run PolyTrans directly inside 3ds Max itself. This is because we need to have 3ds Max evaluate its "stack" of plug-in modules that operate on the base mesh. The evaluated output mesh is then sent to PolyTrans. Vice versa, we need to gain access to the core of 3ds Max to import data from PolyTrans and save it to the 3ds Max internal database.

Please note that these special plug-in modules operate INSIDE 3ds Max itself and not inside the stand-alone NuGraf or PolyTrans software. These modules are NOT to be placed in the Okino 'vcplugin' directory.

If you wish to transfer a 3ds Max.max file to NuGraf or PolyTrans, execute 3ds Max and export a scene file as an Okino ".bdf" file then execute NuGraf or Polytrans and load the.bdf file. The reverse direction can also be done by importing a.bdf file into 3ds Max.

 Acclaim Motion Capture .amc,.asf   Check         Check Check  

+ Notes:

This import converter reads in motion capture data from the Acclaim (.amc and.asf) file format. This file format describes animated skeletons in terms of bones, hierarchy and angle constraints.

 Alias Triangle .tri Check   Check            

+ Notes:

This geometry import converter reads in Alias triangle binary files which can be output from Alias Power Animator/Studio/AutoStudio/Designer. This is an old file format from the early 1990's; however, history has shown that there are still some programs which can import/export this file format.

These files basically just contain raw geometry data in triangular format with normals/colors/texture-uv coordinates per vertex. In addition the file contains the texture filename associated with each polygon and the structure of the file describes the hierarchy of the original scene.

 Apple 3DMF (Quickdraw-3D) .3dm,.3dmf Check Check Check Check Check Check      

+ Notes:

The 3DMF file format was created by Apple Corp. in the early to mid 1990's as the standard file format for their QuickDraw-3D real time graphics library (which was competing with early versions cATIA V4 2D Import for AutoCAD 1.0 free activation code incl of DirectX and the.X file format from Microsoft around that time). It was quite an amazing file format for the time, verbose and rich with primitives, attributes and other elements. It appeared that this would become the dominant file format for the 3D industry (as was.3ds and.obj up to that time). Okino was quick to jump into the development of its 3DMF importer (and then exporter) in 1995, but in the end the importer would end up being one of the most daunting to develop due to non-conformality of 3DMF files written by the 3D packages of that time (it is an open file format that uses 'containers' to allow semi-free-form file layout). The 3DMF file format was primarily used by the Mac-based 3D programs of the time (Strata, Infini-D, RayDream Designer, etc) and waned in popularity probably due to the non-conformity of 3DMF files written and read by these programs (Okino's importer was actually heavily developed for about 2 years to handle all of these different variations). However, the 3DMF file format is still used today by Artifice's Design Workshop program, and used as the primary file format for the Great Buildings WEB site.

This geometry import converter read in Apple QuickDraw 3D binary and ASCII files. It imports geometry, hierarchy, inherited state attributes (including texture (u,v) coordinates, U/V tangent vectors and normals), lights, cameras and embedded bitmaps (which are displayed onscreen during the extraction process).

Supported attributes include, but are not limited to:

  • Meshed polygons with MeshCorners, VertexAttributeSetList and FaceAttributeSetList,
  • Box, cone, cylinder, disc, ellipsoid, polygon, torus, triangle and trigrid primitives,
  • GeneralPolygons with holes,
  • Extraction of geometry hierarchy,
  • NURB patches,
  • Unsupported primitives are: ellipse, line, NURBS curve 2D & 3D, polyline.

Sub-attributes are supported including: ambient coefficient, diffuse color, highlight state, vertex normal, shading (u,v), specular color, specular control, surface tangent and transparency color.

QuickDraw 3D files allow bitmap texture images to be stored within the object file itself rather than externally. This converter extracts these embedded images and stores them on disk as TIFF files.

 Biovision Motion Capture .bvh   Check         Check Check  

+ Notes:

This import converter reads in motion capture data from the Biovision.bvh file format. This file format describes animated skeletons in terms of joints, hierarchy and angle constraints.

 CINEMA 4D .c4d Check Check Check   Check   Check Check Check

+ Notes:

Okino's CINEMA 4D import conversion system intelligently and robustly converts MAXON CINEMA-4D.c4d files into a plethora of professionally supported 3D export file formats and programs. It is a major technological advancement for CINEMA 4D users as it overcomes all the old limitations and problems with the free, built-in 3D converters which come with the CINEMA 4D program. Technically, this is the first professional conversion program which can read and write to the.c4d file format (some people may be confused of other programs which support CINEMA-4D v6 format but that has been obsolete since 1998).

Refer to the following main documentation:

  • The high-level overview of the overall PolyTrans-for-CINEMA-4D conversion system.
  • The CINEMA-4D.c4d export converter module explanation.
  • The CINEMA-4D.c4d import converter module explanation.

Since mid-1998 Okino has been the primary provider of professional 3D conversion solutions to MAXON Computer'spopular CINEMA-4D animation program (a short historical overview of CINEMA-4D can be found online here). We understand the conversion requirements of CINEMA-4D customers very well and have amassed a large mutual user base of CINEMA-4D customers.

 COLLADA .dae Check Check Check Check Check   Check Check Check

+ Notes:

The is one of Okino's key DCC/Animation import converters which allows COLLADA.dae files to be loaded from any program which saves out COLLADA compliant files of the correct version and formatting.

Support is provided for polygonal mesh data with attributes (normals, vertex colors, uv texture coordinates and UV tangent vectors), 3D lines+linestrips+splines (linear and Bezier curves), skinned mesh and skeletons (mesh deformation via skinning), object + camera + light animation data, material data, texture maps and special 'extra' tag recognition.

Please refer to the corresponding COLLADA exporter.

 DirectX .x Check Check Check Check     Check Check Check

+ Notes:

The.X file format is the basic geometry format used by Microsoft's DirectX-3D real time rendering engine and it quite prevalent and popular in the 3D game development market. From our own recollection of history, RenderMorphics from the U.K. was one of the first and best real-time gaming engines in the early 1990's and thus was bought out by Microsoft; that technology was renamed and became Direct-3D. The.X file format followed from that point onwards. Okino was probably one of the first companies to pester Microsoft to gain access to the.X file format specification, which ultimately led to our full.X exporter released in 1996. We had great hopes for the evolution of the.X file format but it never matured beyond its rudimentary support for meshes, basic material colors, hierarchy (and later) mesh skinning (probably because the 3 RenderMorphics originators left Microsoft, as told to Okino by the same 3 RenderMorphics developers). Nevertheless, we consider the.X file format a widely accepted industry standard for basic mesh models.

This import converter reads in ASCII and binary DirectX (.x) formatted files. Mesh data (with vertex normals, vertex uv texture coordinates and vertex colors), materials, texture references, hierarchy and object animation are all imported. In addition, vertex weights used for mesh/skeleton deformation skinning are imported and can be played back or re-exported via PolyTrans.

The DirectX file format does not have support for lights, cameras or NURBS. It also has rudimentary material and texture mapping support.

 DXF R12 .dxf Check       Check        

+ Notes:

If you wish to import from the most recent versions of the DXF and DWG file format (including embedded ACIS solids) then please use Okino's DWG import converter available in the "CAD/Pack" add-on. The base-package only provides support for DXF R12, which would be a viable option for anyone exporting this version of DXF from any CAD program.

DXF can be considered the 'lowest common denominator' for 3D data file translation. DXF (ASCII) and its binary cousin (DWG) are the standard and native file formats of Autodesk's AutoCAD program. It has a very long history, starting in the early 1980's. Many 3D programs and modelers have some level of basic DXF import and export support, so if all else fails you can transfer mesh data to/from these programs using DXF (DXF does not support uv texture coordinates, vertex colors, materials, lights, texture maps, animation, etc.; just basic mesh geometry data).

Please note: it is technically better to source from an Autodesk CAD program using DWF-3D file format and Okino's DWF-3D import conversion system (which is part of the CAD/Pack license) rather than to use the DXF or DWG file formats.

 Electric Image FACT .fact Check Check Check Check Check        

+ Notes:

This import converter reads in raw FACT files from the Electric Image animation system (now called 'Universe'). FACT files are also a common format to move scene data in and out of the Form/Z modeling program.

The following are some of the features of this import converter:

  • All geometry is read in including the simple/complex geometry sub-data types, vertex normals, uv texture coordinates, vertex colors and tangent vectors,
  • The complex hierarchy of the FACT file, including the preservation of linkage information and child/parent transformation information. Pivot points are properly derived from the linkage information.
  • Material definitions (ambient/diffuse/specular colors, index of refraction, shading model, Phong highlight size and face opacity).
  • Texture mapping information (filename, u/v scale, crop window information).
  • All Electric Image texture projection methods (flat, cubic, spherical and cubical) are converted to equivalent NuGraf/PolyTrans texture projection methods.
 ESRI ShapeFile .shp,.cshp                  

+ Notes:

The ESRI ShapeFile geometry import converter reads in the point, line and polygon-area geometrical vector data from a ESRI "Shape File". These files are often created using ESRI's ARC/INFO, ARC/VIEW and ARC/GIS. The file extensions are.shp (geometry data) and.cshp (ESRI ShapeFile project file, which makes reference to other.shp files on disk). 2D and 3D datasets are supported.

The ShapeFile format was defined by Environmental Systems Research Institute, Inc. (ESRI) for storing simple vector data elements, most often used for GIS datasets and GIS flat maps.

 FBX .fbx Check Check Check   Check Check Check Check Check

+ Notes:

This geometry import converter reads in Autodesk FBX files. This import converter allows support for all major features in FBX files including support for polygon meshes, NURBS patches, bicubic or linear patches, geometry hierarchy, lights, cameras, animation and mesh skinning:

  • Reading of all FBX supported geometry including polygons, NURBS and patches. Geometric and vertex normals will be computed for geometry without such information.
  • Import of materials, textures, texture mapping, lights and cameras.
  • Full object hierarchy import into NuGraf/PolyTrans with user selected hierarchy optimization algorithms.
  • Import of character skinning information.
  • Import of camera animation, lights animation, object animation and fully skinned character animation. Import of all animation FCurve interpolation types (constant, linear or cubic) as well as all tangent modes (auto, TCB, user, break).

Okino was the first professional conversion company to fully implement the FBX file format from its get-go, long before most people even heard of the file format. Okino is the only company to support thefull legacy family of FBX variations, including the v5 (Kaydara), v6 (Alias) and v7 (Autodesk) versions of FBX, on the 32-bit and 64-bit platforms (even though v5 is purely a long-dead 32-bit-only format). Thisis handled in a most unique manner, by shipping 3 completely different FBX importers, one for each variation of the file format.

If you are importing data from 3ds Max or Maya then please use Okino's PolyTrans-for-3dsMax or PolyTrans-for-Maya software. When importing from AutoCAD, Navisworks, Revit or Inventor please useOkino's native DWF-3D importer or native Inventor importer.

Please refer to the corresponding FBX exporter.

 Houdini (geometry file) .geo Check   Check Check   Check      

+ Notes:

This import converter reads in Houdini GEO files. Houdini is a popular, high-end 3D effects and animation program. The importer handles ASCII GEO files This importer was developed over a period of several years, with help and feedback on its implementation coming from Side Effects (Toronto), the developers of Houdini.

The preferred methods to interface with Houdini in this day and age is either with the Okino FBX import and export converters, or via the Okino Collada import and export converters.

 Illustrator (Adobe; 2D curves) .ai                  

+ Notes:

This is a rather different and unique import converter in the long list of Okino importers. This converter can be used to import high quality 2D vector spline shape data from such page design programs as Adobe Illustrator, CorelDraw, Micrografix Designer, or any other 2D design package which can output Adobe Illustrator (.ai) vector files.

For example, this.ai import converter can be used to import 2D vector logos, 2D text, bezier and linear spline shapes, and have them converted into a 3D polygonal representation ideal for instant rendering in a 3D software rendering package, or for subsequent export to another file format.

Thus, ideal uses of this import converter include:

  • Import of logos and text, in spline form, from popular 2D design packages into Okino's NuGraf package for rendering in 3D, or export to another 3D file format for rendering in another software package.
  • Conversion of complex spline shape data (curves within curves, such as the letter B) into a polygonal representation which can be accepted by any major 3D software package.
  • Import of one form of 2D spline curve data (such as Cardinal curves from the OpenFlight file format) and conversion to another 2D spline format for subsequent output as 2D spline curves again (such as Bezier curves output to 3ds Max).
 Inventor2 (SGI) .iv Check Check Check Check Check        

+ Notes:

This import converter handles a significant aspect of the SGI Inventor 2.x and VRML 1.0 file formats. This version of "Inventor" is not to be confused with the native file format of the Autodesk Inventor solid modeling package; rather, this it is the native file format of the SGI (Silicon Graphics) OpenInventor toolkit. The SGI Inventor file format is quite common and popular on the SGI IRIX hardware platform, and it has been made popular on the Intel PC platform via the TGS (Template Graphics Software) port and maintenance of the OpenInventor toolkit to PC.

The VRML 1.0 file format is a direct sub-set of the SGI Inventor 2.0 file format, hence this import converter can equally handle VRML 1.0 files as an added benefit. A full list of features is provided here.

 LightWave .lwo,.lws Check Check Check Check Check   Check    

+ Notes:

This geometry import converter reads in LightWave binary object files (.lw) and ASCII scene files (.scn). It is a very complex converter, and one of the most developed in PolyTrans since 1994. This LightWave importer, and its corresponding exporter have long been two of the most important converters in PolyTrans and NuGraf for many of our dedicated game development, animation and content development users. These converters, for example, allow data to be moved from LightWave, into 3ds Max, and back again with little or no degradation in scene content (including hierarchy, object and camera animation, bones and skinning, automatic bitmap conversion and so forth).

The converter is actually composed of two distinct sub-converters: a LightWave v4-5.6 importer, and a LightWave 6.0 or newer importer. LightWave 6 was released in the 2000 by Newtek and introduced a completely revamped.lwo and.lws file format, as described below. This importer takes advantage of many of the major new features of the LightWave 6 file format. Please note: there is no need for Okino to quality this importer for each successive new version of LightWave (such as V7, V8, V9, V10, etc). LightWave is pretty well the only 3D program which has a file format that can, and has, remained stable and unchanged for close to adecade. It is an IFF chunk-based file format and hence the version of the file format has little or no bearing on the version of LightWave itself. The Okino LightWave importer is always compliant and supported up to the current version of LightWave.

 MOL Molecular Database .mol Check                

+ Notes:

This import converter reads in ASCII files based on the MOL Molecular Database format.

The MOL Import Converter was designed to allow MOL users to bring their models into the Okino NuGraf software, or to any other 3D rendering/modeling package. Once imported, the model data can be manipulated, renderings can be generated and the data can be re-exported to various other 3D formats.

 Okino Transfer File Format .bdf Check Check Check Check Check Check Check Check Check

+ Notes:

The Okino.bdf file format is the native format used by Okino's PolyTrans and NuGraf products. It is a "snap shot" of the core Okino 3D scene graph database and in essence is a super-set of the capabilities of most 3D files formats. It is the preferred and best file format to use when converting data between 3ds Max (via the PolyTrans-for-3dsMax native plug-in system) and Maya (via the PolyTrans-for-Maya native plug-in system).

 PLY .ply Check   Check Check          

+ Notes:

The PLY geometry import converter reads in binary and ASCII PLY formatted files, including mesh attributes (vertex normals, vertex colors and vertex texture coordinates) and an optional material definition. A PLY file contains the description of exactly one object. No lights, cameras, hierarchy, texture maps or animation are provided by the PLY file format.

The PLY format is NOT intended to be a general scene description language, a shading language or a catch-all modeling format. This means that it includes no transformation matrices, object instantiation, modeling hierarchies, or object sub-parts. It does not include parametric patches, quadric surfaces, constructive solid geometry operations, triangle strips, polygons with holes, or texture descriptions.

Typically, PLY files are associated with 3D scanning and object reconstruction.

Please refer to the corresponding PLY exporter.

 Pro/Engineer "Render File" .slp Check                

+ Notes:

Note, the SLP import method is quite old and obsolete relative to how ProE conversions are now done. Okino has been the main licensee and provider of native ProE conversion solutions since 1996, so you would always want to obtain the Okino Granite/Pack module to perform conversions via native ProE files, ProE neutral files or ProE STEP/IGES files.

The geometry import converter imports and processes SLP ("Render") files which are typically exported by PTC's Pro/Engineer program. Once the SLP file has been imported it can be automatically exploded into separate objects, and each object can have its vertices welded together.

In order to use this file format successfully, you will need to tag each part inside Pro/Engineer with a different color. This is because all triangles exported to the SLP file format are thrown into "one large pot", and the color of a triangle is the only salient feature which can be used to segment the model back into different parts upon re-import.

 Protein (Molecular) Database .pdb Check                

+ Notes:

This import converter reads in ASCII files based on the PDB (Protein Database) file format.

The PDB Import Converter was designed to allow PDB users to bring their models into the Okino NuGraf software, or to any other 3D rendering/modeling package. Once imported, the model data can be manipulated, renderings can be generated and the data can be re-exported to various other 3D formats.

 Rhino-3D/OpenNURBS .3dm Check Check Check Check Check Check      

+ Notes:

This import converter reads in geometric and scene data from the OpenNURBS.3dm file format. This is the main file format used by the Rhino-3D NURBS modeling package by Robert McNeel and Associatesand is also an open standard for the transfer of NURBS based surface and curve data.

The following data is imported from the OpenNURBS.3dm file format:

  1. Meshes with vertex normals, vertex uv texture coordinates and vertex colors are imported.
  2. Breps are imported as multiple distinct NURBS surfaces (with optional trim curves) parented to one new grouping node/folder.
  3. Independent NURBS curves and composite curves are imported as-is.
  4. Layers which are hidden in Rhino become hidden objects upon import (they are not ignored).
  5. Materials are created and assigned per layer or per object. Ambient, diffuse and specular colors are the basic entities imported from a Rhino material.
  6. The texture map associated with a material definition is imported as a texture reference.
  7. Ambient, spot and point light source are supported as well as their light color and intensity.
  8. Each Rhino layer is converted into an Okino grouping folder, and all related geometry is attached to one of these grouping folders.
  9. The 3D Viewport is imported as a default camera definition.
  10. Points and point clouds are ignored.
 SketchUp .skp Check Check Check   Check        

+ Notes:

Okino's professional SketchUp conversion system intelligently and robustly converts SketchUp models (included embedded texture images) into a plethora of professionally supported 3D export file formats and programs.

SketchUp is a popular 3D design product originally developed by @Last Software (http://www.sketchup.com) and now owned by Trimble, Inc. Okino recognized the growing popularity of SketchUp (well before it was purchased by Google and then Trimble) and as such we worked directly with the original SketchUp developer to create the very first set of independent, professional and fully compliant SketchUp 3D converters outside of the SketchUp program itself. Okino's SketchUp conversion system is used throughout the 3D production world by everyone from Disney to LucasFilm to Sony Productions to NASA and many people just like yourself.

Please refer to the corresponding SketchUp exporter.

 StereoLithography .stl                  

+ Notes:

This geometry import converter reads both binary and ASCII versions of StereoLithography STL files which are typically sent to 3D stereolithography (prototyping) machines. These are very primitive files, with just pure polygon data and vertices (no normals, uv texture coordinates, etc). The polygons are typically triangles. Many 3D CAD programs output STL files, so this could be considered one method to transfer data from a modeling program (however, XGL, IGES and others are becoming more common these days). All the polygons are read into a single object since there is no object information contained within a.stl file.

 Strata StudioPro v1.75 .vis Check Check     Check        

+ Notes:

This geometry import converter reads files which are in the older Strata StudioPro v1.50 and v1.75 file format. For newer versions of Strata, please use the QuickDraw-3D, VRML1 or VRML2 file formats for inter-program data transfer.

This converter is probably one of the most complete Strata StudioPro v1.75 file readers next to that of the one included with Strata StudioPro itself. You will find that most StudioPro models are of quite high quality, with good use of bezier patches (for high resolution modeling) and good use of shading + texture mapping to give realistic rendered results. Of particular note, this converter completely recreates the complex geometry hierarchy typically found in most StudioPro files; it also has the unique feature of extracting PICT texture images that are embedded within StudioPro files and converting them to stand-alone TIFF images. The converter also imports Bezier and meshed Bezier patches which are quite common in StudioPro files.

Strata.vis 1.75 format does not use uv texture coordinates. Instead, it uses the oldesr concept of uv texture projections to map the textures onto objects. This is fully supported and emulated.

 trueSpace .cob,.scn Check Check Check   Check        

+ Notes:

This geometry import converter reads in Caligari trueSpace '.cob' and '.scn' binary scene files. The following are some of the features of this converter:

  • All geometry is read in including the local axes and all material assignments.
  • Holes within polygons are also properly converted into Okino compatible meshed polygons with holes.
  • All (u,v) texture coordinates are read in and stored along with the meshed polygon data.
  • All three polygon faceting modes are properly handled: faceted, autofacet and smooth. This allows proper smoothing of the data as per the Caligari trueSpace smoothing conventions.
  • The original scene hierarchy is completely recreated, including all groupings and their related transformations.
  • The directional, point and spot light sources are properly imported as well as the light color and shadow mapping parameters.
 U3D .u3d Check Check Check Check Check   Check Check Check

+ Notes:

Okino's mirror set of U3D import and export converter modules are two of the most well developed and feature rich converter modules available for handling U3D files. U3D files are most often associated with the 3D models which are embedded in Adobe® PDF files.

This import converter loads in files of the U3D file format, including meshes, materials, hierarchy, lights, cameras, animation, skeletons (bones) and skinned meshes. There are very few U3D file import converters, and of those very few if none import the range of data and options that this Okino U3D importer does.

An overview of its salient technical features can be read here.

Okino also has a long history involved with the U3D file format. U3D has quite a tainted history in the development community. It was derived from the old Intel IFX 3D gaming toolkit of the 1990's and forced upon developers as the Macromedia 'Shockwave-3D file format' in 2000. The Shockwave-3D format was abandoned in 2002 and then it resurfaced in 2004 when Intel forced it upon Adobe as the 3D file format to use within 3D PDF files (instead of Adobe using the better X3D file format). With the IFX toolkit being so buggy, Okino spent much of 2004 through to 2007 debugging the IFX toolkit and creating the main, defacto implementation of the U3D import/export converters.

 USGS & Gtopo-30 DEM (and
SDTS with external converter)
.dem     Check   Check        

+ Notes:

This geometry import converter import converter imports, manipulates and converts digital elevation model (DEM) data as well as GTOPO30 DEM data. It has been a popular import converter since its original release in 1996. With the help of the public domain SDTS2DEM.EXE program, this importer can also read in the new SDTS DEM file format.

The USGS DEM data is provided as a service of the United States Geological Survey (USGS). Each data set describes the elevation of semi-square regions of land for various locations across the U.S.A., Alaska, Hawaii and some surrounding areas of Mexico and Canada. The most accurate DEM data sets are sampled every 30 metres (7.5 minute DEMs) while the least accurate are sampled every 3 arc seconds (for 1:250,000 scale DEMs).

 VRML1 .wrl Check Check Check Check Check        

+ Notes:

This import converter handles a significant aspect of the VRML 1.0 file format. The VRML 1.0 file format is a direct sub-set of the SGI Inventor 2.0 file format, hence this import converter can equally handle Inventor2 files as an added benefit. A full list of features is provided here.

 VRML2 .wrl Check Check Check Check Check   Check    

+ Notes:

In the realm of writing import converters this VRML 2.0 import converter was one of the more delicate and difficult to implement. VRML 2.0 is a very verbose and extensive 3D scene description language that provides much freedom of expression to write complex files. The development of this import converter has concentrated on implementing a proper and exacting import of complex VRML files, including nested PROTOS, keyframe animation and even the extraction of embedded bitmap data to stand-alone TIFF files. While there are many 3D VRML browsers, there are few stand-alone data conversion programs which properly implement the import of VRML files; we hope that making this carefully coded VRML import converter available will satisfy the many requests from our users who have long sought a good VRML import solution.

Many people consider VRML2 a "dead" file format, or a file format used primarily for WEB publishing of interactive worlds and scenes. This is far from the truth in terms of Okino customers. VRML2 is an excellent method to transfer mesh models out of many CAD modeling packages, and it is also a secondary method (after Okino's own.bdf file format) to transfer data (as well as animation) our of Discreet's 3ds Max product.

 Wavefront OBJ .obj Check   Check     Check      

+ Notes:

This geometry import converter reads in Wavefront 'OBJ' format files in their entirety, including vertex, normal and texture coordinates, as well as grouping and smoothing information. It also parses the full Wavefront NURBS file format, allowing trimmed NURBS data to be imported from such programs as Rhino-3D; when imported into PolyTrans or NuGraf, the NURBS data remains as true trimmed NURBS, allowing the data to be exported as trimmed NURBS to such supported file formats as Renderman RIB, Softimage or IGES. when outputting to a polygonal file format (LightWave, 3ds Max, etc.) the PolyTrans or NuGraf export converter will tessellate the trimmed NURBS patches to optimized indexed polygon lists prior to export.

The Wavefront OBJ file format itself does not include any capabilities for vertex color information, lights, cameras, NURBS, animation or skeleton/skinning information. Even so, it's a very standard and good format for general 3d mesh model conversion and archiving.

This import converter is a complete and accurate implementation of the Wavefront OBJ file format, including the parsing of all attributes in a Wavefront material ('.mtl') file. The converter has been under constant and refined development since 1992; it is one of the 'must have' import converters of game developers and others requiring easy transport of indexed polygon data or NURBS data amongst most of the 3D software programs currently on the market. Many companies which sell 3D models provide their datasets in the OBJ file format, so you can use this converter to read in these data files and be guaranteed nice rendered results.

An important feature of this import converter is its ability to break apart the imported polygonal data according to assigned object name, group name, smoothing number, material name or texture mapping name. Likewise, new materials definitions (inside NuGraf/PolyTrans) can be created based on one of these Wavefront OBJ file attributes.

The converter will also read material definitions from a Wavefront material file (typically which has a file extension '.mtl') if the material file is referenced within the Wavefront geometry file (typically which has a file extension '.obj') using the 'mtllib' keyword. If one or more Wavefront material files are listed on a single line then all will be read into memory for possible reference by the geometry file.

Please note: if you were not given a ".mtl" file along with the ".obj" files, then you will not get any material or texture maps after import.

 X3D .x3d Check Check Check Check Check Check Check    

+ Notes:

Okino's X3D importer (and corresponding exporter) are one of the first set of production-quality X3D and Classic VRML converters to come to market, just as Okino had provided the first industry standard set of re-purposing converters for VRML1 and VRML2 in 1996 and 1998 respectively (and which are still two of our most popular file formats today, a decade later). They were developed in full cooperation with the Web3D Consortium and the U.S. Navy.

"X3D" is the next generation standard, a superset of the VRML2 specification. It is an Open Standards XML-enabled 3D file format to enable real-time communication of 3D data across all applications and network applications. It has a rich set of features for use in engineering and scientific visualization, CAD and Architecture, Medical visualization, Training and simulation, multimedia, entertainment, educational, and more. Where VRML1 and VRML2 dominated the 3D market for the last decade, it is expected that X3D will become the successor and replacement for the next decade. More information about the X3D file format and initiative can be found at www.web3d.org.

As mentioned by Robert Lansdale, President & CEO of Okino, "I would like to impress on our Okino customer user base the importance of this new generation of X3D import/export converters. Almost every month a new 3D file format is introduced to the market, often because the developers of the file format do not believe that existing file formats are acceptable. Typically this is internally motivated by company politics or the common 'not invented here' mentality. The current 3D market is becoming glutted with an overabundance of similar 3D file formats, yet that does not need to be the case. One of the longest standing and most successful 3D file formats since 1996 has been VRML2, as it was designed to be an extensive, open and standards-based data transfer file format. VRML2, and its new X3D XML-based successor, are stable and well established file formats that will most likely outlast many of today's existing 3D formats. Okino's customers have had great success with our bi-directional VRML 1+2 conversion pipelines since the 90's and hence we decided to collaborate with the Web3D Consortium and the US Navy to extend these capabilities to include production-quality X3D and Classic VRML support. VRML2 and X3D are very verbose file formats, with many nuances, which made the implementation and testing of our second generation converters very time intensive."

The following are some of the features of this X3D import converter:

  • Object, camera, light and material animation using keyframe data.
  • Indexed face sets (meshes), indexed line sets, 3D point sets, extrusions, height field, box, cone, cylinder and sphere geometry is supported.
  • Triangle primitives: TriangleSet, IndexedTriangleSet, TriangleFanSet, IndexedTriangeFanSet, TriangleStripSet and IndexedTriangleStripSet.
  • Unique support for importing of X3D NURBS surfaces and NURBS curves.
  • Vertex normals, vertex texture coordinates, vertex colors, per-face colors and material assignments are supported for the indexed face set geometry.
  • For IndexedFaceSets and IndexedLineSets geometry, colors (in addition to X3D Materials) can be assigned on a per-vertex or per-face basis. If assigned on a per-face basis, the face colors are converted to polygon-assigned NuGraf/PolyTrans materials. Any inherited texture maps will be assigned to these per-polygon materials as well.
  • User options are available to import a specific sub-child of LOD (level of detail) nodes.
  • X3D hierarchy is recreated, including support for DEF/USE and nested PROTOs.
  • Unique support for the X3D CAD working group extensions: CADassembly, CADpart and CADface.
  • External references are supported, whereby external X3D files are inserted into the main hierarchy tree of the source file.
  • If geometry is DEFd then USEd more than once in the X3D file (ie: the geometry is instantiated multiple times), then this converter will create one object definition internally and create multiple instances of the object definition (to replicate the behaviour of VRML).
  • Each Material parameter is imported and stored, including diffuse & specular colors, ambient intensity, luminous color, shininess and transparency.
  • The directional, point and spot light sources are properly imported as well as their related parameters.
  • File-referenced bitmaps and embedded texture bitmaps are supported.
  • Bitmaps which are embedded within the X3D file are automatically extracted and converted to TIFF files on disk. The images are also displayed on the screen as they are being imported.
  • The various fields of the Transform node (scale, rotation, translation, center, scale orientation) are imported and converted to an equivalent 4x4 transformation matrix.
  • Fog and Backgrounds (color only) are imported and converted to equivalent forms.
  • Viewpoint nodes are converted to perspective cameras.
  • An optional optimization algorthm can be enabled after import is completed to remove redundant nodes from the scene graph and hierarchy.
  • Global and per-node metadata. WorldInfo imported as user-data.
 XGL (good for CAD transfers) .xgl &.zgl Check Check Check   Check        

+ Notes:

This import converter reads in ASCII XGL formatted files as well as their ZGL compressed equivalents. Triangular mesh data (with vertex normals and vertex uv texture coordinates), basic material properties, embedded texture images and object hierarchy are imported from the XML-style XGL file.

XGL is an ideal file format to export data from various supported 3D programs (see here, primarily CAD packages) to an XGL viewing program, be it on a local machine or across the Internet. XGL is also an ideal file format to move data from these CAD packages into Okino's NuGraf software for viewing, visual editing and photo-realistic rendering.


Legend: Mat = basic or advanced materials, Hier = full scene hierarchy, u/v = uv mesh texture coordinates, VC = mesh vertex colors, L&C = lights and cameras, NURBS = trimmed NURBS surfaces, Anim = keyframe animation, Skel = skeletons defined by bones or joints, Skin = mesh skinning (deformation by skeletons).

 Optional Add-On Importers in the 'CAD/Pack' License

Okino has been actively involved with developing our own CAD converters starting in 1988 and such converters form the basis of our common daily customer sale. We don't "write" converters but rather "nurture" them over years and years to handle all varieties of data.

The CAD/Pack is primarily purchased by these types of customers:

  • Users who wish to import native SolidWorks or Solid Edge files.
  • Users who wish to import from Autodesk CAD programs such Autodesk Inventor, AutoCAD, Navisworks or Revit.
  • For all other CAD import requirements please refer to the Granite/Pack module.

SolidWorks 'Backhoe' model imported into 3ds Max via PolyTrans-for-3dsMax.
Autodesk Inventor engine model imported directly into Okino's NuGraf.
Click on either image to see full scale rendition.
 3D CAD Importer Extensions Import From
Disk Files?
Import From
Live Application?
 Autodesk Inventor .iam (assemblies),
.ipt (parts)
Check Check

+ Notes:

The Autodesk Inventor import converter module allows geometry, hierarchy and materials (assembly data) to be imported from native disk-based Autodesk Inventor files or from a running copy of the Autodesk Inventor 3D solid modeling application using the Autodesk Inventor automation API. No intermediate files are used in the translation.

Also refer to Okino's DWF-3D importer as an equally good and supported method to convert data from Inventor.

If you do not have a copy of Autodesk Inventor installed on your computer then you will need to install the Inventor "Apprentice Server" COM component module. This module allows Okino's Inventor importer to import data from.iam assembly files and/or.ipt part files without need for a full resident copy of Autodesk Inventor. This "Apprentice Server" is distributed by Autodesk in an installer called "Design Tracking". References to this page can be found on the Okino demo downloads WEB page.

Features of the Autodesk Inventor importer:

  • Import from a live running copy of Autodesk Inventor, or from native Autodesk Inventor.iam and.ipt files on disk (no copy of Autodesk Inventor required for this latter feature).
  • Imports and retains: assembly hierarchy information and assembly names, as well as BREP structure of the source model (bodies and faces). Can query accurate vertex normals, uv texture coordinates and UV tangent vectors from Autodesk Inventor directly.
  • The quality of the model (the number of polygons) can be controlled when importing from Autodesk Inventor or from disk-based files.
  • Okino's "CAD Scene and Hierarchy Optimization System" has been integrated right into the Autodesk Inventor importer. This is most important when importing large CAD models into 3ds Max, Maya or Lightwave. These animation packages tend to have performance problems then the source CAD model is large, and/or has a large number of individual parts (which is often the case with the BREP model topology of data provided by Autodesk Inventor).
  • The native PolyTrans plug-in systems for 3ds Max (PolyTrans-for-3dsMax) and Maya (PolyTrans-for-Maya) have been refined since 1998 specifically for importing large CAD assembly models from Autodesk Inventor. This has come about partly from our good software users, and also from the main Okino CAD programmers who have been specializing in CAD to non-CAD conversion software since 1988.
  • Complete control over material parameter modification on an automatic basis. Many CAD systems like Autodesk Inventor have basic material parameters (like color, ambient + diffuse shading coefficients, opacity, etc) but when they are transferred over to a rendering and animation system they often look "too bright" or "highly ambient". This can be expected and is quite normal. The material tweak parameters easily allow such saturated shading values to be automatically compensated.
 Autodesk DWF-3D (for AutoCAD, Navisworks, Revit & Inventor) .dwf,.hsf Check  

+ Notes:

This DWF-3D importer is considered by Okino to be our most important CAD importer for handling data from AutoCAD, Navisworks, Revit and optionally Autodesk Inventor. Okino wrote the first and primary implementation of DWF-3D over a long period of 6 years. Its development focus has been to import the absolute most humongous of DWF-3D files and then have the data highly optimized for downstream programs which just can't handle such files. Common examples are very large oil & gas rigs, entire ships and architectural models. The converter will also import from HOOPS.hsf files.

This is not "just another 3D importer" but rather something we consider a "god send" to us and our customers. Whereas DXF and DWG are some of the worst file formats for general data translation, DWF-3D is one of the very best 3D file formats available. DWF-3D is actually an empty 'container file format', as is Adobe PDF, which uses the extensive and concise HOOPS 3D HSF format to capture and convey the 3D data.

It is highly recommended that you use DWF-3D file format to export out of AutoCAD and not the DXF or DWG file formats. For Navisworks and Revit, always use DWF-3D and never FBX format. For Autodesk Inventor, either use Okino's native Inventor importer or DWF-3D.

Please also refer to the corresponding DWF-3D export converter.

 Autodesk DXF & DWG (all versions) .dxf,.dwg Check  

+ Notes:

The DWG import converter is an intelligent and complex converter which will read in DWG/DXF files containing 2d, 2-1/2d or 3d entities and transform them into optimized, grouped meshes of 3d polygons.

Please note that the base-level NuGraf and PolyTrans programs only import the DXF R12 file format whereas the CAD/Pack license adds in support up to the current version of DXF and DWG.

Highlights of the converter are as follows:

  • Conformance to AutoCAD versions going back as far as the oldest 2.5 format.
  • Reads both ASCII and binary versions of the DXF/DWG format.
  • The 'scan mode' option allows the DXF/DWG file to be pre-scanned for color numbers, layer names and block names.
  • Retains blocks and instances within the imported database (no object replication).
  • Creates cameras from the VIEW entries found in the DXF/DWG file. The cameras are compliant with the unpublished AutoCAD 'VIEW' algorithm for perspectivecameras.
  • Reads in the most popular and important DXF/DWG entity and converts them into optimized 3d polygon meshes by a variety of means.
  • Allows 2d entities with no width or thickness to be intelligently converted into 3d polygons of very narrow width. This allows, for example, 2d drafting diagrams to be imported and rendered in 3-dimensions. It can also be used, for example, to import GIS data that consists of DEM terrain and simple 3d polylines (very powerful!). This feature is quite useful since 3D AutoCAD diagrams often use 2d lines and 2d arcs to add fine detail to a scene; without this feature such detail would be non-existent within the 3d imported scene.
  • All adjoining polylines which have been assigned "width" are properly mitred. The only other 3d DXF/DWG converter that is known to have this capability is that provided with Autodesk's 3D Studio. Mitring adjusts the angle of abutting polygons so that they fit together snuggly (as with the corners of a picture frame). The mitring code handles every possible case, including 2d mitring (widened polylines) and 3d mitring (widened polylines which are subsequently extruded upwards).
  • The converter is extemely memory efficient.
  • If ACIS solid entities are stored in the DWG file then they will be decrypted and turned into polygon meshes prior to import.
 Okino IGES (Trimmed Surfaces) .iges,.igs Check  

+ Notes:

This complex geometry import converter reads in "Trimmed Surface" IGES files including the most used NURBS entities, their related trim curve information, geometry hierarchy connectivity and polygonal data. It was the core back-bone of Okino CAD conversions during the 90's and early 2000's era. However, all IGES conversions are now preferred to be handled by the IGES-solids importer in the Okino Granite/Pack module.

Features of this Okino IGES "Trimmmed Surface" import converter:

  • All of the major 3d geometry entities, such as tabulated surface, surface of revolution, parametric spline surface and all NURB entities are imported and converted to clean and legal trimmed NURB patches.
  • The reader fully recreates the geometrical hierarchy of an IGES file via entities 308 (subfigure definitive) and 408 (subfigure instance) in an efficient manner using the instance/object capabilities of the NuGraf/PolyTrans internal database manager. This allows the IGES reader to define an object once (such as a bolt) then have it instanced many times; thus, there only has to be one copy of the geometry in memory even though there are many virtual copies of it in the scene.
  • The IGES specification does not provide an efficient method to store meshed polygonal data. Rather, each single polygon is typically written to an IGES file within its own entity (#106, copious data). When reading in an IGES file, this converter will flag all of these polygons which belong to a single subfigure definition and accumulate them into an efficient 'Indexed Polygon' mesh primitive rather than create a new object for each polygon read in.
  • All polygons which do not belong to a subfigure definition will be accumulated and stored in a single indexed polygon mesh with an instance name of 'lone polygons'.
  • If a circular arc is not subordinate to another entity (ie: it is not used as a trim curve on a NURB surface) then it is turned into a planar NURB patch surface with a circular boundary. The same holds true for composite curves and conic arcs which are closed.
  • External file references are handled, in a recursive manner. This allows sets of IGES files, hierarchically linked via one main "root" IGES file, to be imported and its hierarchy recreated. This is most often used for files coming from Pro/Engineer.
 Solid Edge .asm (assemblies),
.prt (parts)
Check Check

+ Notes:

The Solid Edge import converter module allows geometry, hierarchy and materials (assembly data) to be imported from native disk-based Solid Edge files or from a running copy of the Solid Edge 3D solid modeling application using the Solid Edge automation API. No intermediate files are used in the translation.

Features of the Solid Edge import converter:

  • Import from a live running copy of Solid Edge, or from native Solid Edge.asm and.prt files on disk (no copy of Solid Edge required for this latter feature).
  • Imports and retains: assembly hierarchy information and assembly names, as well as BREP structure of the source model (bodies and faces). Can query accurate vertex normals, uv texture coordinates and UV tangent vectors from Solid Edge directly.
  • The quality of the model (the number of polygons) can be controlled when importing from Solid Edge (but not when importing from files directly on disk).
  • If one part is instantiated N times in the Solid Edge assembly tree then this importer will recognize such a situation and use Okino's core database master/instance capability to import the part just once and instantiate it N times.
  • The native PolyTrans plug-in systems for 3ds Max (PolyTrans-for-3dsMax) and Maya (PolyTrans-for-Maya) have been refined since 1998 specifically for importing large CAD assembly models from Solid Edge. This has come about partly from our good software users, and also from the main Okino CAD programmers who have been specializing in CAD to non-CAD conversion software since 1988.
  • A good number of important options that can be (optionally) set prior to import, to control most situations that could be encountered with Solid Edge data import. Many options have come about from end-user requirements or situations.
  • Complete control over material parameter modification on an automatic basis. Many CAD systems like Solid Edge have basic material parameters (like color, ambient + diffuse shading coefficients, opacity, etc) but when they are transferred over to a rendering and animation system they often look "too bright" or "highly ambient". This can be expected and is quite normal. The material tweak parameters easily allow such saturated shading values to be automatically compensated.
  • If you are importing the Solid Edge data into Okino's PolyTrans or NuGraf software then it is possible to "refresh" or "update" the scene data directly from Solid Edge without having to re-import the whole scene again.
 SolidWorks .sldasm (assemblies),
.sldprt (parts)
Check Check

+ Notes:

The SolidWorks import converter module allows geometry, hierarchy and materials (assembly data) to be imported from native disk-based SolidWorks files or from a running copy of the SolidWorks 3D solid modeling application using the SolidWorks automation API. No intermediate files are used in the translation.

Features of the SolidWorks import converter:

  • One of the most well developed, customer-requested and supported CAD importers written by Okino.
  • Import from a live running copy of SolidWorks, or from native SolidWorks.sldasm and.sldprt files on disk (no copy of SolidWorks required for this latter feature).
  • Imports and retains: assembly hierarchy information and assembly names, as well as BREP structure of the source model (bodies and faces). Can query accurate vertex normals, uv texture coordinates and UV tangent vectors from SolidWorks directly.
  • The quality of the model (the number of polygons) can be controlled when importing from SolidWorks (but not when importing from files directly on disk).
  • If one part is instantiated N times in the SolidWorks assembly tree then this importer will recognize such a situation and use Okino's core database master/instance capability to import the part just once and instantiate it N times. This feature can be disabled so that assembly-level part modifications within SolidWorks (and using the automation import mode) can be imported, such as per-instance colors and feature changes (such as per-part hole cuts).
  • Okino's "CAD Scene and Hierarchy Optimization System" has been integrated right into the SolidWorks importer. This is most important when importing large CAD models into 3ds Max, Maya or Lightwave. These animation packages tend to have performance problems then the source CAD model is large, and/or has a large number of individual parts (which is often the case with the BREP model topology of data provided by SolidWorks).
  • The native PolyTrans plug-in systems for 3ds Max (PolyTrans-for-3dsMax) and Maya (PolyTrans-for-Maya) have been refined since 1998 specifically for importing large CAD assembly models from SolidWorks. This has come about partly from our good software users, and also from the main Okino CAD programmers who have been specializing in CAD to non-CAD conversion software since 1988.
  • A good number of important options that can be (optionally) set prior to import, to control most situations that could be encountered with SolidWorks data import. Many options have come about from end-user requirements or situations.
  • Complete control over material parameter modification on an automatic basis. Many CAD systems like SolidWorks have basic material parameters (like color, ambient + diffuse shading coefficients, opacity, etc) but when they are transferred over to a rendering and animation system they often look "too bright" or "highly ambient". This can be expected and is quite normal. The material tweak parameters easily allow such saturated shading values to be automatically compensated.
  • If you are importing the SolidWorks data into Okino's PolyTrans or NuGraf software then it is possible to "refresh" or "update" the scene data directly from SolidWorks without having to re-import the whole scene again.
 Optional Add-On Importers in the 'Granite/Pack' License

Okino's Granite/Pack is the core back-bone of Okino's BREP solids-based CAD conversion pipelines. Click here for an overview of the CAD file formats supported, a feature list and the screen snapshots of the importer wizard panels. A succinct selection of imagery created by users of the Okino Granite/Pack can be viewed online here.


    Click on image to see full scale rendition

The following table of Granite/Pack supported file formats has been sorted by the general popularity of each file format to our typical customers:

 3D CAD Importer Extensions File Format Version
 Creo Elements (Pro/Engineer) .asm,.prt,.neu Current PTC version

+ Notes:

This is the main and defacto method to import from native "Pro/Engineer (Creo) Parts & Assembly" files. Okino licenses the ProE/Creo software from PTC Corp. and embeds it directly into Okino software for use in importing complex native ProE/Creo datasets. This is one of the most demanded, used and refined of all Okino CAD conversion pipelines.

You would either want to import the top-level ProE/Creo.asm assembly file, or ask your client for "ProE/Creo Neutral files" and import the top-level.neu assembly file. Contrary to what some people initially try to do, please do not import every.prt file in a directory; rather, what you do with ProE/Creo datasets is only import the single, top-level assembly file. The name of that file must be provided to you from the client provider.

 STEP .stp,.step,.ste AP203 and AP214

+ Notes:

STEP AP203 allows users to exchange geometry, topology and configuration data of a part or the whole product assembly. The user can exchange wireframe models, surface models and boundary representation of exact or faceted three-dimensional solids. STEP AP214 is a super set of AP-203 to define core data for automotive mechanical design processes.

STEP (which is short for STandard for the Exchange of Product model data and is also known as ISO 10303) is a standards-enabled technology for manufacturing developed by the International Organization for Standardization (ISO) to improve the exchange of data to meet a variety of industrial needs. This data includes design solids, product structure, product management and kinematics.

STEP AP203 and AP214 (which are supported in the Granite STEP importer) allow organizations to exchange 3-D solid, surface and wireframe geometry between heterogeneous CAD systems. These two APs can exchange a complete assembly of parts together with configuration management data and more, instead of just a single part.

STEP AP203 allows users to exchange geometry, topology and configuration data of a part or the whole product assembly. The user can exchange wireframe models, surface models and boundary representation of exact or faceted three-dimensional solids.

STEP AP214 is a super set of AP-203 to define core data for automotive mechanical design processes.

 PTC IGES (all variations) .igs or.iges Various

+ Notes:

IGES, or the Initial Graphics Exchange Specifications, is by far one of the most openly accepted and implemented neutral file formats used to transfer CAD data between dissimilar modeling programs and applications. The file format specification is over 300 pages and over 1" thick; however, most IGES files only use a subset of the full specification.

We consider there to be 3 main types of IGES files:

  • "Trimmed" surfaces. These IGES files use the 144/142/128 entities to define 3D objects defined by uv-space trimmed NURBS surfaces. Okino's IGES importer has been tailored specifically to this very common variation of the IGES spec.
  • "Bounded" surfaces. These IGES files use the 143/141/128 entities to define 3D entities by bounded regions of world-space curves on surfaces. This form of IGES was more common prior to the 144/142/128 entities being added to the IGES spec, and in general this variation is less common today.
  • "BREP" or "solids" surfaces. These IGES files use the 186 and 500 range of entities to define 3D entities as BREPs (body, shell, face, loop, edge and vertices). This is the standard for transferring "solids" data from one solids modeler to another, and the core of the Granite importers.

This importer handles all variations of IGES files in a very robust and time tested manner.

 Parasolid .xmt,.xmt_txt,.xmt_bin,
.xmt_neu,.x_t,.x_b,.x_n
Various

+ Notes:

The Parsolid.x_t importer is written by PTC and does not use the Siemens Parasolid modeling toolkit to import and handle the.x_t file.

Parasolid is a common, popular and well established 3D solids modeling toolkit. It forms the basis, or is used, with many 3D modelers, including Unigraphics/NX, SolidWorks and Solid Edge. The native file format is the Parasolid ".x_t" format.

Through decades of experience, we at Okino have found that the 'STEP AP214' file format is the most stable and mathematically sound method to source CAD data from UG NX. We would recommend using STEP over Parasolid format. STEP AP214 is also the preferred method to source files from Solid Edge, if and when you do not wish to import native Solid Edge files.

If you are importing from SolidWorks, and don't have native SolidWorks files available to you, then ask your client or vendor for 'IGES solids' files.

 Okino IGES (surfaced data) .igs,.iges 5.3

+ Notes:

The Okino IGES import importer has been bundled together with the Granite/Pack license as a complement to the PTC IGES importer and other CAD importers. In general you will always want to import your files with the PTC IGES importer, although the Okino IGES importer is written for, and very fast to process, "Trimmed Surface" IGES file variations.

 SAT (ACIS) .sat Various

+ Notes:

The ACIS.sat importer is written by PTC and does not use the native Spatial ACIS toolkit to import and handle the.sat file. Please refer to the Okino/Spatial SAT/SAB importer which is the defacto method to import ACIS models for all past and current versions of the file format.

"SAT" is the native ASCII based file format of the industry standard "ACIS" 3D solids modeling toolkit developed by Spatial Corp. Programs which are based upon the ACIS 3D solids modeling toolkit will naturally import and export this file format.

It is extremely rare when a customer will use the SAT file format in this day and age.

 Granite "g-plugs" .g Various

+ Notes:

This is an expansion mechanism that allows 3D data to be imported from other vendors by way of their own dynamic "g-plug" plug-in modules.

 Pro/DESKTOP .des Current PTC version

+ Notes:

This is the native file format to import solids data from the PTC Pro/DESKTOP modeler. A free version of this solids modeler (Pro/DESKTOP Express) can be downloaded from the PTC WEB site.

 VDA-FS .vda,.vdafs v2 or older

+ Notes:

VDA-FS is similar in concept to IGES files, but of a much more limited nature. It conveys NURBS 3D surface geometry data only, and no information about colors, layers or text annotations. It was meant to move 3D surface data from one CAD system to another, with the fewest number of problems and with the least amount of work. You should consider using all of the other Granite converters first (or even VRML, XGL, etc) before using VDA to transfer CAD data.

VDA-FS is a German standard for transferring CAD geometric data amongst various CAD systems. It was developed by the German Automobile Manufacturers Association, the Verband der Automobilindustrie E.V (VDA, "http://www.vda.de"), as the German national standard, DIN 66301.


 Optional Add-On Importers in the 'DCC/Pack' License

The DCC/Pack contains our most developed and heavily used converters dealing with the common "Digital Content Creation" animation and modeling programs, as well as VizSim (OpenFlight). These converters are grouped together in the DCC/Pack as they are developed in unison so that data can flow fairly evenly between any two DCC-based animation or VizSim packages. The DCC/Pack is an electronic add-on license to the baseline PolyTrans and NuGraf products, available when you purchase the baseline product or any time in the future. Anyone who normally uses Maya, OpenFlight or Softimage in their conversion pipelines will typically purchase the standard DCC/Pack license.

See also the corresponding table of DCC/Pack export converters.

If you wish to convert 3D scenes and animation between 3ds max and Maya, which is one of our most requested conversion pipelines, then you would purchase either the baseline PolyTrans or NuGraf program, and the DCC/Pack add-on license.



FBX 'Samurai' model (courtesy of Autodesk) imported,
animated & rendered in Okino's NuGraf. Click on any
image to view a Windows Media 640x480 animation.
 3D Import File Format Extension Mat Hier u/v VC L&C NURBS Anim Skel Skin
 PolyTrans-for-Maya (via
native plug-in system)
.ma,.mb Check Check Check Check Check Check Check Check Check

+ Notes:

PolyTrans-for-Maya runs inside Maya as a native plug-in system (and requires a resident copy of Maya). This allows a Maya user to easily access all of the stand-alone Okino converter modules. PolyTrans-for-Maya would be considered one of Okino's "main software products" that a large number of Okino customers would own.

To convert data to/from 3ds Max use the Okino ".bdf" scene transfer file format and the native PolyTrans-for-3dsMax plug-in system on the 3ds Max side.

To convert data to/from CINEMA 4D use the.c4d import/export converters from the Maya side.

To convert data to/from Softimage use the.dotXSI file format from the Maya side.

To convert data to/from Lightwave use the Lightwave import/export converters from the Maya side.

 OpenFlight .flt Check Check Check Check Check        

+ Notes:

This geometry import converter reads in the Presagis OpenFlight '.flt' binary format files. The converter extracts and converts the OpenFlight data to equivalent Okino internal data representations. This has been the 'defacto implementation' of OpenFlight and one of our most popular DCC-based converters sold daily since its original release.

NOTES: OpenFlight format does not have keyframe animation capabilities, nor NURBS or skeletons.

 Softimage 'dotXSI' format
(does not require copy of Softimage)
.xsi Check Check Check Check Check Check Check ¥ Check

+ Notes:

This geometry import converter reads in Softimage.xsi files. No copy of the Autodesk Softimage animation program is required. Meshes (with vertex normals, vertex colors and vertex uv texture coordinates), hierarchy, cameras, lights, materials, texture maps, object animation, envelopes (mesh skinning) and 3D NURBS curves are supported as a baseline. Dialog box controls are provided to allow automatic tweaking of shading parameters. The multiple meshes per 'model' can be automatically compressed back up into single meshes, or kept separate.

¥ = The dotXSI file format really doesn't have a sense of a "skeleton" like in other file formats. In most other formats, except for DirectX, a grouping node can be tagged as a bone or joint; when imported into its respective animation program, such nodes are visualized as bones. In the dotXSI file format you would normally create an IK chain in order to have bones visualized in the XSI user interface. However, it is not necessary to create an IK chain in order to define a "skeleton" for mesh skinning (enveloping in XSI lingo). The dotXSI file format allows any object or any grouping node to be used as a "mesh skinning bone" (deformation object) so to speak, and this is exactly how the Okino converter handles bones & mesh skinning for the dotXSI file format.


 Optional JT-Open Add-On CAD Importer

The 'JT' CAD import converter module allows geometry, hierarchy and materials (assembly data) to be imported from native.jt disk-based MCAD files (otherwise called "DirectModel" files). The JT importer module also allows PMI graphical data to be imported and then re-exported to such compatible Okino export file formats as U3D. The JT importer is built upon the official "JT Open" Toolkit which has been licensed from UGS Corp. The use of the official "JT Open" toolkit ensures consistency of JT files across the enterprise and throughout the PLM market.

See also the optional Okino JT exporter module.

 Optional Spatial SAT, CATIA v4 and CATIA v5 Add-On CAD Importers

Three optional, top-notch and best-of-class CAD importer modules are available for Okino software which implement ACIS SAT/SAB, CATIA v4 and CATIA v5 import using the defacto industry standard software components from Spatial Corp and its parent company Dassault Systèmes (the makers of CATIA). These modules provide precise, crack-free imports from BREP solids models.

Please refer to the product ordering page for additional information about the licensing and maintenance terms for the Spatial-based CAD importer modules.

 3D CAD Importer Extensions File Format Version
 Spatial ACIS SAT .sat,.sab Up to current version

+ Notes:

"SAT" is the native ASCII based file format of the industry standard "ACIS" 3D solids modeling toolkit developed by Spatial Corp. Programs which are based upon the ACIS 3D solids modeling toolkit will naturally import and export this file format.

Okino has licensed the full ACIS modeling toolkit in order to provide defacto and perfect support for the SAT (text) and SAB (binary) file formats. The toolkit is used to read in its own native file format (SAT/SAB) and provide conversion of the BREP solids into a crack-free model for import into Okino software.

 CATIA v4 Models .model,.dlv,.exp,.session v4.1.9 up to v4.2.4 (or newer)

+ Notes:

This geometry import converter imports and processes BREP solids-based CAD geometry files stored in the CATIA v4 native file formats. Okino has been a trained Spatial Corp. developer since 1997, resulting in a top notch, refined and professional implementation of the Okino-CATIA importer.

The CATIA stand-alone program (made by Dassault Systèmes and distributed by IBM) is an integrated suite of Computer Aided Design (CAD), Computer Aided Engineering (CAE), and Computer Aided Manufacturing (CAM) applications for digital product definition and simulation. It allows manufacturers to simulate all the industrial design processes, from the pre-project phase, through detailed design, analysis, simulation, assembly and maintenance. CATIA is primarily used by the automotive and aerospace industries for automobile and aircraft product and tooling design (it is well known for being used by Boeing to design their massive airplanes, or NASA to help design the Space Shuttle). There are roughly 20,000 companies worldwide using CATIA with roughly 30,000 seats sold per year.

 CATIA v5 Parts & Assemblies .CATPart,.CATProduct R2 and newer

+ Notes:

This geometry import converter imports and processes BREP solids-based CAD geometry files stored in the CATIA v5 native.catpart part and.catproduct assembly file formats. The importer is based on the actual CATIA v5 runtime DLLs and components from Dassault Système (the developers and owners of the CATIA v5 modeling software) and hence provides the absolute best conversion of native CATIA v5 part and assembly files - no reverse engineered libraries are used, as is often the case with other CATIA v5 importers.

The CATIA stand-alone program (made by Dassault Systèmes and distributed by IBM) is an integrated suite of Computer Aided Design (CAD), Computer Aided Engineering (CAE), and Computer Aided Manufacturing (CAM) applications for digital product definition and simulation. It allows manufacturers to simulate all the industrial design processes, from the pre-project phase, through detailed design, analysis, simulation, assembly and maintenance. CATIA is primarily used by the automotive and aerospace industries for automobile and aircraft product and tooling design (it is well known for being used by Boeing to design their massive airplanes, or NASA to help design the Space Shuttle). There are roughly 20,000 companies worldwide using CATIA with roughly 30,000 seats sold per year.


 3D Import File Converters From Third Party Vendors

Okino has had one of the most extensively developed plug-in development systems and APIs since its original creation in 1988. Okino's plug-in development program allows third party developers and vendors to create new importers and exporters, as well as system-level plug-ins to create such add-in components as renderers, modelers and search engines.

Click on the following logo to jump to the online list of third party commercial plug-in modules available for Okino software.


  Contact Okino | Legal & Privacy | Products | Download Demos | RSS | Purchase  


840
Sitemap