You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Go to file

TigerKat a2515dc7f3 bugfix: Wasn't skipping over a defunct field in version 7 and under files.		5 years ago
LICENSE	Initial commit	5 years ago
README.md	Made the input/output file type for geo.py more clearer.	5 years ago
bones.py	Initial import.	5 years ago
geo.py	bugfix: Wasn't skipping over a defunct field in version 7 and under files.	5 years ago
stl_dump.py	Initial import.	5 years ago

geopy

Python tools for manipulating .geo files. The long term plan is to be able to export .geos direct from Blender.

geo.py

Contains the Geo class, which represents the contents of .geo files. Can be run to test the reading and writing functionality.

geo.py <infile.geo> [<outfile.geo>]

If only an input .geo file is specified, it will read the input and dump the contents of the .geo to the console.

If an output .geo file is specified, it will read the input .geo file, and write the contents to the output as a new .geo file.

Dumps the meshes of a .geo file to .stl files. Used for testing and validation, as .stl isn't useful for games.

stl_dump.py <file.geo>

Dumps all the meshes contained in <file.geo> to <geo_name>/<model_name.stl>. <geo_name> and <model_name> are read from the .geo.

##Known issues:

Not all structures are read from the .geo file. (AltPivotInfo)
Not all structures are regenerated when writing a .geo file. (PolyGrid and Reductions)