I'm currently working with D3D 11 and if I understood it correctly, D3D 10 had a mesh interface built in to it which was removed in 11.

If this is correct, why was the mesh interface removed? It seems like a useful interface to have.

  • \$\begingroup\$ Is this causing a problem for you? Are you asking for work-arounds? Things like that are sometimes removed to not limit developers into a specific way of doing things. \$\endgroup\$ – MichaelHouse Jun 23 '13 at 16:08
  • \$\begingroup\$ @Byte56 No not really, just takes a bit more time :) Im only asking out of curriosity. I can see how i could limit developers, however 1. if they feelt it limited their potentiall, then they could just make one themself ? 2. I meen there is a limit to how much you can perfect a function to run as fast as possible. I feel this is a good reason to have on standar function for it, to perfect it. Now when you make your own function, sure you can design it to work how you want it to work, but you start att square one everytime, from a performace point of view . \$\endgroup\$ – Fredrik Boston Westman Jun 23 '13 at 16:16
  • 2
    \$\begingroup\$ Frederik, we can only speculate. Maybe this utilitiy stuff was in the way of deeper optimizations, or maybe they just wanted to simplify the interface. Who knows. Voting to close, as in its current form this will only poll speculation and there is no problem to solve here, which is the actual intention of the site. Please check the FAQ for details on what kind of questions are encouraged on the site. \$\endgroup\$ – Maik Semder Jun 23 '13 at 16:31
  • \$\begingroup\$ @MaikSemder with all due respect, if i had know it was only gonna give speculative anwsers it wouldnt have been a question. For all I know it was something major wrong with it and could have sent me down a bad path using the directX 10 interface. Do you think that is something unworthy of knowing for a newbie ? \$\endgroup\$ – Fredrik Boston Westman Jun 23 '13 at 16:37
  • \$\begingroup\$ @FredrikBostonWestman - I agree that it's probably worth knowing and that there may be useful information in an answer to it, that's not in dispute, and despite that the relevant point is: even given that it may be worth knowing, is it appropriate for this site? \$\endgroup\$ – Maximus Minimus Jun 23 '13 at 16:44

D3D10 core didn't have a mesh class; you're probably thinking of ID3DX10Mesh, which is actually part of the D3DX API. D3DX itself was wholly deprecated with Windows 8. The relevant math bits were moved into another library. The higher-level utility interfaces, like mesh, were not ported.

The API was removed because it was a continuation of the evolving focus of D3D and its related APIs: to become narrower in scope, more representative of only the underlying graphics hardware. APIs like the mesh interface were an attempt both to provide something much higher level than the GPU actually does, and to be a one-size-fits-all solution (which is often a lowest-common-denominator solution).

Furthermore, by divorcing the graphics library from the utility library, it's easier for Microsoft to utilize separate (and more appropriate) release vehicles for both, and easier for the components to be updated and versioned independently.

All of the above factors contributed significantly to the decision to deprecate the functionality (which had been underway since the 9-to-10 transition, when the built-in functionality to load meshes from .x files vanished).

You should look at the DirectXTK for potential replacements to interfaces you miss from D3DX.

| improve this answer | |

Not the answer you're looking for? Browse other questions tagged or ask your own question.