DIRECT X 9 CODE
DIRECT X 9 PC

I also support PC, UWP, and Xbox One for DX11/DX12, but obviously DX9 would be limited to PC only.The Microsoft DirectX End-User Runtime provides updates to 9.0c and previous versions of DirectX, the core Windows technology that drives high-speed multimedia and games on the PC. It's also quite a lot of work keeping up two versions of the library, much less three including documentation, input & audio, etc. DX12 is 'pro API' and DX11 is the 'beginner API', so there's really not a lot of reason to go back to DX9. I just don't understand the value of doing it at this point. It really wouldn't be that difficult to make a DirectX Tool Kit for DX 9 with DDSTextureLoader, SpriteFont, SpriteBatch, WICTextureLoader, ScreenGrab, SimpleMath, VertexTypes, GeometricPrimitive, and/or Model. Keep in mind that there's no support for the DX 9 Developer Runtime on anything newer than Windows 7, so it's not a great experience for a beginner in any case. With Direct3D 9 you can use the fixed-function pipeline so you don't actually need BasicEffect, although you can implement it since the original XNA Game Studio shaders I used were Shader Model 2. With Direct3D 9 you can just use DrawPrimitiveUP so you don't need PrimitiveBatch.

DIRECT X 9 CODE

While this DDSTextureLoader that includes DX9 support is pretty old at this point, you can pretty easily take the current DDSTextureLoader & WICTextureLoader code from DirectX Tool Kit for DX11 and create a version that supports DX9.

The more recent D3DCompiler supports Shader Model 2.0 & 3.0, but the DLL itself does not work on Windows XP. It's difficult to stop using the legacy DirectX SDK for DX9 development, although you do have a few things to look at.ДirectXMath is reasonably agnostic, and SimpleMath is as well except for the automatic viewport conversion operator which you could easily do without. There's basically no reason at all to use DX10, as DX11 is supported on the same platforms and has more hardware support.

Otherwise DX11 is supported on everything newer. What's the technical motivation to support DX9? The only really solid reason to continue to use DX9 is to support Windows XP systems. I'm aware a last resort is to make a Zombie DirectX SDK, as your blog explains, but I'd like to avoid it if possible. I've seen there's a DirectXTex library that sounds like it should help, but I couldn't find any documentation on equivalent methods to dx3d9.h

I'd also be interested in hearing your perspective/knowledge on implementing Fonts, Texture loading ( jpg/png/dds) and surface copying in a way that's compatible with DX9. Is this something you would consider doing officially? I can move things around so that including SimpleMath provides both halves and the DX9 compatible bit is in a new file for compatibility. With a local copy I have separated out Viewports into its own file, which seems to be the only dependency on DX11/12 allowing me to use the SimpleMath extensions with DX9. The main issue I'm currently trying to solve is unifying similar code so I was hoping I could use the SimpleMath Extensions, but they have a preprocessor error preventing compilation without inclusion of DX11 or 12. DXTK seems like a great resource, and I'd like to use it in a project I am contributing to that supports DirectX 9-11 (and in future 12).

Direct x 9