struct ConstantBuffer
{
    float value0;
    float value1;
} g_CBData;

And in the Vertex Shader I'm just trying to multiply the color by the Sin() of any of these two values:

cbuffer cbPerFrame : register (b0)
{
    float  value0;
    float  value1;
};


struct VSInput
{
    float3 Pos : POSITION;
    float4 Col : COLOR;
};


struct VSOutput
{
    float4 Pos : SV_POSITION;
    float4 Col : COLOR;
};


VSOutput main( VSInput vs_in )
{
    VSOutput vs_out;

    vs_out.Pos = float4( vs_in.Pos, 1 );
    vs_out.Col = vs_in.Col * sin( value1 ); // "value0" runs ok, "value1" causes E_INVALIDARG

    return vs_out;
}

If I use "value0" everything runs well, however, if I use "value1" then I get an E_INVALIDARG when creating the VertexShader:

R = g_pDirect3D->CreateVertexShader( pVSData, vsSize, nullptr, &g_pVertexShader );

The weird thing is that if I don't use the sin() function (i.e. I just multiply Color * value1):

vs_out.Col = vs_in.Col * value0; // runs ok
vs_out.Col = vs_in.Col * value1; // runs ok

Then the values are read correctly.

Also I can't multiply value0 * value1, nor sum or anything between these two values.. when I do, I just get the E_INVALIDARG error.

Is there any strange rule when using the values from a constant buffer?

Thanks

Thanks Juliean,

In this particular case I'm precompiling the shader (I'm targeting Win8, so no effects framework, etc), and then I'm loading the compiled data to my app.

However, the error is not at compile time (it compiles just fine), but at creation time when calling:

g_pDirect3D->CreateVertexShader( pVSData, vsSize, nullptr, &g_pVertexShader );

So it just doesn't make sense to me that by using "sin( value0 )" the shader compiles, creates and runs without problems, but when using "sin( value1 )" the shader still compiles fine but cannot be created.

I just don't know what might be causing it

thanks!

Do you have the debug layer enabled? It should give you more detailed info about why CreateVertexShader call is failing.

Thankyou MJP,

Didn't know about the debug layer until now, I think I better start from there!

thanks!

In the end the problem was that I wasn't loading the compiled shader as a binary file, so, sometimes the file read was interrupted before the actual end, thus the CreateVertexShader() caused an E_INVALIDARG because the size of the vs data did not match the actual size of the shader.

dogh!...

anyways!... thanks for the help!