• 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

How hard will it be to convert an MD5 Loader in DirectX 11 to DirectX 9

3 posts in this topic

Ive found this tutorial online




I am not ready for DirectX 11 yet, i want to load this in DirectX 9 instead

What steps do i need to take to adjust to DirectX 9,i am not bothing about shaders at this moment in time,i am just interested to get an animated model thats not .x loaded in my DirectX 9 window


(dx11)            (dx9)




is that correct?

Edited by Anddos

Share this post

Link to post
Share on other sites

The bulk of the loader code is all CPU-side, and the D3DX/XM data types are actually not API-specific; they're all from CPU-side math libraries.

  • You can use D3DX data types in D3D11 if you have the headers and libs available for them.
  • You can use XM data types in D3D9 if you have the headers and libs available for them.
  • You can even just use raw float arrays instead, if you're so inclined (and in some cases that may be preferable as you won't have a dependency that may affect code portability).

The only conversion that should be needed is that relating to actual D3D objects, which will be those who's data type begins with "ID3D11" or "IDirect3D9" (or "LPDIRECT3D9" if using those).  So for a model format that's just going to be vertex and index buffers.


Thanks for the input


I am unsure how to convert this correctly to d3d9


// create an index buffer interface called i_buffer
    g_pD3DDevice->CreateIndexBuffer(sizeof(WORD) * subset.numTriangles * 3,
VOID* pVoid;    // a void pointer
// lock i_buffer and load the indices into it
    i_buffer->Lock(0, 0, (void**)&pVoid, 0);
    memcpy(pVoid, subset.indices[0], sizeof(indices));
The parameters are different it seems
// create a vertex buffer interface called v_buffer
// create a vertex buffer interface called v_buffer
    g_pD3DDevice->CreateVertexBuffer(sizeof( Vertex ) * subset.vertices.size(),
                               CUSTOMFVF, //what do i put for this flag?
    VOID* pVoid;    // a void pointer
    // lock v_buffer and load the vertices into it
    v_buffer->Lock(0, 0, (void**)&pVoid, 0);
    memcpy(pVoid, subset.vertBuff, sizeof(Vertex));
Edited by Anddos

Share this post

Link to post
Share on other sites

For a CreateVertexBuffer call in D3D9 the FVF should normally be 0.


There is only one case where specifying an FVF is needed and that's:

  • You're creating a device with software vertex processing, and
  • This vertex buffer is the destination buffer for a ProcessVertices call.

If this doesn't apply (and if you don't know what ProcessVertices does or don't even know the call exists then it doesn't apply) you set FVF to 0 and the buffer will create OK and can be used for any vertex format.  There are no disadvantages to setting FVF to 0 in normal usage.


For reference, ProcessVertices was an optimization with software T&L that allowed you to kick off vertex processing on another thread, or to have vertex processing occur once only for multi-pass algorithms.  You run ProcessVertices and vertex processing copies from the source streams to a single destination stream, running transform and lighting on them (or the vertex shader if one is active) as it goes, and which you then use as input to a normal draw call.  There's no reason to use it otherwise and ProcessVertices is not available with a hardware T&L device.


So this is a special kind of vertex buffer known as an "FVF vertex buffer" which is only used in very limited and very specific scenarios.  Otherwise you just set FVF to 0 and don't worry about it.


Unfortunately a lot of D3D9 tutorial material doesn't take this distinction into account (which gives the impression that the authors of the tutorials don't really know what they're doing - also unfortunate) so you sometimes see it used.  Just be aware that outside of the ProcessVertices call, 0 is a valid value for the FVF parameter and you can use it, no matter what you see in tutorials.

Edited by mhagain

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 YixunLiu
      I have a surface mesh and I want to use a cone to cut a hole on the surface mesh.
      Anybody know a fast method to calculate the intersected boundary of these two geometries?
    • By hiya83
      Hi, I tried searching for this but either I failed or couldn't find anything. I know there's D11/D12 interop and there are extensions for GL/D11 (though not very efficient). I was wondering if there's any Vulkan/D11 or Vulkan/D12 interop?
    • By lonewolff
      Hi Guys,
      I am just wondering if it is possible to acquire the address of the backbuffer if an API (based on DX11) only exposes the 'device' and 'context' pointers?
      Any advice would be greatly appreciated
    • By MarcusAseth
      bool InitDirect3D::Init() { if (!D3DApp::Init()) { return false; } //Additional Initialization //Disable Alt+Enter Fullscreen Toggle shortkey IDXGIFactory* factory; CreateDXGIFactory(__uuidof(IDXGIFactory), reinterpret_cast<void**>(&factory)); factory->MakeWindowAssociation(mhWindow, DXGI_MWA_NO_WINDOW_CHANGES); factory->Release(); return true; }  
      As stated on the title and displayed on the code above, regardless of it Alt+Enter still takes effect...
      I recall something from the book during the swapChain creation, where in order to create it one has to use the same factory used to create the ID3D11Device, therefore I tested and indeed using that same factory indeed it work.
      How is that one particular factory related to my window and how come the MakeWindowAssociation won't take effect with a newly created factory?
      Also what's even the point of being able to create this Factories if they won't work,?(except from that one associated with the ID3D11Device) 
    • By ProfL
      Can anyone recommend a wrapper for Direct3D 11 that is similarly simple to use as SFML? I don't need all the image formats etc. BUT I want a simple way to open a window, allocate a texture, buffer, shader.
  • Popular Now