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

Shader system approach

4 posts in this topic

Hi,
I arrived at the point that creating a good shader system in my engine is unevitable.
After quite some thinking i found/ thought of a few approaches.

Today
- defined an effect id to each mesh instance
- all effects include exactly the same lighting equations
(quite flexible though, including up to 3 drectional and 16 point lights in one pass, depending on sm2.0 or 3.0, read from my own scene file format)
- i'm also at the point of creating a grid for spatial culling (sort of quadtree in my scenegraph).
That way i only pass pont lights to the effect/shader if they have effect within the 'active node'/ frustum.
- my rendering function using scenegraph, now loops through: effects, materials, meshes, meshinstances
The decision on my shader system probably will affect this.
- i'm aware of deferred renderg but first want to 'master' this without

Scenario 1:
- separate lighting from other effects and create 1 generic and flexible lighting shader
(few variants based on input in my scene file format and the available shader model).
This effect includes materials, ambient lighting, directional lighting, point lights, transformations, single texturemapping, an opaque and a blended technique
- additional effects which can be used on mesh instance level, read from scene file format

Scenario 2:
- same as 1 but additional effects are on material level (might be to complex because a material isn't that big a part of the effect

Scenario 3:
- keep it as is today
- create my own engine's semantics list and do lighting through all the different effects if semantics exist

Scenario 4:
Other solutions?

This all basically comes down to the question, is it performance wise vs flexibility, worthwhile to go through the whole visible scene with more then one effect? (for meshinstances or materials that need something else then the lighting of the scene)

All advice is really appreciated.
0

Share this post


Link to post
Share on other sites

Which one sounds best to you?  Any of your approaches sound like they will work, so it is just a matter of what you want your engine to be able to do.  I put a premium on flexibility, with performance and usability coming next (in a tie).  But it sounds like you want to build the system for a specific lighting scheme, so flexibility probably isn't that important for your stated requirements.

0

Share this post


Link to post
Share on other sites

Hi Jason, thank for the reply.

Personally I'd say scenario one achieves all I need;

- have a generic lighting scheme/ shader which does all 'the basics' including lighting/ single texturing/ material etc..

This way when implementing 'nicer'/'better' lighting I don't need to change a lot of effects/shaders.

- for the lower number of mesh instances I can then use another effect for 'special effects'

 

The only thing I'm not sure of, is if this approach wil 'kill' performance, by executing multiple effect files on specific meshinstances during rendering.

0

Share this post


Link to post
Share on other sites

Unfortunately there is no good answer to that question.  No matter how you architect your engine, there is always the possibility that a particular scene can wipe out performance - even the big boys like iD and Unreal and Crytek all have their limitations.  That was why I was emphasizing the 'is it what you want' part of the question, since you will probably implement this and later on discover that there are some improvements or updates that you want to make.

 

I have been adding to my engine for well over 10 years now, with no end in sight :)

1

Share this post


Link to post
Share on other sites

Thanks, this really helps. I have to let go that I want to achieve the 'ultimate' situation (at once).

For now I'll go for scenario 1 because that achieves what I need now with high flexibility and 'relatively low' performance impact.

1

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