• 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
neoaikon

XNA/HLSL Color Fading Issue

5 posts in this topic

Hello all, I recently wrote a shader that's only purpose was to fade out an all white texture passed to it, this texture is saved to a render target and then passed back into the shader. This works unless I set the fade value greater than .95f. When it's higher than .95f the color doesn't fade to black but to .1921f and stops. I initially tried the following pixel shader:

[code]float4 PixelShaderFunction(float4 cin : COLOR0, float2 coords: TEXCOORD0) : COLOR0
{
  cin = tex2D(inputsampler, coords)*.99;
  return cin;
}[/code]

with this the color does indeed fade, but not completely, the same thing happens when I use:

[code]float4 PixelShaderFunction(float4 cin : COLOR0, float2 coords: TEXCOORD0) : COLOR0
{
  cin = lerp(float4(0, 0, 0, 1), tex2D(inputsampler, coords), float4(.99f, .99f, .99f, .99f));
  return cin;
}[/code]

HOWEVER! When I use the following function, the color does fade completely as expected:

[code]float4 PixelShaderFunction(float4 cin : COLOR0, float2 coords: TEXCOORD0) : COLOR0
{
  cin = floor((tex2D(inputsampler, coords) * .99f)*255.0f);
  return cin/255.0f;
}[/code]

Why aren't the first two functions working as expected?! I can't see it being floating point precision, so what gives? [img]http://public.gamedev.net//public/style_emoticons/default/blink.png[/img] Just in case it's something in my drawing function, here it is:

[code]protected override void Draw(GameTime gameTime)
{
    graphics.GraphicsDevice.SetRenderTarget(rtA);
    graphics.GraphicsDevice.Clear(Color.Black);
    spriteBatch.Begin(SpriteSortMode.Texture, BlendState.Opaque, null, null, null, Diffusion);
    spriteBatch.Draw(Feedback, Vector2.Zero, Color.Black);
    spriteBatch.End();          

    graphics.GraphicsDevice.SetRenderTarget(rtB);
    graphics.GraphicsDevice.Clear(Color.Black);
    spriteBatch.Begin();
    spriteBatch.Draw(rtA, Vector2.Zero, Color.White);
    spriteBatch.End();

    Feedback = rtB;

    graphics.GraphicsDevice.SetRenderTarget(null);
    graphics.GraphicsDevice.Clear(Color.Black);
    spriteBatch.Begin();
    spriteBatch.Draw(rtB, Vector2.Zero, Color.White);
    spriteBatch.End();

    base.Draw(gameTime);
}[/code]
0

Share this post


Link to post
Share on other sites
In the first example, you multiply with a double precision value. You can try adding an f in the end in case that the compiler don't convert it.

I suspect that the input to the lerp function is in the wrong order in the second example since you pass a constant as variable s.
[url="http://msdn.microsoft.com/en-us/library/bb509618%28v=vs.85%29.aspx"]http://msdn.microsof...v=vs.85%29.aspx[/url]

I don't see why you multiply with 0.99.
0

Share this post


Link to post
Share on other sites
In the first example, adding f to the end does not help, this really doesn't seem to be an issue with precision from what I can tell.

The second example, I am lerping by a constant because the sampled color is the result of the last lerp operation.

I use .99 in all these examples because I want to remove 1% of the color value each pass, it's an extreme case but it is unusual that it doesn't work and a 4% lower value does.
0

Share this post


Link to post
Share on other sites
Hello Dawoodoz. You pretty much hit the nail on the head from what I found out last night, if I switch the surface format to use Vector4 then it behaves as expected in all cases, before that I was only using Color which provides 8 bits. When the color would reach .1921f (49) and get passed to the shader, the shader would multiply it by .99 giving us .1901 (48.495). From what I can gather although I can't find an official answer, is that something is causing that value to be consistently rounded upwards so when it is converted back into the Color Format, once it gets to 48.495 it gets rounded back up to 49 and will never return a lower value after reaching that point.
0

Share this post


Link to post
Share on other sites
If one runs the following code in a pixel shader:

[code]float4 PixelShaderFunction(float4 cin : Color0, float2 coords : TEXCOORD0) : COLOR0
{
cin = float4(.190235f, .190235f, .190235f, 1);
return cin;
}[/code]

you can see this rounding up behavior. 255.0f/49.0f = .192156 * .99f = .190235 * 255.0f = 48.51f. From previous experience in programming I'm used to the default behavior to be rounding down. In this case it seems the default behavior is to round up instead. Is this behavior documented anywhere?
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