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

Retriving Indices from mesh buffer

4 posts in this topic

So I'm using ID3DXMESH to store a .X file, I'm loading it into the application with D3DXLoadMeshHierarchyFromX. I'm trying to get the vertex and index buffer from the mesh but getting incorrect results. The vertex buffer is correct but the index buffer is not, at least I don't think so. To simplify things; I created a basic cube mesh .X file. I've been changing around the index values of the file and the model changes shape but the returned index buffer does not reflect what is stated in the file.

 

 

DWORD numFaces = pCurrentFrame->pMeshContainer->MeshData.pMesh->GetNumFaces();
 
if(MESHFLAGS&D3DXMESH_32BIT)
{
DWORD* indices;
DWORD tempIndex;
pCurrentFrame->pMeshContainer->MeshData.pMesh->LockIndexBuffer(D3DLOCK_NOOVERWRITE | D3DLOCK_READONLY,        (void**)&indices);
 
for(DWORD k = 0; k < (numFaces*3); k++)
{
memcpy(&tempIndex, indices, sizeof(DWORD));
indices++;
}
}
 
else
{
WORD* indices;
WORD tempIndex;
pCurrentFrame->pMeshContainer->MeshData.pMesh->LockIndexBuffer(D3DLOCK_NOOVERWRITE | D3DLOCK_READONLY, (void**)&indices);
 
for(DWORD k = 0; k < (numFaces*3); k++)
{
memcpy(&tempIndex, indices, sizeof(WORD));
tempIndex = 0;
indices++;
}
}
 
pCurrentFrame->pMeshContainer->MeshData.pMesh->UnlockIndexBuffer();
 
what I get back for my index values is 0,1,2,3,4,5,6,7,8,9,10,6,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,23,28,29,30,31,28,32
 
 
here's the vertex and index information from the file.
 
   Mesh { //Cube_001 Mesh
      36;
      -1.000000; 1.000000;-1.000000;,
       1.000000; 1.000000;-1.000000;,
       1.000000; 0.999999; 1.000000;,
      -1.000000; 1.000000; 1.000000;,
      -1.000000; 1.000000;-1.000000;,
       1.000000; 0.999999; 1.000000;,
      -1.000000; 1.000000; 1.000000;,
      -1.000000;-1.000000; 1.000000;,
      -1.000000;-1.000000;-1.000000;,
      -1.000000; 1.000000;-1.000000;,
      -1.000000; 1.000000; 1.000000;,
      -1.000000;-1.000000;-1.000000;,
      -1.000000;-1.000000;-1.000000;,
       0.999999;-1.000001; 1.000000;,
       1.000000;-1.000000;-1.000000;,
      -1.000000;-1.000000;-1.000000;,
      -1.000000;-1.000000; 1.000000;,
       0.999999;-1.000001; 1.000000;,
       1.000000;-1.000000;-1.000000;,
       1.000000; 0.999999; 1.000000;,
       1.000000; 1.000000;-1.000000;,
       1.000000;-1.000000;-1.000000;,
       0.999999;-1.000001; 1.000000;,
       1.000000; 0.999999; 1.000000;,
       0.999999;-1.000001; 1.000000;,
      -1.000000; 1.000000; 1.000000;,
       1.000000; 0.999999; 1.000000;,
       0.999999;-1.000001; 1.000000;,
      -1.000000;-1.000000; 1.000000;,
      -1.000000; 1.000000; 1.000000;,
      -1.000000;-1.000000;-1.000000;,
       1.000000;-1.000000;-1.000000;,
       1.000000; 1.000000;-1.000000;,
      -1.000000; 1.000000;-1.000000;,
      -1.000000;-1.000000;-1.000000;,
       1.000000; 1.000000;-1.000000;;
      12;
      3;0;1;2;,
      3;1;4;5;,
      3;6;7;9;,
      3;9;10;11;,
      3;3;1;4;,
      3;15;16;12;,
      3;18;14;20;,
      3;21;22;23;,
      3;24;25;27;,
      3;27;35;29;,
      3;30;31;32;,
      3;33;34;35;;
 
It doesn't seem like it's right, is the LoadHierarchy function doing some kind of optimization behind the scenes, are the returned values somehow correct or am I just doing something wrong?
 
Thanks for any help!
 
 
 

 

 

0

Share this post


Link to post
Share on other sites

This is how i lock the mesh and get the vertices , you might be able to work something out with the indices

 

[code] 

void LockMesh(LPD3DXMESH Mesh)
{
 
 
BYTE* lpbVb;
int numIndices;
BYTE *lpIB;
DWORD idxVbVert0, idxVbVert1, idxVbVert2;
D3DINDEXBUFFER_DESC ibdesc;
    LPDIRECT3DINDEXBUFFER9 lpIndexBuffer = NULL;
Mesh->LockVertexBuffer(D3DLOCK_READONLY, (VOID**)&lpbVb);
Mesh->LockIndexBuffer ( D3DLOCK_READONLY, (VOID**)&lpIB);
Mesh->GetIndexBuffer( &lpIndexBuffer );
lpIndexBuffer->GetDesc( &ibdesc );
if(ibdesc.Format == D3DFMT_INDEX32)
{
//MessageBox(NULL,"ibdesc.Format 32","",0);
numIndices = ibdesc.Size / sizeof(DWORD);
}
else
{
//MessageBox(NULL,"ibdesc.Format 16","",0);
numIndices = ibdesc.Size / sizeof(WORD);
}
 
DWORD numBytesPerVertex = Mesh->GetNumBytesPerVertex();
 
 
for(int i=0; i<numIndices; i += 3 )
{
idxVbVert0 = ((WORD*)lpIB)[ i ];
idxVbVert1 = ((WORD*)lpIB)[ i+1 ];
idxVbVert2 = ((WORD*)lpIB)[ i+2 ];
 
D3DXVECTOR3 v0 = *(D3DXVECTOR3*) &lpbVb[ idxVbVert0 * numBytesPerVertex ];
   D3DXVECTOR3 v1 = *(D3DXVECTOR3*) &lpbVb[ idxVbVert1 * numBytesPerVertex ];
D3DXVECTOR3 v2 = *(D3DXVECTOR3*) &lpbVb[ idxVbVert2 * numBytesPerVertex ];
 
}
 
Mesh->UnlockVertexBuffer();
Mesh->UnlockVertexBuffer();
}
[/code]
0

Share this post


Link to post
Share on other sites

Thanks for the response! I made some changes based on your code example. Unfortunately same results :(. 

0

Share this post


Link to post
Share on other sites

Ok so if anyone is interested in how this all worked out. I took the time to remove the duplicate vertices in the .X cube file so that there are now only 8 vertices, which is correct for an indexed cube. Vertex and index values are now listed below. The index buffer now returns different values, still not the ones listed in the file though. I took a look at the vertex buffer in the application and the vertices have been reordered, also for some reason GetNumVertices() returns 16 instead of eight. It's obvious that each of the 8 vertices has been duplicated in the buffer, I have no idea why. Anyway I matched the vertices in the vertex buffer to the vertices in the file. Then I matched the returned indices to those values, and the 12 faces in the index buffer are indeed correct and identical to the 12 faces in the .X file. So bottom line is that D3DXLoadHierarchyFromX() is doing some things to both the vertex and index buffers behind the scenes, but adding an additional 8 vertices certainly does not seem like an optimization. Oh well at least I know the indices are right now, I'm going to try to do a vertex cache mesh->OptimizeInPlace and see if that removes the duplicate vertices. If that doesn't work I guess I'll just add some code to remove the duplicate vertices. 

 

 

 Mesh { //Cube_001 Mesh
      8;
      -1.000000; 1.000000;-1.000000;,
       1.000000; 1.000000;-1.000000;,
      -1.000000;-0.999999;-1.000000;,
       1.000000;-1.000000;-1.000000;,
      -1.000000; 1.000000; 1.000000;,
       1.000000; 1.000000; 1.000000;,
      -1.000000;-0.999999; 1.000000;,
       1.000000;-1.000000; 1.000000;;
      12;
      3;0;1;2;,
      3;2;1;3;,
      3;5;4;6;,
      3;6;7;5;,
      3;1;5;3;,
      3;3;5;7;,
      3;4;0;2;,
      3;6;0;2;,
      3;0;4;1;,
      3;4;5;1;,
      3;2;3;6;,
      3;6;3;7;;
0

Share this post


Link to post
Share on other sites

Ok last bit of info. I thought the vertex buffer contained duplicate vertices. My .X file lists only 8 vertices but the application says 16 vertices. I wasn't bothering to look at the indexed normal list contained in the .X file. D3DXLoadHierarchyFromX is creating vertices with the same position, but with different normals, so they are not duplicates and everything seems to be working as intended. :)

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