[SOLVED] Effect parameter not being set in OpenGL, however works in DirectX project

[jnoyola]

@markus

If you move the swizzle parameter above the
WorldViewProjection parameter

Yep, I’d recommend trying that, or commenting out the WorldViewProjection parameter entirely if it’s unused.

This reminds me of this issue that I and several other users have run into.

Shader parameter order bug

I’m using 2MGFX to compile a shader with the OpenGL profile, and I noticed a strange bug. I haven’t heard of anything like this, so I’m assuming it’s not a known issue. At the very top of my shader I have a bunch of constants to be taken as parameters: float4x4 World; float4x4 View; float4x4 Projection; float4x4 InverseViewProjection; float3 CameraPosition; float4x4 LightViewProjection; float3 LightPosition; float4 LightColor; float LightIntensity; ... and I found that some of the parameters …

I don’t remember all the details of the issue, but basically the shader compiler will aggressively remove unused parameters (or even unused individual columns of matrix parameters). However MonoGame isn’t made aware of this, so it will still pass parameters by index in the original order. So if your WorldViewProjection is unused, then when you set WorldViewProjection from code, it’s probably actually using the first column (or maybe first row?) to set swizzle.