GCC 6.3.0 certainly does appear to be full of problems, the initial MingW release of it produced executables that crashed on Windows XP but shouldn't, that was subsequently fixed. However, I blame the Direct3D threading for one reason - DOSBox also does it (via SDL) and I have the same kind of problems (crashes and freezes) there, in fact in DOSBox it's worse, it freezes as soon as I switch to Direct3D.
SarahWalker wrote:You've screwed up the merged from mainline
At first I did but later I just replaced my merge attempt with a direct copy+paste, which while it alleviated the problems, they apparently still are there.
SarahWalker wrote:You have bad D3D libraries
I'm on Windows 10, specifically Creator Update (the one released this year), and Direct3D seems to be exceptionally bad on this (my window-patched Dicrect3D.dll in my GTA SA directory used to work perfectly in the Anniversary Update of Windows 10, but has been glitching badly ever since I updated to the Creator Update), though I also received reports about it from other users of AMD graphics cards, and I have a Radeon as well, so there seems to be a correlation.
SarahWalker"}You have the worst graphics drivers in the world[/quote]
Per the above, yes, it does seem the AMD Radeon drivers do Direct3D 9 badly.
[quote="SarahWalker wrote:None of which I can do anything about.
You could write an OpenGL or Direct3D 10 (or 11) renderer, that should work better. Well, I personally use DirectDraw because it's faster on my card, but OpenGL might be on par with DirectDraw. On DOSBox, I just use OpenGL and it works like a charm.