DirectXTK12 VS The-Forge

DirectXTK 12 (includes SimpleMath and other goodies)

Looks like that's from https://github.com/microsoft/DirectXTK12, an open-source DX12 tool kit

For example: https://github.com/microsoft/DirectXTK12

or https://github.com/microsoft/DirectXTK12/wiki/Getting-Started

DirectX Tool Kit for DirectX 12

Oh, I forgot a few major ones:

https://github.com/ConfettiFX/The-Forge was used in No Man's Sky, Hades and Starfield.

https://github.com/jrouwe/JoltPhysics is the physics engine in Horizon Forbidden West.

To my understanding, every source I've read says that this should cause issues, but in practice it doesn't. What gives? Did I miss something? Here are multiple examples using the latter approach.

This is a toy project that I've been working on for the past few months. Essentially, I've rewritten all the rendering code for the engine using BGFX. This means that all the fixed function OpenGL 1.2 code has been removed from the engine. BGFX supports OpenGL 3.3 and DirectX11, but there are still some rendering artifacts with DirectX11, so the engine still uses OpenGL when running on Windows. I've been considering switching to The Forge (https://github.com/ConfettiFX/The-Forge) if I want to have more control over the rendering pipeline. However, this is a complex topic with significant implications for the codebase. I've already done the hard work of eliminating clumsy abstractions in the engine and simplifying the render pipeline, so it's just a matter of deciding what direction I want to take.

The-Forge might fit:

So, I'm not sure if it is widely known, that Starfield is going to be running on a lot of "The Forge." The creators of The Forge says it was added to Creation Kit in 2019. This will open a LOT of new systems for Bethesda games.