Is there any reason you're running Baldur's Gate II under dgVoodoo other than curiosity? You won't get OpenGL effects that way (well, theoretically it's possible with some OpenGL>Glide wrapper, but I doubt you got that setup).

To get ReShade to run. Otherwise this happens: https://reshade.me/forum/troubleshooting/4551 … nhanced-edition

Is there anything I could do to help fix this issue? I'd really like to see this resolved.

This game is one of the old DDraw ones that draws (its own cursor in this case) directly to the screen which is a pain to emulate with the expected appearance and good performance.

Direct screen drawing can basically be implemented in two ways.
Currently dgVoodoo implements only one of them which make the mouse flicker in this game (or other screen elements in other games).
For curiosity I whipped up the implementation of the other way and the mouse flickering was gone.

I'm about to do some DirectDraw development to address known issues like this but I don't know how to expose them to the user.
As for this one in general, it cannot be detected at runtime what way to go, so should I introduce a new option for that?

This is exciting news, Dege! Yes, I believe many would love to see an option for the alternative DDraw implementation if it meant solving issues like that. Thank you 😀

I'm in favor of this option too !

I think I have quite a few games that might benefit from it. I will have to test it a lot (Dark Earth slowing down on an Intel HD4000 with dgVoodoo comes to mind).

I forgot to mention that this game now should work flashing-free with option DirectXExt\PrimarySurfaceBatchedUpdate enabled.