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

Same vertex, but different UV?

7 posts in this topic

Hello

 

I found this old thread http://www.gamedev.net/topic/171751-texture-coordinates-and-index-buffers-can-it-be-done/ which describes a problem I wanted to know if newer DirectX versions has addressed.

 

Suppose you have a Cube, which has 8 corners. But depending on which side of the cube that is being rendered, different UVs and Normals would have to be used. The thread concludes that the vertices would have to be duplicated in the seams that use different components.

 

I immediately start thinking of Streams and how they could possibly be used for solving this issue, but I can't figure out exactly how it can be done, or if it can be done.

 

Is it possible to move UV and Normal components over to the Index buffer in some way, such that a vertex may be drawn multiple times with different UVs?

0

Share this post


Link to post
Share on other sites

http://msdn.microsoft.com/en-us/library/windows/desktop/ff476335%28v=vs.85%29.aspx

 

You could put the vertex positions, normals and UVs each in a separate structured buffer, and the vertex buffer would simply contain indices into these three structured buffers.

Then, in the vertex or geometry shader, you simply use three structured buffers at the indices from the input vertex buffer.

0

Share this post


Link to post
Share on other sites

You can indeed bind multiple vertex buffers, but you can only bind a single index buffer. You'll always read from the vertex streams with a shared index.

 

Mesh resolutions have become higher and thus smoother, resulting in less duplication needed, so in a way it has been addressed/minimized.

Compared to a few duplicated vertices, having multiple index buffers would only have higher demands on memory, because then every vertex is guaranteed to carry extra information (a fixed set of indices).

1

Share this post


Link to post
Share on other sites

The case of the cube is an extreme example because every vertex is on a seam. In a realistic sensibly-UV-mapped model the proportion of vertices that need to be duplicated for such a reason is small as a proportion of the total number of vertices: the vertex count is far more likely to be dominated by those internal to smoothly-varying portions of the model, which have shared positions, normals and textures.

 

Basically, under normal circumstances the overhead of duplicated vertex data at seams is unlikely to be a cause for concern in terms of performance or memory.

2

Share this post


Link to post
Share on other sites

For the specific case of a cube, you can use instancing to achieve a similar result.  With this setup, you create a single fully-specified unit cube in one vertex buffer, then use a per-instance buffer to store the center position and size of each cube you wish to draw.  Each cube therefore only needs 4 floats (assuming it doesn't need to be rotated) and this can be done even with D3D9.

 

For D3D10+ you can specify a cube using only positions and output normals and texcoords from a geometry shader, but that's likely to be slower than the instancing method.

 

Either way a second index buffer isn't even necessary, even if it was possible.

0

Share this post


Link to post
Share on other sites


Mesh resolutions have become higher and thus smoother, resulting in less duplication needed, so in a way it has been addressed/minimized.

 

So smooth surfaces do not duplicate vertices at the same position? I figure the Normal must then be a blend of the 3 adjacent face normals?

0

Share this post


Link to post
Share on other sites


So smooth surfaces do not duplicate vertices at the same position? I figure the Normal must then be a blend of the 3 adjacent face normals?

 

Yes, for a cube specifically, that would be problematic. If you tie the SV_VertexID semantic to a vertex shader input (D3D10+), you can forego vertex buffers altogether and construct a cube in its entirety in the vertex shader based of the index value that's passed in.

1

Share this post


Link to post
Share on other sites


but you can only bind a single index buffer

That's why I said he can put the indices into a vertex buffer:


and the vertex buffer would simply contain indices into these three structured buffers
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