Just D3D9 FFP and DirectXMath use row-major layout.Ģ.) Using shaders give you the freedom to choose between A * B and B * A like you need. In memory this makes the same sequence of numbers.ĮDIT: So, after some more research … HLSL assumes column-major order at default, and GLSL assumes column-major order, too.

D3D11 is used to work with row vectors and matrices in column major order. compatible to DirectX in OpenGL (or vice versa, for all I care), without having to 'manually' adjust multiplication order and tampering with the matrix values? I'm also hoping that those issues will go away once that works, so well.ġ.) OpenGL 4 is used to work with column vectors and matrices in row major order. The question now mainly is: Is there any way, like some sort of setting, to make matrix multiplication, screen space etc. However, this was a total quess (I'm still quite surprised it works), and there are still occasional problems, like right now I'm trying to solve a complete f***-up in my cascaded shadow maps in opengl. Matrix MatPerspFovLH(float fovy, float aspect, float zn, float zf) I also flipped the sign of the m22-value in the projection-matrices to resolve a problem where everything was rendered upside down. First thing I did was flip the multiplication order when parsing out GLSL shader code.

Now most of my problems are due to matrix multiplications. My entry-point, if you will, is always DirectX11, because I'm far more common to it, and so are my coordinate systems (LH). For 90% of the times this works well without any kind of modification, but then there are times when I'm just having such trouble getting stuff to work under OpenGL4. I've writting myself a graphical wrapper for writing API independant code, also including a basic unified shading language.

Opengl 4.1 vs directx 11