Standards for 2D transforming

[mankrip]

[Zylyx_]

Everything is done 3D, even things that seem to be 2D transformations they are done in 3D. There is no point in writing a matrix library/interface, since there are so many well written and free to use ones out there. Also, unless you know exactly what you are doing, chances are you are gonna end up with half assed matrix class that works not even half as well as other matrix operation classes out there.

Same goes for vector, quaternion and other misc maths functionality. OpenGL already provides a standardazied method for performing 2D rendering in a 3D scene.

[Zylyx_]

If you do really want to get your hands dirty, my personal recommendation:

[mh]

Direct3D comes with an incredibly rich set of matrix routines that cover just about anything you might want to do, are hyper-optimised, will give you SSE/etc support, and so on. They can even be linked to an OpenGL (or general math) program and used in that as they don't require a Device to be created. No D3D programmer in their right mind would use anything else; they might wrap them to handle conversion from in-game data types to D3D data types, and they might write special-case versions for specific circumstances that a generic library can't foresee, but otherwise why reinvent the wheel?

Unless it's fun of course, in which case by all means power ahead!

[mankrip]