• 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

DrawIndexed vs DrawIndexedInstanced

2 posts in this topic

Just a quick one. It seems to be me that when creating a basic 3D engine, unless you're creating something that you know for a fact ahead of time that is only ever going to exist in one place in your scene (e.g. the ground terrain mesh), then it simplifies things if the default class for rendering meshes always assumes that multiple instances might exist, and therefore caters for that in terms of making an instance buffer available, and the shaders taking instancing information.


So I guess what I'm asking is, is it normal to set things up so you're using DrawIndexInstanced for most scene items, and DrawIndexed for the few other remaining things, or is it more normal to simply render each instance individually with DrawIndexed and leave DrawIndexInstanced for things like particles?

Edited by axefrog

Share this post

Link to post
Share on other sites

In my experience, it is easier to implement just one of the above for mesh rendering for example. It is rather small as an optimization to handle single mesh drawing as efficiently as possible versus drawing many meshes optimally, so in my opinion it isn't worth the extra code paths or extra shader code. 


I had both code paths originally, but eventually I dropped support for single drawing calls as that functionality exists still with the instanced draw calls.


Of course there are cases which are much simpler to handle with single draw calls or cases where instancing is less usefull (such as full screen quads). Also, particles can be drawn with geometry shader so instancing may not be the best approach (geometry shader is used to create the quads on screen from a singular vertex position). 


Terrain is another beast then, if you had one unique modelled mesh for a terrain, then instancing may sound unnecessary, but again, if it is a mesh, then your mesh class should have only one code path for drawing 1 or many meshes, so the first answer stands here too. On the other hand, if you are using something like a quadtree terrain LOD, then instancing can be used with drawing different terrain chunks.



Edited by kauna

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