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

Making world matrices available when drawing instanced objects

2 posts in this topic

Most of the tutorials and books I've been going through provide code and examples to specify object matrix data (world, view projection, world inverse transpose, etc) for individual objects by setting a constant buffer and then drawing the object, with the vertex shader referring to those values from the constant buffer.

 

In my case, I'm experimenting with drawing lots of the same object, instanced. Because each instance has its own world matrix and so forth, I can't just set these values in a constant buffer, which means it looks like my instance buffer needs to have all of the instance-specific matrices passed in as vertex shader parameters. In my case, that means, per instance, and in accordance with trying to translate what I saw being set in the constant buffer per object draw call (in the example code I'm referring to) to instead being set as vertex shader parameters, I have a color, a texture coordinate, a normal, a precalculated world-view-projection matrix, a world matrix for calculating lighting, and a world-inverse-transpose matrix for bring normals into world space after non-uniform scaling.

 

So, at this point, it means the vertex shader will have at least 3 vectors and at least 3 matrices being passed in, with each of those 3 matrices being precalculated per instance and being updated to the instance buffer every draw call. Is this ok? Or is this a red flag that I should be doing things more simply/efficiently? It seems that all those matrix calculations should be done on the GPU, but one of them involves inverting a matrix, and there doesn't seem to be a hlsl function for that.

Edited by axefrog
0

Share this post


Link to post
Share on other sites

Use structured buffers to store per instance data. Later in the shader use SV_InstanceID. that id is actually an index, witch is uniqe for each instance. You can use that index

do get the current object parameters from the StructuredBuffer.

 

It is possible to achieve the *same* results using constat buffers, but it will be slower, beause of the nature of cbuffers and how they are red from the memory.

2

Share this post


Link to post
Share on other sites

Not quite sure you understood the question, but even so, your advice corresponds to what I was looking for confirmation on, so thanks.

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