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

How does clipping fit into the pipeline?

5 posts in this topic

Hello everybody, I'm trying to figure out how to implement clipping in my code. My understanding is that when a triangle crosses a clipping plane (ie the frustum), new vertices are added to avoid disappearing triangles artifacts. This is done on the CPU (correct?), and any object is eligible for clipping. But my question is: doesn't this make GL_STATIC_DRAW flag utopic? I mean, an object standing on the screen border gets clipped every frame, so its vertex data is far from being static (new vertices added and removed continuously).
Moreover, how does it fit with skinned meshes or any other GPU-generated vertices? Anyone got a good reference on clipping? All I've managed to find is either abstract theory or very basic examples.
0

Share this post


Link to post
Share on other sites
The GPU clips primitives automatically. AFAIK, there's no way to turn it [i]off[/i].
Manual clipping is only required for software renderers (not GL/D3D).

In GL, after your vertex shader, the transformed vertices are in Normalized Device Coordinates (NDC), which is a cube from (-1,-1,-1) to (1,1,1). Any primitives that clip the edge of this cube are handled appropriately by the GPU's rasterization hardware.
0

Share this post


Link to post
Share on other sites
Ok, thanks for clarifying! I can't find it right now, but one of the tutorial I stumbled upon stated that clipping was necessary in order for the rasterizer to remain inside its buffer. Somehow, I understood it was my responsibility to do that, not the hardware's. All the better then, I'll just remove invisible polygons and leave partially visible polygons as they are! Edited by King_DuckZ
0

Share this post


Link to post
Share on other sites
[quote name='King_DuckZ' timestamp='1348229245' post='4982334']
Hello everybody, I'm trying to figure out how to implement clipping in my code. My understanding is that when a triangle crosses a clipping plane (ie the frustum), new vertices are added to avoid disappearing triangles artifacts.
[/quote]
This is how OpenGL is specified - however, no-one actually does it that way (for eons). "Guard bands" are used ( http://en.wikipedia.org/wiki/Guard_band_clipping ). For normal frustum - there are no actual clip-planes used at all (even for near and far plane [i do not know any official names for it tho] - nowadays one can even turn that part off in OpenGL).
0

Share this post


Link to post
Share on other sites
[quote name='King_DuckZ' timestamp='1348231914' post='4982353']
Ok, thanks for clarifying! I can't find it right now, but one of the tutorial I stumbled upon stated that clipping was necessary in order for the rasterizer to remain inside its buffer. Somehow, I understood it was my responsibility to do that, not the hardware's. All the better then, I'll just remove invisible polygons and leave partially visible polygons as they are!
[/quote]

A lot of tutorial material is woefully out-of-date - either the tutorial was written sometime back in the 90s, or - if more recent - the person writing it hasn't bothered updating their understanding of things since that time. Back then clipping would certainly have been done on CPU, but by your driver, not by you. Since the advent of consumer-level hardware T&L much of the "knowledge" accumulated at that time is now completely irrelevant (or worse, it may lead the unwary to do awful things in their own code) so always be careful to double-check tutorial sources before you put much weight into what they say.
0

Share this post


Link to post
Share on other sites
[quote name='Hodgman' timestamp='1348229811' post='4982339']In GL, after your vertex shader, the transformed vertices are in Normalized Device Coordinates (NDC), which is a cube from (-1,-1,-1) to (1,1,1). Any primitives that clip the edge of this cube are handled appropriately by the GPU's rasterization hardware.[/quote]Not exactly. The transformed vertices are in clip space, which is a 4D space where every 3D point has a w value. Clipping happens here. The perspective divide happens AFTER this (divide everything by w), bringing it to (eventually) NDC.

It's an important distinction because negative w values are behind the camera and so are invisible. If clipping happened after the perspective divide, then vertices behind would be divided by negative w values and suddenly become visible!
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