Reply 20 of 27, by Ben Gunn
wrote:The thing is, I can't fix it. Last time I debugged it, it revealed that the (game) renderer releases (destroys) some of its text […]
The thing is, I can't fix it. Last time I debugged it, it revealed that the (game) renderer releases (destroys) some of its textures before they get rendered.
Isn't it a bug in DXGL instead? I mean, DXGL may not release the texture objects when they should be released and so it works only by chance?BTW, unfortunately I don't have an AMD card at all by now. But I see that AMD texturing problem is a growing issue.
I'd need some little app (a scene demo maybe) that it can be reproduced with, and send it to the AMD bugreport system.
Hi Dege,
I tested your dgvoodoo2 wrappers to play Outlaws on my Windows 10 64-bit machine.
Version 2.54 works very good and Outlaw is playable without big problems (only the waterfall texture glitch).
Version 2.55.x of dgvoodoo2 however just sucks, because Outlaws just shows a white screen instead of the 3D world.
Why is 2.55.x so terrible when it comes to playing Outlaws?
What did you change compared to 2.54?
Is the source code of dgvoodoo2 available or for your eyes only?
Kind Regards,
Ben Gunn