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

[HLSL] Generic Blur Shader

2 posts in this topic

Hello,

 

I have some blur shader, but honestly it's hardly customizable. I'd like to have it more generic in such way that I set how many neighbours I want to get into calculations. My first attempt was to convert all of the TEXCOORDX into some array, but unfortunately it fails on compile time. What's wrong with it? (of course I have also changed pixel shader in the same way).

 

Vertex shader (before convertion):

 

 

 
cbuffer MatrixBuffer {
    matrix worldMatrix;
    matrix viewMatrix;
    matrix projectionMatrix;
};
 
struct VertexInputType {
    float4 position : POSITION;
    float2 tex : TEXCOORD0;
};
 
struct PixelInputType {
    float4 position : SV_POSITION;
    float2 tex : TEXCOORD0;
    float2 texCoord1 : TEXCOORD1;
    float2 texCoord2 : TEXCOORD2;
    float2 texCoord3 : TEXCOORD3;
    float2 texCoord4 : TEXCOORD4;
    float2 texCoord5 : TEXCOORD5;
    float2 texCoord6 : TEXCOORD6;
    float2 texCoord7 : TEXCOORD7;
    float2 texCoord8 : TEXCOORD8;
    float2 texCoord9 : TEXCOORD9;
    float2 texCoord10 : TEXCOORD10;
    float2 texCoord11 : TEXCOORD11;
    float2 texCoord12 : TEXCOORD12;
    float2 texCoord13 : TEXCOORD13;
    float2 texCoord14 : TEXCOORD14;
    float2 texCoord15 : TEXCOORD15;
};
 
PixelInputType HorizontalBlurVS( VertexInputType input ) {
    PixelInputType output;
    
    input.position.w = 1.0f;
    output.position = mul( input.position, worldMatrix );
    output.position = mul( output.position, viewMatrix );
    output.position = mul( output.position, projectionMatrix );
    output.tex = input.tex;
    
    float texelSize = 1.0f / 640.0f;
 
    output.texCoord1 = input.tex + float2( texelSize * -7.0f, 0.0f );
    output.texCoord2 = input.tex + float2( texelSize * -6.0f, 0.0f );
    output.texCoord3 = input.tex + float2( texelSize * -5.0f, 0.0f );
    output.texCoord4 = input.tex + float2( texelSize * -4.0f, 0.0f );
    output.texCoord5 = input.tex + float2( texelSize * -3.0f, 0.0f );
    output.texCoord6 = input.tex + float2( texelSize * -2.0f, 0.0f );
    output.texCoord7 = input.tex + float2( texelSize * -1.0f, 0.0f );
    output.texCoord8 = input.tex + float2( 0.0f, 0.0f );
    output.texCoord9 = input.tex + float2( texelSize *  1.0f, 0.0f );
    output.texCoord10 = input.tex + float2( texelSize *  2.0f, 0.0f );
    output.texCoord11 = input.tex + float2( texelSize *  3.0f, 0.0f );
    output.texCoord12 = input.tex + float2( texelSize *  4.0f, 0.0f );
    output.texCoord13 = input.tex + float2( texelSize *  5.0f, 0.0f );
    output.texCoord14 = input.tex + float2( texelSize *  6.0f, 0.0f );
    output.texCoord15 = input.tex + float2( texelSize *  7.0f, 0.0f );
 
    return output;
}

 

Vertex shader (converted):

 

 

 
cbuffer MatrixBuffer {
matrix worldMatrix;
matrix viewMatrix;
matrix projectionMatrix;
};
 
struct VertexInputType {
    float4 position : POSITION;
    float2 tex : TEXCOORD0;
};
 
struct PixelInputType {
    float4 position : SV_POSITION;
    float2 tex : TEXCOORD0;
    float2 texCoord[15] : TEXCOORD1;
};
 
PixelInputType HorizontalBlurVS( VertexInputType input ) {
    PixelInputType output;
 
    input.position.w = 1.0f;
    output.position = mul( input.position, worldMatrix );
    output.position = mul( output.position, viewMatrix );
    output.position = mul( output.position, projectionMatrix );
    output.tex = input.tex;
    
    float texelSize = 1.0f / 640.0f;
 
    output.texCoord[0] = input.tex + float2( texelSize * -7.0f, 0.0f );
    output.texCoord[1] = input.tex + float2( texelSize * -6.0f, 0.0f );
    output.texCoord[2] = input.tex + float2( texelSize * -5.0f, 0.0f );
    output.texCoord[3] = input.tex + float2( texelSize * -4.0f, 0.0f );
    output.texCoord[4] = input.tex + float2( texelSize * -3.0f, 0.0f );
    output.texCoord[5] = input.tex + float2( texelSize * -2.0f, 0.0f );
    output.texCoord[6] = input.tex + float2( texelSize * -1.0f, 0.0f );
    output.texCoord[7] = input.tex + float2( 0.0f, 0.0f );
    output.texCoord[8] = input.tex + float2( texelSize *  1.0f, 0.0f );
    output.texCoord[9] = input.tex + float2( texelSize *  2.0f, 0.0f );
    output.texCoord[10] = input.tex + float2( texelSize *  3.0f, 0.0f );
    output.texCoord[11] = input.tex + float2( texelSize *  4.0f, 0.0f );
    output.texCoord[12] = input.tex + float2( texelSize *  5.0f, 0.0f );
    output.texCoord[13] = input.tex + float2( texelSize *  6.0f, 0.0f );
    output.texCoord[14] = input.tex + float2( texelSize *  7.0f, 0.0f );
 
    return output;
}
0

Share this post


Link to post
Share on other sites

Don't pass all the offsets as interpolants from the vertex to the pixel shader, but calculate them on the cpu-side and upload them into a constant buffer:

 

 

cbuffer Filter{

   float2 offsets[OFFSETS_COUNT_MAX];
   unit   offsetsCount;
};

PS: for(uint i = 0; i < offsetsCount; ++i) ...
0

Share this post


Link to post
Share on other sites

I'm sorry but I don't understand it completely. How can I calculate offsets on cpu? The code requires the:

 

input.tex

 

to send the data later to the pixel shader, so where can I get the value with cpu? Sorry if this is stupid question.

 

// ---

 

Is there any other way (without constant buffer)?

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