04-14-2015, 08:54 PM
haha, thanks
I can't really get much working atm with my sm4sh script because I need to redo my bone verification.
I think I'm just gonna leave the LRS for the user (including supplied matrices), and then have the verifier calculate the bind and inv matrices for transformation of the supplied UT data...
btw, I officially HAATE MaxScript
I hated it before, but now that I'm dissecting RTB's noobishly formatted (poor indentation, hard to read, too many arrays, converts primitives to triangles, and more) code, I'd blow my brains out before working on a max-script...
now I can say Blender is far better than max.
I've always hated max's dirty, cluttered, and confusing user interface, but having a backend that operates more similar to the disgusting DAE format really makes me hate it.
the language for UMC-scripts is more closely related to OpenGL's FFP, so it's easy for noobs to use.
to add, UMC supports every type of primitive including quad-strips and polygons.
the automated file and data interfaces allow you to easily manage file data (rather than having to define functions for particular data types)
heck, UMC even goes as far as a #-byte IEEE754 float value:
float5 = bf(5)
data = float5() # read
UMC-scripts are based off python in which the indentation standard enforces readability.
@RTB: don't worry, I'm not mad at you in the least, though a little disappointed at the code...
still congrats for what you've done
I can't really get much working atm with my sm4sh script because I need to redo my bone verification.
I think I'm just gonna leave the LRS for the user (including supplied matrices), and then have the verifier calculate the bind and inv matrices for transformation of the supplied UT data...
btw, I officially HAATE MaxScript
I hated it before, but now that I'm dissecting RTB's noobishly formatted (poor indentation, hard to read, too many arrays, converts primitives to triangles, and more) code, I'd blow my brains out before working on a max-script...
now I can say Blender is far better than max.
I've always hated max's dirty, cluttered, and confusing user interface, but having a backend that operates more similar to the disgusting DAE format really makes me hate it.
the language for UMC-scripts is more closely related to OpenGL's FFP, so it's easy for noobs to use.
to add, UMC supports every type of primitive including quad-strips and polygons.
the automated file and data interfaces allow you to easily manage file data (rather than having to define functions for particular data types)
heck, UMC even goes as far as a #-byte IEEE754 float value:
float5 = bf(5)
data = float5() # read
UMC-scripts are based off python in which the indentation standard enforces readability.
@RTB: don't worry, I'm not mad at you in the least, though a little disappointed at the code...
still congrats for what you've done