• 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
3DModelerMan

Skeleton representation

4 posts in this topic

I'm working on a skeletal animation and skinning system for my engine and I'm trying to decide what the best way to store the skeleton would be. I already have a hierarchical game object system that can be set to play an animation clip by attaching a component to it. I plan on having attachment support for my skeletal animation (attaching guns, swords, etc as children of a specific bone). Would it be a bad idea to use the existing hierarchical object system as my skeleton? I would just load each bone as a child object, and that would allow me to attach any sort of component I wanted to each bone later, or add child objects to them. Would there be any problems with this approach, other than the fact that the bone hierarchy would need to be traversed at the beginning of each frame to generate a new set of matrices for use by the vertex shader in skinning?

0

Share this post


Link to post
Share on other sites

Would there be any problems with this approach, other than the fact that the bone hierarchy would need to be traversed at the beginning of each frame to generate a new set of matrices for use by the vertex shader in skinning?

 

Assuming you're talking about an animated object, you don't mention how you would render it without updating the matrices each frame. The common method of rendering a hierarchical animated skinned object calculates the animation matrices each frame in any case. Adding a couple of extra calculations per frame shouldn't be a burden. However, in such a case, if you add-remove attachments dynamically (at run-time), that complicates things quite a bit, depending on your implementation. Commonly, for efficiency, the animated mesh (without attachments) is a single vertex/index buffer. If you have a separate mesh for each arm, each leg, etc., your method should work, but would be rather inefficient.

 

More commonly, attachments are separate meshes (separate vertex/index buffers) and are rendered separately, as desired. You can set a flag for each attachment to indicate whether it should be rendered or not.

Edited by Buckeye
1

Share this post


Link to post
Share on other sites

Okay, so it's basically the same thing as a normal system performance wise then. I don't think the attachments would need to cause an update at runtime if they didn't affect the transform for current frame would they? Or are you talking about how the bone indices are assigned to the matrix array?

1

Share this post


Link to post
Share on other sites

Okay, so it's basically the same thing as a normal system performance wise then. I don't think the attachments would need to cause an update at runtime if they didn't affect the transform for current frame would they? Or are you talking about how the bone indices are assigned to the matrix array?

 

If rendering an attachment doesn't require a change in the frame transforms array, you're correct - no problem. Without details of your implementation, I had to generalize.

Edited by Buckeye
1

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