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

OpenGL
Looking for a decent Assimp animation tutorial

4 posts in this topic

I've been trying to get my head around how to properly set up a skinning animation system using the bone transform data that can be imported using the Open Asset Import Library (http://assimp.sourceforge.net) but always seem to fail, which I admit is starting to get on my nerves.

I've made a good 5+ attempts inspired by this article: http://ogldev.atspace.co.uk/www/tutorial38/tutorial38.html as well as the limited hints that are given in the Assimp documentation. One thing to note is that I'm using DirectX rather than OpenGL, so things in the above tutorial will obviously not match to 100%, which may be where I'm going wrong. I'm adhering to the standard matrix multiplication order of scale * rotation * translation and I'm transposing all of Assimp's imported matrices which the documentation suggests are in a right handed format. Comparing my animation frame matrices to that exposed by the assimp_view application, they do seem to match so the problem most likely lies in the way I append all these local matrices in order to construct the final transform of each bone. Pseudo-code of my approach to that:

XMMATRIX transform = bone.localTransform;
BoneData *pParent = bone.pParent;
while(pParent) {
    transform = pParent.localTransform * transform;
    pParent = pParent.pParent;
}

// The actual bone matrix applied to each vertex, scaled by its weight, is calculated like so:
XMMATRIX mat = globalMeshInverseTransform * transform * bone.offsetMatrix;

The other thing I'm doing differently from all info on this I've been able to find is that I'm doing the vertex transformation on the CPU by updating the vertex buffer rather than doing it in a vertex shader. I do see the upside to the vshader approach, I just want to see that I'm able to do it in this, presumably easier, way before moving on to that though.

 

 

So my question is basically; is there anything obvious one needs to do when using DX rather than OGL or when setting vertex data on the CPU rather than in the vertex shader (not likely) that I've missed, or is there some more to-the-point tutorial on how to go about this somewhere (I've searched but haven't been able to find any), preferably using DirectX?

 

 

Thanks for any pointers, 

Husbjörn

0

Share this post


Link to post
Share on other sites

You don't mention any particular problems or symptoms of a problem, so I can only make a couple observations.

 

First, just for clarity, is your intent to implement a left-handed coordinate system? You mention D3D11, but that doesn't exclude right-handed systems.

 

Second, I'm not familiar with Assimp, so I can't help you much with that part of your project. But, from what you posted, you may have a couple problems.

 


I'm transposing all of Assimp's imported matrices which the documentation suggests are in a right handed format.

It's not clear what you mean by "right handed format." At a guess: transposing a matrix doesn't change the coordinate system handedness, if that's your intent. Transposition changes the matrix from row-major to column-major or vice-versa.

 

Also, as it appears that you're implementing left-to-right matrix multiplication order (SRT vs TRS), then you need to swap the order of parent-child matrix mults:

transform *= pParent.localTransform; // left-to-right order

The same would apply to the final bone transform. You say what you posted is pseudo-code so I'll leave my comments at that.

 

Don't know if it will help you, but you can take a look at my skinned-mesh article for a general description of the process for skinned-mesh animation.

1

Share this post


Link to post
Share on other sites

 

 

You don't mention any particular problems or symptoms of a problem

There isn't that much to mention, my meshes ends up looking like a pile of (wrongly) deformed polygons when I try to set it to match the first animation frame. I've been unable to find any consistency to further pinpoint the error more than to that they are obviously being wrongly transformed. The vertices do seem to keep within a radius that is approximately 2 - 3 times that of the untransformed mesh (in its default bind pose that is) however.

 

 

 

First, just for clarity, is your intent to implement a left-handed coordinate system?

Yes, I've already got a rendering system set up that's working with left-handed coordinates and now trying to add animation features on top of that. I suppose you're right in that this isn't a strict necessity when using DX but it seems to be what is nearly always used anyway so I basically just went with it.

 

 

 

It's not clear what you mean by "right handed format." At a guess: transposing a matrix doesn't change the coordinate system handedness, if that's your intent. Transposition changes the matrix from row-major to column-major or vice-versa.

Ah yes, I got the wording wrong here, they are transposed into row-major matrices. However upon reviewing the Assimp documentation it suggests that its matrices already are in row-major format, however not transposing them makes my static mesh imports appear backwards. Also not transposing the provided joint / frame offset matrices does neither provide the expected results.

 

 

 

Also, as it appears that you're implementing left-to-right matrix multiplication order (SRT vs TRS), then you need to swap the order of parent-child matrix mults

Hm, that does sound like something that may be wrong indeed. I'll take a look at it when I get home.

 

 

Also that's a great article you wrote, I've only skimmed through the first half of it so far but it does seem to be rather descriptive, so thanks a lot for that!

0

Share this post


Link to post
Share on other sites

Taking a fresh look at your post this morning, the algorithm for the final bone transforms doesn't appear efficient, and, depending on what you're actual code looks like, may be incorrect. You're working your way from child-to-parent. You're duplicating lots of calcs for any bone that has multiple children. You should start with the root frame (node, bone) and work your way through the children - i.e., parent-to-children. That's discussed in the article I linked.

Edited by Buckeye
1

Share this post


Link to post
Share on other sites

Taking a fresh look at your post this morning, the algorithm for the final bone transforms doesn't appear efficient, and, depending on what you're actual code looks like, may be incorrect. You're working your way from child-to-parent. You're duplicating lots of calcs for any bone that has multiple children. You should start with the root frame (node, bone) and work your way through the children - i.e., parent-to-children. That's discussed in the article I linked.

Yes, I'm aware it isn't efficient, its just written to be as obvious as possible so that I don't miss any errors in storing things in flattened hierarchy lists etc. as I intend to do once I get something up and running that I can see what's what from.

 

Anyway, thanks to your article and some more restructuring into a proper node hierarchy I've finally got the meshes to appear correct, albeit they seem to be offset by 90° around the X axis. I can just offset the root node to fix this but I'm thinking there must be something wrong with my transformations still (I haven't checked but there might be a translation / scale offset too by the looks of it). Anything that sounds familiar?

 

This is the code I'm using at the moment for applying transformations to the vertices:

            for(UINT m = 0; m < meshList.size(); m++) {
				Mesh *mesh = meshList[m].operator->();
				mesh->LockVertexData();
				size_t vertOffsetPos = mesh->GetVertexDataSemanticOffset("POSITION", 0);
				for(size_t v = 0; v < mesh->vertexCount; v++) {
					XMVECTOR vertexPos	= XMLoadFloat3(&(mesh->pBindPose->at(v)));
					XMFLOAT3 newPos;
					XMMATRIX matTransform	=	flattenedNodeList[mesh->pVertexWeight->at(v).boneId[0]]->matOffset * 
												flattenedNodeList[mesh->pVertexWeight->at(v).boneId[0]]->matGlobalTransform * 
												mesh->pVertexWeight->at(v).weight[0];

					for(UINT w = 1; w < 4; w++) {
						if(mesh->pVertexWeight->at(v).boneId[w] == 0xffffffff)
							break;
						matTransform += flattenedNodeList[mesh->pVertexWeight->at(v).boneId[w]]->matOffset * flattenedNodeList[mesh->pVertexWeight->at(v).boneId[w]]->matGlobalTransform * mesh->pVertexWeight->at(v).weight[w];
					}

					XMStoreFloat3(&newPos, XMVector3Transform(vertexPos, matTransform));
					mesh->SetVertexData(v, vertOffsetPos, newPos);
				}
				mesh->UnlockVertexData(); 
			} 

Edit: I tried to get the formatting to look better for the code section but it doesn't seem willing to play along so sorry for it looking a bit messed up.

Edit2: Ah, figured it out; I forgot to apply the mesh's inverse global transform; everything seems to be working as intended now smile.png

Onwards to making a more efficient implementation then, thanks again for your help Buckeye.

Edited by Husbjörn
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

  • Similar Content

    • By Toastmastern
      So it's been a while since I took a break from my whole creating a planet in DX11. Last time around I got stuck on fixing a nice LOD.
      A week back or so I got help to find this:
      https://github.com/sp4cerat/Planet-LOD
      In general this is what I'm trying to recreate in DX11, he that made that planet LOD uses OpenGL but that is a minor issue and something I can solve. But I have a question regarding the code
      He gets the position using this row
      vec4d pos = b.var.vec4d["position"]; Which is then used further down when he sends the variable "center" into the drawing function:
      if (pos.len() < 1) pos.norm(); world::draw(vec3d(pos.x, pos.y, pos.z));  
      Inside the draw function this happens:
      draw_recursive(p3[0], p3[1], p3[2], center); Basically the 3 vertices of the triangle and the center of details that he sent as a parameter earlier: vec3d(pos.x, pos.y, pos.z)
      Now onto my real question, he does vec3d edge_center[3] = { (p1 + p2) / 2, (p2 + p3) / 2, (p3 + p1) / 2 }; to get the edge center of each edge, nothing weird there.
      But this is used later on with:
      vec3d d = center + edge_center[i]; edge_test[i] = d.len() > ratio_size; edge_test is then used to evaluate if there should be a triangle drawn or if it should be split up into 3 new triangles instead. Why is it working for him? shouldn't it be like center - edge_center or something like that? Why adding them togheter? I asume here that the center is the center of details for the LOD. the position of the camera if stood on the ground of the planet and not up int he air like it is now.

      Full code can be seen here:
      https://github.com/sp4cerat/Planet-LOD/blob/master/src.simple/Main.cpp
      If anyone would like to take a look and try to help me understand this code I would love this person. I'm running out of ideas on how to solve this in my own head, most likely twisted it one time to many up in my head
      Thanks in advance
      Toastmastern
       
       
    • By fllwr0491
      I googled around but are unable to find source code or details of implementation.
      What keywords should I search for this topic?
      Things I would like to know:
      A. How to ensure that partially covered pixels are rasterized?
         Apparently by expanding each triangle by 1 pixel or so, rasterization problem is almost solved.
         But it will result in an unindexable triangle list without tons of overlaps. Will it incur a large performance penalty?
      B. A-buffer like bitmask needs a read-modiry-write operation.
         How to ensure proper synchronizations in GLSL?
         GLSL seems to only allow int32 atomics on image.
      C. Is there some simple ways to estimate coverage on-the-fly?
         In case I am to draw 2D shapes onto an exisitng target:
         1. A multi-pass whatever-buffer seems overkill.
         2. Multisampling could cost a lot memory though all I need is better coverage.
            Besides, I have to blit twice, if draw target is not multisampled.
       
    • By mapra99
      Hello

      I am working on a recent project and I have been learning how to code in C# using OpenGL libraries for some graphics. I have achieved some quite interesting things using TAO Framework writing in Console Applications, creating a GLUT Window. But my problem now is that I need to incorporate the Graphics in a Windows Form so I can relate the objects that I render with some .NET Controls.

      To deal with this problem, I have seen in some forums that it's better to use OpenTK instead of TAO Framework, so I can use the glControl that OpenTK libraries offer. However, I haven't found complete articles, tutorials or source codes that help using the glControl or that may insert me into de OpenTK functions. Would somebody please share in this forum some links or files where I can find good documentation about this topic? Or may I use another library different of OpenTK?

      Thanks!
    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
  • Popular Now