A fully functional demo-limited version of the stand-alone PolyTrans and NuGraf software packages are
available for immediate download for Microsoft Windows. In addition, a secondary and optional download of the "Okino Plug-Ins Super Installer" will
allow you to install native Okino import/export converters directly into 3ds Max, Maya and Autodesk Softimage. The PolyTrans-for-CINEMA-4D conversion
modules are included in the stand-alone Okino software.
Please do not use any of the free converters that come with 3ds Max, Maya, CINEMA-4D, LightWave or
Softimage as part of your end to end conversion pipeline but rather always use Okino's dedicated conversion methods.
Also, as the #1 concept to follow to achieve perfect conversions, always source your CAD file data using the short "rule set" as outlined
here which is applicable to all of our users.
!! If you are using 3ds Max or Maya then it is imperative to install the Okino
PolyTrans-for-Maya sub-products, as noted on the next demo information
page. These have consumed most of our last 2.5 decades of DCC/Animation development work, and hence
it is most important to utilize these native conversion systems instead of using the early 90's .3ds and OBJ
Once you have entered the user information on this WEB page please press the "Register and Begin Download" button at the bottom of this page to proceed to the download page.
How to Properly Evaluate Okino Conversion Software
Okino software is not something which you would normally download just to "kick the tires" and
see if it can load in the CAD/DCC file which you may have been blindly given by a third party vendor.
Okino software has been written with hundreds of man years of development and will achieve mathematically
correct conversions for all source to destination paths, but it must be done with the correct
choice of the source file format + converter combination (but notably the proper sourcing of your CAD data).
Many of our new customers come to us with well known
misconceptions about how they should convert their data files and (in many cases) incorrectly sourced
CAD files. Okino is an engineering R&D company for which we work closely and at a grass root's level with
our user base, whereby education and awareness is a critical aspect of achieving perfect data translations. Hence,
we will always exchange at least 2 or 3 short emails with every potential new user to ensure that they are
approaching their conversion process in the correct manner, notably to explain the proper way to
source their CAD files and also what conversion method should be used.
The following is the manner in which we interact with all of our new or long-term Okino customers,
or anyone evaluating our software for the first time:
As the most important step to take in our educational process, please send a short email to our
CTO Robert Lansdale (firstname.lastname@example.org) with the following information:
1a) - The name of the source 3D program and file format from which your data is coming from. Most people will say "IGES or STEP"
but that is not entirely correct. It is the name of the source MCAD program which would be most important (SolidWorks, ProE/Creo, etc.)
as that ideally defines which source file format should be used. If you are unsure then Robert Lansdale
can explain how to discern that information very quickly from your data.
1b) - The destination 3D program and/or file format into which you wish to convert the data.
1c) - Many of our new customers have a "problem" they wish to overcome even if they are not aware of it. If
there is some underlying issue which you are having then please state that in your email.
2 - There are some people who are not aware of how to properly evaluate software for CAD imports.
It is not the export process (into your destination program) which is important whatsoever, since our
Okino software has complete control over that process. Rather, the most important aspect of the
conversion process is the import phase since that is where the sheer complexity of the conversion
occurs. Thus, as we've explained to new users for 25 years, what you would want to do is to import your
source data into our stand-alone PolyTrans or NuGraf program, then press the "Render" button (on the left-most vertical toolbar) to see
the entire model with no demo limitations. Whatever you see in the scanline/ray-traced rendering is
always what you will get when exported to any of the 3D file formats supported by Okino software.
The export process, or conversion into 3ds Max, Maya, CINEMA-4D, LightWave, Softimage, etc. never has
to be 'tested' since the export process is under Okino's complete control and as such will always
produce a proper file. Even with this stated paragraph, people will still write to us weekly asking "Why are there holes
in the model once loaded into my destination program?" -- if there were no demo limitation holes then there would
be no reason to pay for the software since it would then be fully functonal.
3 - Okino software is system-architected and direct-developer supported by Robert Lansdale (our CTO), who
works "one on one" with each and every new or existing customer. We do not run a face-less company -- customer
communication is front and central to everything we do each day. As such, if you would like
a non-demo conversion done by us, or chat with us about the best choice of import/export converters and
options to use, then please email us now.
You should get a response back within a few minutes, or at most 4-6 hours, during our typical 16-18 hour work day, 7 days a week.
The demo is limited in the following manner:
Exported 3D files, or files viewed in the stand-alone Okino PolyTrans/NuGraf software, will have every fifth
polygon removed. As noted in the explanation above, please press the "Render" button on the vertical toolbar within the
stand-alone NuGraf or PolyTrans software to see the model with no holes poked in them. Data imported
into 3ds Max and Maya, via the native plug-in systems, will have these holes poked in the datasets as well,
otherwise the software would be fully functional and there would be no need to pay for the software.
Okino native .bdf scenes cannot be saved to disk in the stand-alone software,
A small watermark bitmap will appear in the lower-left corner of all rendered images,
Texture files used for rendering or re-export will have black lines added to them,
Only the first 25% of object animation keyframes will be converted,
No camera animation data will be converted,
All trimmed NURBS patches will be converted to polygons meshes prior to export, or when NURBS are imported into Maya via PolyTrans-for-Maya (as a demo limitation only).
Skeleton & mesh skinning will be fully functional, and bidirectional, between 3ds Max, Maya, CINEMA-4D, LightWave, Autodesk Softimage, DirectX, FBX, Collada and U3D.
However, skinned meshes exported to DirectX in demo mode do not load into many DirectX viewers due to the '5th polygon removal' demo
mode restriction (the DirectX engine requires a continuous mesh, not one with holes). Email email@example.com
if you would like a DirectX test conversion done without any demo mode restrictions.
Enter User Information & Proceed to Download
If you have any trouble downloading the demos, or this form does not work with
your browser, then please mail firstname.lastname@example.org.