• 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
Yours3!f

Instance culling theory

4 posts in this topic

Hi,

 

I've implemented instance culling using instance cloud reduction described here:
http://rastergrid.com/blog/2010/02/instance-culling-using-geometry-shaders/

This technique works by storing the instance positions in a VBO, then using a vertex shader to cull them (basically render them), then using the transform feedback mechanism and a geometry shader only store those in an output vbo that passed the visibility testing. Now this way the geometry shader outputs GL_POINTS (vec4). This way only position is considered.

Now in my app I'd like to use rotation and scaling as well. As far as I know, this can be best described by a matrix. My question is: how can I output these matrices with the geometry shader? Should I output more than one vertices (more EmitVertex();)? How do they get stored in the output vbo?

Plus how would the culling be done? should I just transform the bounding box by this matrix? then check that?

 

Best regards,

Yours3!f

Edited by Yours3!f
1

Share this post


Link to post
Share on other sites

Write to 4 out vec4 varying attribs. One for the x axis, y axis, z axis, and position. Make sure you set each one before calling EmitVertex().

out vec4 xaxis;

out vec4 yaxis;

out vec4 zaxis;

out vec4 CulledPosition;

 

So basically, you can still use a single vertex, but the varying attribs for that vertex will include a full matrix (which will be combined into your instanced modelview matrix attrib).

Edited by RobTheBloke
1

Share this post


Link to post
Share on other sites

Write to 4 out vec4 varying attribs. One for the x axis, y axis, z axis, and position. Make sure you set each one before calling EmitVertex().

out vec4 xaxis;

out vec4 yaxis;

out vec4 zaxis;

out vec4 CulledPosition;

 

So basically, you can still use a single vertex, but the varying attribs for that vertex will include a full matrix (which will be combined into your instanced modelview matrix attrib).

 

thanks I'll try this. And what about the culling?

0

Share this post


Link to post
Share on other sites

What about it? Unless you want to use a more elaborate scheme (OBB<->Frustum, OBB tree<->Frustum) it should be the same no? If you do want to use something else, then you'll be passing in more in varying attrs to your geometry shader (for the rest of the matrix axes, and possibly an extents vector, or radius). The high level approach isn't going to change, just the tests you're using within the geometry shader

1

Share this post


Link to post
Share on other sites

What about it? Unless you want to use a more elaborate scheme (OBB<->Frustum, OBB tree<->Frustum) it should be the same no? If you do want to use something else, then you'll be passing in more in varying attrs to your geometry shader (for the rest of the matrix axes, and possibly an extents vector, or radius). The high level approach isn't going to change, just the tests you're using within the geometry shader

 

oh ok, I thought it would change radically.

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