The future of d3d driver

[fskqj]

The latest d3d driver of irrlicht is d3d9, which is abandoned by many cases day after day, mingw/msys2 seems dropped d3d9 support, I can not build irrlicht with d3d9 on mingw/msys2 successfully, and d3d11 on shader-pipeline branch is not maintained. Keep continuing multi-render backend is very important, do not be tied to one api: opengl, that's not good. what's the plan to save d3d driver on irrlicht ?

[Noiecity]

You can compile it... but with older versions of mingw, typically one that uses GCC version 4.x...

And if you wanted to compile it in more modern versions, you will have problems to produce .a file compatible with this version ... you can still use Visual Studio... another option is to use IrrlichtBAW, but I don't know, I usually prefer d3d9 anyway...

But if you want to solve it manually, you will likely encounter dozens of compilation errors due to conflicts between the Windows headers in your modern MinGW and the old headers in the DirectX SDK. You would have to manually edit these headers to resolve redefinitions and other conflicts(I don't see it feasible honestly, assuming it would work properly).

[fskqj]

You can compile it... but with older versions of mingw, typically one that uses GCC version 4.x...

And if you wanted to compile it in more modern versions, you will have problems to produce .a file compatible with this version ... you can still use Visual Studio... another option is to use IrrlichtBAW, but I don't know, I usually prefer d3d9 anyway...

But if you want to solve it manually, you will likely encounter dozens of compilation errors due to conflicts between the Windows headers in your modern MinGW and the old headers in the DirectX SDK. You would have to manually edit these headers to resolve redefinitions and other conflicts(I don't see it feasible honestly, assuming it would work properly).

OK. I will not dig and use old mingw and old visual studio. The irrlichtbaw removed q3 loader and irrlicht gui, I think I need them. Thanks.