// Tokens:
//	'CHK' = Place a checkmark
//	'NOCHK' = Don't place any checkmark
// NOTE: Don't uses spaces between the "|" and the NOTES/CHK/etc tokens
//

// ----------------------------->>>> Header Line
//
3D Import Format |					Ext |	Mat |	Hier |	u/v |	VC |	L&C |	Anim | 	Skel | 	Skin

<a href="/conv/pt4maya.htm" class=fft>PolyTrans for Maya</a> (via<br> native plug-in system) |	.ma, .mb |	CHK |	CHK |	CHK |	CHK |	CHK |	CHK |	CHK |	CHK
NOTES-START
<a href="/conv/pt4maya.htm">PolyTrans-for-Maya</a> 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.

<p> To convert data to/from 3ds Max use the Okino ".bdf" scene transfer file format and the native <a href="/conv/pt4max.htm">PolyTrans-for-3dsMax</a> plug-in system on the 3ds Max side.

<p> To convert data to/from CINEMA 4D use the .c4d <a href="/conv/imp_c4d.htm">import</a>/<a href="/conv/exp_c4d.htm">export</a> converters from the Maya side.

<p> To convert data to/from Lightwave use the Lightwave <a href="/conv/imp_lw.htm">import</a>/<a href="/conv/exp_lw.htm">export</a> converters from the Maya side.
NOTES-END

<a href="/conv/imp_flt.htm" class=fft>OpenFlight</a> |	.flt |	CHK |	CHK |	CHK |	CHK |	CHK |	NOCHK |	NOCHK |	NOCHK
NOTES-START
<p>OpenFlight is an industry standard realtime 3D scene description format developed, owned and maintained by Presagis, Inc. OpenFlight is the most widely used file format for visual simulation databases and is supported by dozens of vendors of realtime 3D tools. Military visual simulation includes battle simulation, fighter jet flight simulation, tank simulation. Visual simulation also includes geospecific terrain for accurate realtime fly through of regions of the planet.

<p> In visual simulation, OpenFlight is the defacto standard format. OpenFlight is also prevalent in the PC animation and modeling communities for optimizing and tagging 3D data for realtime playback. As application examples, in the visual simulation industry OpenFlight is the format for entire worlds. In the entertainment industry it is widely used for level building in realtime games and in the AES or urban simulation industries it is used to organize and optimize scenes for realtime walkthroughs.

<p> This <a href="/conv/imp_flt.htm">geometry import converter</a> 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.

<p>NOTES: OpenFlight format does not have keyframe animation capabilities, nor NURBS or skeletons.
NOTES-END

<a href="/conv/imp_xsi.htm" class=fft>Softimage</a> 'dotXSI' format<br>(does not require copy of Softimage) | .xsi |	CHK |	CHK |	CHK |	CHK |	CHK |	CHK |	NOTE |	CHK
NOTES-START
<p>Softimage|3D and Softimage|XSI were two well known 3D animation systems written by Softimage Inc. of Montreal Canada. Autodesk eventually came to buy the company in 2008 and then kill off the software in 2014.

<p> This <a href="/conv/imp_xsi.htm">geometry import converter</a> 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.

<p>¥ = 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.
NOTES-END