Sign in to follow this  

DX11 DX11 Dynamic Linking compilation warnings

This topic is 2478 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi everyone!

We're experimenting with DX11 dynamic linking and ran into some weird warnings, leading to errors.
Has anyone any explanation for these? The internal error, for example, isn't very helpful :( When we inline the code from GetBias, some of the warnings disappear.

See below.


// WARNING X3578 HERE, line 246
float GetBias(const float2 depthGrad, const float2 offset) {
return dot(depthGrad, offset);
}

interface iShadowType {
float getShadow(const float2 depthGrad, const float2 uv);
};

class cShadowTypeNone : iShadowType {
// WARNING X3578, line 258
float getShadow(const float2 depthGrad, const float2 uv) {
return 1;
}
};

class cShadowTypePCF : iShadowType {
float getShadow(const float2 depthGrad, const float2 uv) {
float offset = 1;
float sum = 0;
if (uv.x == 1) {
float bias = GetBias(depthGrad, offset);
float shadow = shadowMap.SampleCmpLevelZero(sampCmpShadowMap, uv + offset, bias);
sum += shadow;
}
else
sum += 1;
return sum;
}
};

iShadowType shadowType;

cbuffer cbShadowType {
cShadowTypeNone shadowTypeNoneInstance;
cShadowTypePCF shadowTypePCFInstance;
};


interface iShadowShader {
float getShadow(const float2 depthGrad, const float2 uv);
};

class cShadowNone : iShadowShader {
float getShadow(const float2 depthGrad, const float2 uv) {
return 1;
}
};

class cShadowNoPCSS : iShadowShader {
float getShadow(const float2 depthGrad, const float2 uv) {
return shadowType.getShadow(depthGrad, uv);
}
};

iShadowShader shadowShader;

cbuffer cbShadowShader {
cShadowNone shadowNoneInstance;
cShadowNoPCSS shadowNoPCSSInstance;
};


The compilation log:

dynamicShadow.fxh(246,7): warning X3578: Output value 'GetBias' is not completely initialized
dynamicShadow.fxh(246,7): warning X3578: Output value 'GetBias' is not completely initialized
internal error: no storage type for block output
dynamicShadow.fxh(246,7): warning X3578: Output value 'GetBias' is not completely initialized
dynamicShadow.fxh(258,8): warning X3578: Output value 'cShadowTypeNone::getShadow' is not completely initialized
shading.fx(310,19): There was an error compiling expression

Share this post


Link to post
Share on other sites
OK, here we go. We fabricated this small sample, the errors are there.

Texture2D shadowMap;

SamplerComparisonState sampCmpShadowMap
{
Filter = COMPARISON_MIN_MAG_LINEAR_MIP_POINT;
AddressU = Border;
AddressV = Border;
BorderColor = float4(1.0, 1.0, 1.0, 1.0);
ComparisonFunc = LESS;
};

float GetBias(const float2 depthGrad, const float2 offset)
{
return dot(depthGrad, offset);
}

interface iShadowType
{
float getShadow(const float2 depthGrad, const float2 uv);
};

class cShadowTypeNone : iShadowType
{
float getShadow(const float2 depthGrad, const float2 uv)
{
return 1;
}
};

class cShadowTypePCF : iShadowType
{
float getShadow(const float2 depthGrad, const float2 uv)
{
float offset = 1;
float sum = 0;
if (uv.x == 1)
{
float bias = GetBias(depthGrad, offset);
float shadow = shadowMap.SampleCmpLevelZero(sampCmpShadowMap, uv + offset, bias);
sum += shadow;
}
else
sum += 1;
return sum;
}
};

iShadowType shadowType;

cbuffer cbShadowType
{
cShadowTypeNone shadowTypeNoneInstance;
cShadowTypePCF shadowTypePCFInstance;
};


interface iShadowShader
{
float getShadow(const float2 depthGrad, const float2 uv);
};

class cShadowNone : iShadowShader
{
float getShadow(const float2 depthGrad, const float2 uv)
{
return 1;
}
};

class cShadowNoPCSS : iShadowShader
{
float getShadow(const float2 depthGrad, const float2 uv)
{
return shadowType.getShadow(depthGrad, uv);
}
};

iShadowShader shadowShader;

cbuffer cbShadowShader
{
cShadowNone shadowNoneInstance;
cShadowNoPCSS shadowNoPCSSInstance;
};

float4 VS(float4 pos : SV_Position) : SV_Position
{
return pos;
}

float PS(float4 pos : SV_Position) : SV_Target
{
return shadowShader.getShadow(pos.xy, pos.zw);
}

technique10 Shading
{
pass P0
{
SetBlendState( NULL, float4( 0.0f, 0.0f, 0.0f, 0.0f ), 0xFFFFFFFF );
SetDepthStencilState( NULL, 0 );
SetRasterizerState( NULL );

SetVertexShader( CompileShader( vs_5_0, VS() ) );
SetGeometryShader( NULL );
SetPixelShader( CompileShader( ps_5_0, PS() ) );
}
}





And this is how you can compile it and what it'd say, to demonstrate the replicability.


c:\effects>"%DXSDK_DIR%/Utilities/Bin/x64/fxc.exe" /Ges /O3 /T fx_5_0 /nologo /Fo "compiled/Sample.fxo" Sample.fx
c:\effects\Sample.fx(12,7): warning X3578: Output value 'GetBias' is not completely initialized
c:\effects\Sample.fx(12,7): warning X3578: Output value 'GetBias' is not completely initialized
internal error: no storage type for block output
c:\effects\Sample.fx(12,7): warning X3578: Output value 'GetBias' is not completely initialized
c:\effects\Sample.fx(24,8): warning X3578: Output value 'cShadowTypeNone::getShadow' is not completely initialized
c:\effects\Sample.fx(106,19): There was an error compiling expression

compilation failed; no code produced



Share this post


Link to post
Share on other sites
MS does know about it now :) It is a compiler bug (possibly more than one) and so you'll have to work around it for the time being. There may be some recommendations later once someone has looked at the issue.

Share this post


Link to post
Share on other sites
Well, the feature isn't useless, it's just that you've tripped a bug. I'm not sure yet what the exact issue is since the current bits here don't repro the issue - so it seems that it was fixed at some point. You can however use functions and and interfaces together. It may just be an issue with types or perhaps with placement within the shader so a slight reorganization or perhaps an alternate method of doing the same thing will result in a working shader. It may also work fine on a different optimization level.

Share this post


Link to post
Share on other sites
I'm running into this problem right now with the June 2010 DirectX SDK. Did you find a good workaround for this problem? If so, what did you do? I think we're overdue for a new SDK release.

Share this post


Link to post
Share on other sites
Hi, for now can help using:

[code]void functionName(out outValue, otherParams...)[/code]
except

[code]outValue functionName(otherParams...)[/code]
It's not optimal solution, but works ;)

Share this post


Link to post
Share on other sites

This topic is 2478 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
      628715
    • Total Posts
      2984351
  • Similar Content

    • By GreenGodDiary
      Having some issues with a geometry shader in a very basic DX app.
      We have an assignment where we are supposed to render a rotating textured quad, and in the geometry shader duplicate this quad and offset it by its normal. Very basic stuff essentially.
      My issue is that the duplicated quad, when rendered in front of the original quad, seems to fail the Z test and thus the original quad is rendered on top of it.
      Whats even weirder is that this only happens for one of the triangles in the duplicated quad, against one of the original quads triangles.

      Here's a video to show you what happens: Video (ignore the stretched textures)

      Here's my GS: (VS is simple passthrough shader and PS is just as basic)
      struct VS_OUT { float4 Pos : SV_POSITION; float2 UV : TEXCOORD; }; struct VS_IN { float4 Pos : POSITION; float2 UV : TEXCOORD; }; cbuffer cbPerObject : register(b0) { float4x4 WVP; }; [maxvertexcount(6)] void main( triangle VS_IN input[3], inout TriangleStream< VS_OUT > output ) { //Calculate normal float4 faceEdgeA = input[1].Pos - input[0].Pos; float4 faceEdgeB = input[2].Pos - input[0].Pos; float3 faceNormal = normalize(cross(faceEdgeA.xyz, faceEdgeB.xyz)); //Input triangle, transformed for (uint i = 0; i < 3; i++) { VS_OUT element; VS_IN vert = input[i]; element.Pos = mul(vert.Pos, WVP); element.UV = vert.UV; output.Append(element); } output.RestartStrip(); for (uint j = 0; j < 3; j++) { VS_OUT element; VS_IN vert = input[j]; element.Pos = mul(vert.Pos + float4(faceNormal, 0.0f), WVP); element.Pos.xyz; element.UV = vert.UV; output.Append(element); } }  
      I havent used geometry shaders much so im not 100% on what happens behind the scenes.
      Any tips appreciated! 
    • By mister345
      Hi, I'm building a game engine using DirectX11 in c++.
      I need a basic physics engine to handle collisions and motion, and no time to write my own.
      What is the easiest solution for this? Bullet and PhysX both seem too complicated and would still require writing my own wrapper classes, it seems. 
      I found this thing called PAL - physics abstraction layer that can support bullet, physx, etc, but it's so old and no info on how to download or install it.
      The simpler the better. Please let me know, thanks!
    • By Hexaa
      I try to draw lines with different thicknesses using the geometry shader approach from here:
      https://forum.libcinder.org/topic/smooth-thick-lines-using-geometry-shader
      It seems to work great on my development machine (some Intel HD). However, if I try it on my target (Nvidia NVS 300, yes it's old) I get different results. See the attached images. There
      seem to be gaps in my sine signal that the NVS 300 device creates, the intel does what I want and expect in the other picture.
      It's a shame, because I just can't figure out why. I expect it to be the same. I get no Error in the debug output, with enabled native debugging. I disabled culling with CullMode.None. Could it be some z-fighting? I have little clue about it but I tested to play around with the RasterizerStateDescription and DepthBias properties with no success, no change at all. Maybe I miss something there?
      I develop the application with SharpDX btw.
      Any clues or help is very welcome
       


    • By Beny Benz
      Hi,
      I'm currently trying to write a shader which shoud compute a fast fourier transform of some data, manipulating the transformed data, do an inverse FFT an then displaying the result as vertex offset and color. I use Unity3d and HLSL as shader language. One of the main problems is that the data should not be passed from CPU to GPU for every frame if possible. My original plan was to use a vertex shader and do the fft there, but I fail to find out how to store changing data betwen shader calls/passes. I found a technique called ping-ponging which seems to be based on writing and exchangeing render targets, but I couldn't find an example for HLSL as a vertex shader yet.
      I found https://social.msdn.microsoft.com/Forums/en-US/c79a3701-d028-41d9-ad74-a2b3b3958383/how-to-render-to-multiple-render-targets-in-hlsl?forum=xnaframework
      which seem to use COLOR0 and COLOR1 as such render targets.
      Is it even possible to do such calculations on the gpu only? (/in this shader stage?, because I need the result of the calculation to modify the vertex offsets there)
      I also saw the use of compute shaders in simmilar projects (ocean wave simulation), do they realy copy data between CPU / GPU for every frame?
      How does this ping-ponging / rendertarget switching technique work in HLSL?
      Have you seen an example of usage?
      Any answer would be helpfull.
      Thank you
      appswert
    • By ADDMX
      Hi
      Just a simple question about compute shaders (CS5, DX11).
      Do the atomic operations (InterlockedAdd in my case) should work without any issues on RWByteAddressBuffer and be globaly coherent ?
      I'v come back from CUDA world and commited fairly simple kernel that does some job, the pseudo-code is as follows:
      (both kernels use that same RWByteAddressBuffer)
      first kernel does some job and sets Result[0] = 0;
      (using Result.Store(0, 0))
      I'v checked with debugger, and indeed the value stored at dword 0 is 0
      now my second kernel
      RWByteAddressBuffer Result;  [numthreads(8, 8, 8)] void main() {     for (int i = 0; i < 5; i++)     {         uint4 v0 = DoSomeCalculations1();         uint4 v1 = DoSomeCalculations2();         uint4 v2 = DoSomeCalculations3();                  if (v0.w == 0 && v1.w == 0 && v2.w)             continue;         //    increment counter by 3, and get it previous value         // this should basically allocate space for 3 uint4 values in buffer         uint prev;         Result.InterlockedAdd(0, 3, prev);                  // this fills the buffer with 3 uint4 values (+1 is here as the first 16 bytes is occupied by DrawInstancedIndirect data)         Result.Store4((prev+0+1)*16, v0);         Result.Store4((prev+1+1)*16, v1);         Result.Store4((prev+2+1)*16, v2);     } } Now I invoke it with Dispatch(4,4,4)
      Now I use DrawInstancedIndirect to draw the buffer, but ocassionaly there is missed triangle here and there for a frame, as if the atomic counter does not work as expected
      do I need any additional synchronization there ?
      I'v tried 'AllMemoryBarrierWithGroupSync' at the end of kernel, but without effect.
      If I do not use atomic counter, and istead just output empty vertices (that will transform into degenerated triangles) the all is OK - as if I'm missing some form of synchronization, but I do not see such a thing in DX11.
      I'v tested on both old and new nvidia hardware (680M and 1080, the behaviour is that same).
       
  • Popular Now