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

How does the pipeline know the index what it need when it draws a quad using the vertices generated by the Geometry Shader?

4 posts in this topic

   Hi! I am learning how the Geometry Shader works in D3D11. I am studying a sample which inputs one point into the Geometry Shader and outputs a quad each time. As shown in the figure below, the sample specifies the vertices generated by the Geometry Shader.(Sorry. I don't know how to upload a image. Hope you can understand the figure.)

 

 

v1               v3

------------------

|                 |

|                 |

|                 |

|                 |

------------------

v0                v2

  With general method,if we want to draw a quad, we pass four vertices to the VertexBuffer, then create a IndexBuffer, binding them to the pipeline. Then the pipeline uses the data in the IndexBuffer and the VertexBuffer to draw two triangles what make up a quad. But in the sample I am studying, there is no IndexBuffer. The sample just generates these four vertices and append them to a TriangleStream object in the order: v0,v1,v2,v3, at the end of the Geometry Shader. Since D3D11 uses counter-clockwise culling state by default, visible triangles must be drawn in clockwise order. But how does the pipeline determine which three vertices of these four vertices to choose and their order to draw a visible triangle. There is no IndexBuffer in the sample. Maybe the Geometry Shader's output is drawn using a fixed index?Can anybody help me figure it out?

 

PS: The sample works well.

Edited by swdever
0

Share this post


Link to post
Share on other sites

http://www.gamedev.net/topic/586527-d3d11-geometry-shader-input-vertex-ordering/

 

So unless you provide adjacency information to your geometry shader, it appears to boil down to this value (http://msdn.microsoft.com/en-us/library/hh404489(v=vs.85).aspx):

 

FrontCounterClockwise

Type: BOOL

Specifies whether a triangle is front- or back-facing. If TRUE, a triangle will be considered front-facing if its vertices are counter-clockwise on the render target and considered back-facing if they are clockwise. If FALSE, the opposite is true.

 

 

Edited by Steve_Segreto
1

Share this post


Link to post
Share on other sites

The triangles you output from the GS are not indexed at all, since there are no indices. Instead you output one or more triangle strips. The vertices that you append to a TriangleStream form a strip according to the standard rules for a triangle strip topology. To mark the end of a strip, you call RestartStrip. If you want to just output a triangle list you can do so by appending 3 vertices, calling RestartStrip, and then repeating.

So in the case of your quad output from the GS, if you append all 4 verts and then call RestartStrip your 2 triangles will be (v0, v1, v2) and (v1, v2, v3), which means the winding order will be clockwise.

1

Share this post


Link to post
Share on other sites

The triangles you output from the GS are not indexed at all, since there are no indices. Instead you output one or more triangle strips. The vertices that you append to a TriangleStream form a strip according to the standard rules for a triangle strip topology. To mark the end of a strip, you call RestartStrip. If you want to just output a triangle list you can do so by appending 3 vertices, calling RestartStrip, and then repeating.

So in the case of your quad output from the GS, if you append all 4 verts and then call RestartStrip your 2 triangles will be (v0, v1, v2) and (v1, v2, v3), which means the winding order will be clockwise.

   I'm sorry there is an error in the figure I provided. It's my fault. I have corrected it. If D3D uses the order you provided to draw, that is, (v0, v1, v2) for the first triangle and (v1, v2, v3) for the second triangle. Then the first triangle's winding order will be clockwise and the second triangle's will be counter-clockwise .

   I find the diagram of vertex ordering for primitive types in this link.

http://msdn.microsoft.com/en-us/library/bb205124%28v=VS.85%29.aspx

   Maybe using the standard rules, the two triangles will be (v0, v1, v2) and (v1, v3, v2)?

0

Share this post


Link to post
Share on other sites

http://www.gamedev.net/topic/586527-d3d11-geometry-shader-input-vertex-ordering/

 

So unless you provide adjacency information to your geometry shader, it appears to boil down to this value (http://msdn.microsoft.com/en-us/library/hh404489(v=vs.85).aspx):

 

FrontCounterClockwise

Type: BOOL

Specifies whether a triangle is front- or back-facing. If TRUE, a triangle will be considered front-facing if its vertices are counter-clockwise on the render target and considered back-facing if they are clockwise. If FALSE, the opposite is true.

 

http://www.gamedev.net/topic/586527-d3d11-geometry-shader-input-vertex-ordering/

 

So unless you provide adjacency information to your geometry shader, it appears to boil down to this value (http://msdn.microsoft.com/en-us/library/hh404489(v=vs.85).aspx):

 

FrontCounterClockwise

Type: BOOL

Specifies whether a triangle is front- or back-facing. If TRUE, a triangle will be considered front-facing if its vertices are counter-clockwise on the render target and considered back-facing if they are clockwise. If FALSE, the opposite is true.

 

http://www.gamedev.net/topic/586527-d3d11-geometry-shader-input-vertex-ordering/

 

So unless you provide adjacency information to your geometry shader, it appears to boil down to this value (http://msdn.microsoft.com/en-us/library/hh404489(v=vs.85).aspx):

 

FrontCounterClockwise

Type: BOOL

Specifies whether a triangle is front- or back-facing. If TRUE, a triangle will be considered front-facing if its vertices are counter-clockwise on the render target and considered back-facing if they are clockwise. If FALSE, the opposite is true.

 

http://www.gamedev.net/topic/586527-d3d11-geometry-shader-input-vertex-ordering/

 

So unless you provide adjacency information to your geometry shader, it appears to boil down to this value (http://msdn.microsoft.com/en-us/library/hh404489(v=vs.85).aspx):

 

FrontCounterClockwise

Type: BOOL

Specifies whether a triangle is front- or back-facing. If TRUE, a triangle will be considered front-facing if its vertices are counter-clockwise on the render target and considered back-facing if they are clockwise. If FALSE, the opposite is true.

  I think you don't understand what I have asked. Maybe it because of my poor English. But I found the first link you provided is useful. I have got a deep understand in the circumstance I have encountered. Thank you!

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