The GTO format's primary usage is storage of static geometric data. The types of data you might find in a GTO file are things like polygonal meshes, various types of subdivision surfaces, NURBS or UBS surfaces, coordinate systems, hierarchies of objects, material bindings, and even images. It is used by film, video, and game production companies to streamline the modeling, animation, rendering, and 3-D paint processes. The distribution includes source code for a RenderMan Procedural plug-in, four Maya plug-ins, a Houdini plug-in, a number of command line tools, a Wavefront .obj parser, and two Python modules for reading, writing, and editing GTO files.
|Tags||multimedia Graphics 3D Modeling 3D Rendering Scientific/Engineering Visualization|
|Operating Systems||Mac OS X Unix|
Release Notes: A new optional ASCII file format was added. The C++ reading and writing classes were updated. The Python classes were updated. The following Maya plugins were added: deformer, particle import/export, particle display, and full Maya attribute handling. Houdini data can be imported and exported. Animation curve storage was added. Exceptions were added to the license for static linking and some other minor license issues were addressed to make it easier to use GTO in commercial products.
Release Notes: RiGTO, a RenderMan plugin for reading GTO files directly into prman/entropy and compatible renderers, was added. It implements an RiProcedural for GTO. The first draft of the new "strand" protocol for hair and hair-like geometry was completed.
Release Notes: The gtoContainer Python module compilation problems have been fixed. There are minor changes in the gtoContainer module API for consistency.
Release Notes: The file format has changed, and is source code compatible. An interpretation string has been added to the property header. A new high-level Python module was added, and the C++ Reader class is backwards-compatible with 2.x files.
Release Notes: gtofilter was changed to optionaly accept POSIX style regular expressions. The C++ writer class now defaults to writing compressed files. The proposed texture assignment protocol (from version 2.0.4) was rejected. A new "channel" protocol was included for assigning mapped surface varying data on geometry. An arbitrary number of texture maps may be assigned to the geometry. The material protocol was fleshed out.