Bound by Flame not an old game. Why you need wrapper for this game? 2010> games difficult to work with DirectX. New games often use complex difficult schemes for shaders and code, this games have thousands shaders and new shader model versions. In most cases these games do not work correctly with wrappers (if they are real wrappers, not just links).

ngovandang wrote on 2024-02-19, 13:58:

Bound by Flame crashes right after intro, any idea?

This thread is for regressive bugs only. What's the previous dgvoodoo version that works with that game?

It crashes for me too, ingame. But only with D3D12. It's because of a GPU crash. There is another game with which I'm aware of this problem (The Witcher). I know why it is but never fixed.
Anyway, I'll do it.

mitradis wrote on 2024-02-19, 19:23:

Bound by Flame not an old game. Why you need wrapper for this game? 2010> games difficult to work with DirectX. New games often use complex difficult schemes for shaders and code, this games have thousands shaders and new shader model versions. In most cases these games do not work correctly with wrappers (if they are real wrappers, not just links).

Wrappers also should work with new games, at least dgVoodoo should. Whether they needed in place of native D3D9 is another question (with new games they are not).
In dgVoodoo D3D 9.0c is completely supported along with basic D3D9Ex. It also no matter how many shaders a game has, and how complicated the internal logic in them, the transition of them is just done.

There are some things however that make the "experience" worse compared to a native D3D9 implementation:

• Generated (large) shader binaries can take more time in the driver to get translated to native gpu bytecode (lagging gameplay) but it should only affect the first run, until the shader cache is not built for them by the OS
• The wrapper consumes more memory than native D3D9, so you might need to patch the executable for 4GB (anyway, I'm planning some improvements to decrease it, we'll see)
• The reserved stack size can be too low in nowdays terms and the D3D11/12 GPU driver might not fit into it (dgVoodoo itself should) causing crash, see Call of Duty 2

Last time I tried dgVoodoo with Tomb Raider 2013 (with the DX9 renderer) which is also a "new enough" game. It just worked and eventually played through the whole game.