• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
DOrmisher

Bizzare shader error

8 posts in this topic

Hi, something strange is happening that I don't understand. This is the code for my shader that does a guassian blur:
void main( in PS_Input i, out PS_Output o )
{
	float4 TotalColour = 0;
    float texelSize = float( 1.0f / TexWidth );
    
    TotalColour += tex2D( Tex0, float2( i.TexCoord0.x, i.TexCoord0.y ) ) * ( KernelSize+1.0f ) / (100.0f/KernelSize);
    
    int limit = KernelSize;
    
	// Loop as many times as there are kernels
	for( int p=1; p <= KernelSize; p++ )
    {
		TotalColour += tex2D( Tex0, float2( i.TexCoord0.x - ( p*texelSize ), i.TexCoord0.y) ) * (KernelSize+1 -p) / (100.0f/KernelSize);
		TotalColour += tex2D( Tex0, float2( i.TexCoord0.x + ( p*texelSize ), i.TexCoord0.y) ) * (KernelSize+1 -p) / (100.0f/KernelSize);
    }
    
	o.Colour.rgba = TotalColour;
    o.Colour.a = 0.3f;
}
When I try to compile I am getting an error and subsequent warning: warning X3553: Can't use gradient instructions in loops with break, forcing loop to unroll error X3511: Unable to unroll loop, loop does not appear to terminate in a timely manner (1024 iterations) However, if I change the loop parameter to an integer rather than the KernelSize constant it runs and works perfectly. This is the code with that one change:
void main( in PS_Input i, out PS_Output o )
{
	float4 TotalColour = 0;
    float texelSize = float( 1.0f / TexWidth );
    
    TotalColour += tex2D( Tex0, float2( i.TexCoord0.x, i.TexCoord0.y ) ) * ( KernelSize+1.0f ) / (100.0f/KernelSize);
    
    int limit = KernelSize;
    
	// Loop as many times as there are kernels
	for( int p=1; p <= 5; p++ )
    {
		TotalColour += tex2D( Tex0, float2( i.TexCoord0.x - ( p*texelSize ), i.TexCoord0.y) ) * (KernelSize+1 -p) / (100.0f/KernelSize);
		TotalColour += tex2D( Tex0, float2( i.TexCoord0.x + ( p*texelSize ), i.TexCoord0.y) ) * (KernelSize+1 -p) / (100.0f/KernelSize);
    }
    
	o.Colour.rgba = TotalColour;
    o.Colour.a = 0.3f;
}
That is the only thing that is stopping the shader from working correctly, and without that, I can't have any sort of flexibility with the shader. Anybody any ideas why this is happening?
0

Share this post


Link to post
Share on other sites
OK, this is a bit difficult to explain. First, the reason why the second one works, is because it is automatically unrolled. You loop a constant amount of iteration, so the compiler can silently unroll without side effects.

Now, the reason the first doesn't work as expected, is due to the fact that derivatives (as used by a gradient instruction, such as tex2D) are undefined within a conditional statement (such as the one implicitly used by the loop).

You can solve this by either not using derivatives at all (ie. supplying a constant LOD through tex2DLod rather than the tex2D) or by manually computing the derivatives outside of the loop, and supplying them explicitly. If you only want to blur a screen aligned rectangle, then the best method is the former one.
0

Share this post


Link to post
Share on other sites
Ok thanks for the reply I understand. I just looked up tex2Dlod on msdn, and it states that the second input parameter, i.e. the UV coords, should be a float4. How can there be 4 part coordinate for a texture UV??
0

Share this post


Link to post
Share on other sites
I just solved the problem by making it a float4 and adding a couple of 1.0f's in the constructor and it seems to work. Don't really understand why though...
0

Share this post


Link to post
Share on other sites
Quote:
Original post by DOrmisher
Ok thanks for the reply I understand. I just looked up tex2Dlod on msdn, and it states that the second input parameter, i.e. the UV coords, should be a float4. How can there be 4 part coordinate for a texture UV??

Because some texture operations require 3-dimensional coordinates (UVW, for example volume textures) or 4-dimensional homogeneous ones (projective texturing). If you don't need the last two components, you should set them to 0 and 1, respectively.
0

Share this post


Link to post
Share on other sites
Quote:
Original post by Yann L
Quote:
Original post by DOrmisher
Ok thanks for the reply I understand. I just looked up tex2Dlod on msdn, and it states that the second input parameter, i.e. the UV coords, should be a float4. How can there be 4 part coordinate for a texture UV??

Because some texture operations require 3-dimensional coordinates (UVW, for example volume textures) or 4-dimensional homogeneous ones (projective texturing). If you don't need the last two components, you should set them to 0 and 1, respectively.


Actually, when using tex2Dlod you should put the mip level that you want to sample in the 4th component of the texture coordinate.
0

Share this post


Link to post
Share on other sites
Quote:

Actually, when using tex2Dlod you should put the mip level that you want to sample in the 4th component of the texture coordinate.

I was more referring to the general question of why texture coordinates can have three or four components. But yeah, tex2Dlod specifically uses a somewhat broken and inconsistent semantic.
0

Share this post


Link to post
Share on other sites
Quote:
Original post by Yann L
Quote:

Actually, when using tex2Dlod you should put the mip level that you want to sample in the 4th component of the texture coordinate.

I was more referring to the general question of why texture coordinates can have three or four components. But yeah, tex2Dlod specifically uses a somewhat broken and inconsistent semantic.


The tex bias funcions also use the w component as the bias value, and the tex proj functions use w for the projective divide. It is best to check the docs when first using any of the tex functions, because the use of the w component is quite inconsistent.
0

Share this post


Link to post
Share on other sites
I think the error was refering to the fact that "5" is defined, but "KernelSize" is a variable with a unknown value. The compiler does not know if KernelSize > 1024


As for the UV coords, both of these lines of code are the same:

cDiffuseMap.rgb = tex2D(diffuseMapSampler,baseTC.xy);
cDiffuseMap.rgb = tex2D(diffuseMapSampler,float4(baseTC.xy, 0, 1.0));

The extra zw coords are ignored.


0

Share this post


Link to post
Share on other sites

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  
Followers 0