• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            天行健 君子當自強而不息

            D3D Animation Basis(2)

            Extending D3DXMESHCONTAINER

            Whereas you might be used to using the ID3DXMesh object to contain your mesh data, you may have found
            it a pain to store the mesh's material and effects data separately. Not only that, but what about using the other
            D3DX mesh objects, such as ID3DXPMesh and ID3DXSkinMesh? Why not just create a single mesh
            object that represents all mesh types and contains all material data along with it?

            In fact, there is such an object−it's called D3DXMESHCONTAINER! The D3DXMESHCONTAINER object
            stores a pointer to your mesh data (regardless of the mesh type used) and all material and effects data. It also
            contains pointers to your mesh's adjacency buffer and skinned mesh data object. And as if that wasn't enough,
            the D3DXMESHCONTAINER contains pointers to form a linked list of mesh objects.

            typedef struct D3DXMESHCONTAINER {
            LPSTR Name;
            D3DXMESHDATA MeshData;
            LPD3DXMATERIAL pMaterials;
            LPD3DXEFFECTINSTANCE pEffects;
            DWORD NumMaterials;
            DWORD * pAdjacency;
            LPD3DXSKININFO pSkinInfo;
            D3DXMESHCONTAINER * pNextMeshContainer;
            } D3DXMESHCONTAINER, *LPD3DXMESHCONTAINER;

            What could I possibly do to extend the usefulness of the already nifty D3DXMESHCONTAINER, you ask?
            Well, for one thing, D3DXMESHCONTAINER has no default constructor or destructor. Also, textures data is
            missing−there's only a buffer that contains the names of the textures to use for the mesh. Last, there's no
            support for storing skinned mesh animation data.

            No problem, because extending the D3DXMESHCONTAINER is simple! The new version, which I call
            D3DXMESHCONTAINER_EX, adds a total of four data objects and three functions. The data objects include
            an array of texture objects, a skinned mesh object (to store an animated skinned mesh), and two arrays of
            matrix objects.

            Here's how I defined the D3DXMESHCONTAINER_EX object, as well as declaring the four variables I
            mentioned:

            //-------------------------------------------------------------------------------------------
            // Declare an extended version of D3DXMESHCONTAINER that contains a constructor and destructor
            // as well as an array of textures, a mesh object that contains the generated skin mesh, and
            // matrices that map to the frame hierarchy's and for updating bones.
            //-------------------------------------------------------------------------------------------
            struct D3DXMESHCONTAINER_EX : public D3DXMESHCONTAINER
            {
              IDirect3DTexture9** textures;
              ID3DXMesh* skin_mesh;

              D3DXMATRIX** frame_matrices;
              D3DXMATRIX* bone_matrices;

             

            The textures array of pointers contains the texture objects used to render the mesh. I build the
            textures array up by first loading a mesh and then querying the texture buffer
            (D3DXMESHCONTAINER::pMaterials) for the file names of the textures to use.

            As for skin_mesh, you only use it when you are using a skinned mesh  You see, when loading a skinned mesh, the actual mesh data is stored in D3DXMESHCONTAINER::MeshData::pMesh. The only problem is, you need another mesh container to store the skinned mesh as it is animated. That is the purpose of skin_mesh.

            Last, you'll find frame_matrices and bone_matrices. Not to drag it out, but these are also used for
            skinned meshes. Just so it makes sense at this point, a skinned mesh animates by attaching the vertices of the mesh to an underlying hierarchy of bones. As the bones move, so do the vertices. ppFrameMatrices and pBoneMatrices are used to map the vertices to
            the bones.

            Aside from the variables in D3DXMESHCONTAINER_EX, there are also a few functions. The first two are the
            constructor and destructor:

            D3DXMESHCONTAINER_EX()
            {
              ZeroMemory(this, sizeof(*this));
            }

            ~D3DXMESHCONTAINER_EX()
            {
            if(textures && NumMaterials)
            {
              for(DWORD i = 0; i < NumMaterials; i++)
                release_com(textures[i]);
            }

            delete[] textures; textures = NULL;
            NumMaterials = 0;

            delete[] Name; Name = NULL;
            delete[] pMaterials; pMaterials = NULL;
            delete pEffects; pEffects = NULL;

            delete[] pAdjacency; pAdjacency = NULL;
            delete[] frame_matrices; frame_matrices = NULL;
            delete[] bone_matrices; bone_matrices = NULL;

            release_com(MeshData.pMesh);
            release_com(pSkinInfo);
            release_com(skin_mesh);

            delete pNextMeshContainer; pNextMeshContainer = NULL;
            }

            The constructor and destructor have the task of initializing the data to a known state and releasing the data
            used by the object, respectively.  Basically, release_com is a macro that safely releases a COM interface and sets the interface pointer to NULL.

            The third function in D3DXMESHCONTAINER_EX is find, which lets you scan the linked list of meshes for
            a specifically named mesh, much like D3DXFRAME_EX::find. A quick string compare is used to check the
            names, and a recursive call to find is used to scan the entire linked list.

            D3DXMESHCONTAINER_EX* find(const char* mesh_name)
            {
            // return this mesh instance if name matched
            if(Name && mesh_name && !strcmp(mesh_name, Name))
              return this;

            // scan next in list
            if(pNextMeshContainer)
              return ((D3DXMESHCONTAINER_EX*) pNextMeshContainer)->find(mesh_name);

            return NULL; // no found
            }

            And that does it for the helper objects! The D3DXFRAME_EX and D3DXMESHCONTAINER_EX objects are
            extremely helpful when it comes to dealing with Direct3D; as such, you should spend as much time as you
            can getting used to these two objects. I think you'll find them very useful in your own projects.

            Aside from the helper objects, there are a number of helper functions that I'd like to introduce to you, which
            should help you alleviate the mundane tasks common to most Direct3D−related projects.


            posted on 2008-04-14 09:55 lovedday 閱讀(528) 評論(0)  編輯 收藏 引用

            公告

            導航

            統計

            常用鏈接

            隨筆分類(178)

            3D游戲編程相關鏈接

            搜索

            最新評論

            午夜精品久久久久久久| 色欲av伊人久久大香线蕉影院| 人妻无码αv中文字幕久久| 无码伊人66久久大杳蕉网站谷歌 | 亚洲色欲久久久久综合网 | 国产精品9999久久久久| 久久精品国产精品青草app| 久久婷婷五月综合97色直播| 国产亚洲美女精品久久久2020| 国产精品久久久亚洲| 久久久青草青青国产亚洲免观 | 免费观看成人久久网免费观看| 久久精品中文字幕一区| 亚洲AV日韩AV永久无码久久| 嫩草影院久久99| 久久永久免费人妻精品下载| 午夜精品久久久久9999高清| 国产精品对白刺激久久久| 久久久黄色大片| 久久www免费人成看国产片| 亚洲精品午夜国产VA久久成人| 国产成人精品久久亚洲高清不卡 | 亚洲va久久久噜噜噜久久男同| 成人精品一区二区久久久| 99国产欧美精品久久久蜜芽| 久久夜色精品国产噜噜噜亚洲AV| 性做久久久久久久久| 久久久黄片| 97久久精品人人澡人人爽| 久久这里只精品国产99热| 精品久久久久久久无码| 久久亚洲AV成人无码电影| 久久久亚洲裙底偷窥综合| 热久久国产欧美一区二区精品| 一级做a爰片久久毛片16| 91精品国产9l久久久久| 国产成人久久精品激情| 久久久无码人妻精品无码| 久久精品亚洲一区二区三区浴池| 色8久久人人97超碰香蕉987| 久久亚洲AV成人无码电影|