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

Branch or two diffrent shaders for "help" objects.

6 posts in this topic

Hi.

In my system there is currently objects and "helper" objects. Objects reacts to light and all other kinds to effects. "Helper" object are lines that can be a object's normal or axes, and this objects should not be affect by the render effects (Lines has no normals so they can be anyway).. How should this be handle, should have two diffrent shaders one that handels the usual stuff and one with our any effects or have the have a boolean on the objects that says "no effects" and the branch the shader accordingly?

0

Share this post


Link to post
Share on other sites

Do not use dynamic branching (if statement) in  your shader, it will only slow the retail version down.

You could use defines and compile the shader two times (with and without the define, so with and without helpers). 

 

 

What I do in my framework, is a separated class to render debug related stuff (cleverly called DebugRenderer J ). 

It provides a couple of functions (draw line, sphere, quad, ..).

Whenever I want to debug something (for example normals or a rendertarget), I issue a number of draw commands to the DebugRenderer, who stores them internally.

Near the end of the frame (in my case before the present), I let the debugrenderer draw on top of the final frame buffer.

1

Share this post


Link to post
Share on other sites

Super thx folks. This helps a lot and opens up my eyes for the complexity of shader developing.

 

A short follow up question. So if i have one shader which I compile multiple times with different define paths each time. Is it possible to automate this process in VS2012? I setup so VS is compiling the shader when it builds everything else.

0

Share this post


Link to post
Share on other sites

Super thx folks. This helps a lot and opens up my eyes for the complexity of shader developing.

 

A short follow up question. So if i have one shader which I compile multiple times with different define paths each time. Is it possible to automate this process in VS2012? I setup so VS is compiling the shader when it builds everything else.

Yes that is perfectly possible.

 

If you use the effect framework (.fx files with techniques, passes, ...), you can simple make a custom build event that calls fxc.exe (see http://msdn.microsoft.com/en-us/library/windows/desktop/bb509709(v=vs.85).aspx for syntax).

 

If you use straight forward hlsl code (that you compile using D3DCompile) is a bit more work as you need to create a small program or script (that you again call using a custom build event). this program/script compiles the shader based on arguments and writes it as a binary blob to a file.

 

If you really feeling it, you could add custom build rule to visual studio (http://msdn.microsoft.com/en-us/library/xfsbz6cw(v=vs.80).aspx)

1

Share this post


Link to post
Share on other sites

If you use straight forward hlsl code (that you compile using D3DCompile) is a bit more work as you need to create a small program or script (that you again call using a custom build event). this program/script compiles the shader based on arguments and writes it as a binary blob to a file.

 

I use hlsl code so i will try it out.

 

It would be interesting to know how the big house solves this problem. Do they have one mega shader that is compile with Diffrent options or do they use a more branched approched. The mega shader would be very large and would have to be compiled with many many many options (the combinations would be almost endles, Point light with X function, Spot light with X function and so on). This would be a major overhead in the development process i guess.

0

Share this post


Link to post
Share on other sites

Sorry for intrusion.

 

What about single branch, for example lightning pixel shader (DX9):

float4 pixelProgram(...) : COLOR
{
    float4 outColor = 0.0f;
    if(dot(lightDir, normal) < 0.0f)
    {
    ...// do light calc
    }
    return outColor;
}

Is it worth it?

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