Looking at the command list, regarding meshes:
I don't understand why indie languages always underestimate the importance of having proper mesh and animation support (either with interchangeable formats like FBX or Collada, or at least support for major modellers). So far, it is only useful for static meshes, unless you want to mess with old and limited gaming formats such as SMD/MD2/MD3/GL2.
The following formats are currently supported:
3DS (3DStudio, and many others)
MD2, MD3 (Quake2/3, animated)
OBJ (WaveFront, and many others)
SMD (Half-Life, skeletal animation, obtained from a decompiled MDL, f.i. with MilkShape)
NMF (Normal Mapper File, ATI tool)
GTS (GNU Triangulated Surface)
GL2 (Ghoul2, aka MDX)
OCT (FSRad)
And partial support is available for:
BSP (Quake3 BSP)
PLY (Stanford)
LWO (LightWave)
MS3D (MilkShape)
STL, TIN
3DS (3DStudio, and many others)
MD2, MD3 (Quake2/3, animated)
OBJ (WaveFront, and many others)
SMD (Half-Life, skeletal animation, obtained from a decompiled MDL, f.i. with MilkShape)
NMF (Normal Mapper File, ATI tool)
GTS (GNU Triangulated Surface)
GL2 (Ghoul2, aka MDX)
OCT (FSRad)
And partial support is available for:
BSP (Quake3 BSP)
PLY (Stanford)
LWO (LightWave)
MS3D (MilkShape)
STL, TIN
I don't understand why indie languages always underestimate the importance of having proper mesh and animation support (either with interchangeable formats like FBX or Collada, or at least support for major modellers). So far, it is only useful for static meshes, unless you want to mess with old and limited gaming formats such as SMD/MD2/MD3/GL2.