• 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

Forget the Index Buffer?

5 posts in this topic

Hi

 

My model viewer application is getting more and more complex and it starts acting up on me, so I really wish to reduce the complexity to avoid alot of recoding. What I find interesting is that most of my vertices are unique, meaning that indexing the same vertex twice is uncommon since they usually need to have different normals.

 

What I use now is a ID3DXMesh that I fill with vertices and indices. I optimize it and Generate Adjacency on it. But what is the point of all that when most of the indices are mapped 1:1 on the vertex buffer?

 

Should I just toss out the ID3DXMesh and roll my own class with only the vertex buffer and not the index buffer?

 

Cheers!

0

Share this post


Link to post
Share on other sites

What I find interesting is that most of my vertices are unique, meaning that indexing the same vertex twice is uncommon since they usually need to have different normals.

You must have some seriously strange models - any contiguous smooth ares in your surface ought to share vertices.

 

Are you modelling a sea urchin?

0

Share this post


Link to post
Share on other sites

Maybe I misunderstand but arent a triangle supposed to have normals perpendicular to its surface?

 

If two triangles share a side (neighbours), but are not in parallell then the two shared vertices must have different normals?

 

Are you saying that in a smooth surface, a vertex which is shared between three triangles will have its normal, equal to the avarage normal of three normals each perpendicular to its triangle plane?

 

Think of a cube (not smooth), should it have 8 vertices, one for each corner (indexed), or should it have 24 vertices (non-indexed) to contain all normals? If the former, where would the normal vector be pointing?

0

Share this post


Link to post
Share on other sites

Vertices should each have a normal perpendicular to the surface at that point. The only place where you need duplicated vertices is where there is a hard corner (or 'crease') in the mesh.

 

As a trivial example, all edges on a cube are hard edges, so a cube needs vertices duplicated per-face. A sphere is a continuous surface without hard edges, so none of the vertices should be duplicated.

0

Share this post


Link to post
Share on other sites

You might be right. I am fiddling with UV maps and trying to map them to a vertex buffer. The catch is that the vertex buffer might be indexed more then once with different UV coordinates.

 

It seems like a shortcut to just duplicate all vertices, the downside is that it potentially triples the vertex buffer size. Does that translate into a third of the potential performance?

 

Also, my characters have may equip different gear, and gear may hide other gears subsets and so on, so there are multiple drawcalls on each piece of gear. I am thinking of batching the character into a single vertex buffer where ranges are draw depending on the texture.

0

Share this post


Link to post
Share on other sites

If you have multiple draw calls an index buffer may still be useful as it will allow you to concatenate the different primitives and handle everything with a single draw call.  This may or may not involve having to create a dynamic buffer, which will have it's own overhead, but either way - I'd strongly urge you to profile and see if the perf gain from being able to do a single draw call is worth it nonetheless, rather than making assumptions based on memory usage alone (which is quite often not even a valid benchmark).

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