http://bugs.winehq.org/show_bug.cgi?id=19017 abrasive <winehq@tiger.wah.net.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq@tiger.wah.net.au --- Comment #28 from abrasive <winehq@tiger.wah.net.au> --- I've found two bugs in this game - the first causing crashes and the second causing black (unlit) geometry. I've patched both of these and now it seems to run fine (on wine-proton 10.0.3). I've posted the patch here: https://codeberg.org/abrasive/IveGotSomeBalls-patch The crash bug is that it does ID3DTexture2::Release on all its textures before doing IDirect3DDevice3::SetTexture. I'm guessing this used to work because the object memory managed to not get reused long enough in win9x? It is reported not to work, or to work patchily, on Win7 and not at all on Win10. The unlit geometry is because it doesn't initialise D3DLIGHT.dvRange when setting up its one light; it's allocated on the stack so it gets random fluff. I was mighty confused when I got the crash bug fixed, it worked, and then it suddenly didn't work - what had changed was that I'd inadvertently removed WINEDEBUG=+ddraw and one of those logging leaf functions had been politely setting the range to a massive number. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.