[Bug 43153] Gothic 1.0 from Steam freezes in new game on phrase "I'm Diego "

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=43153

--- Comment #14 from Richard Thier <u9vata at gmail.com> ---
I still had this problem nevertheless whatever I was doing... then I have found
a working workaround to share with you here guys!!!

These are the things I was doing:
- Tried all the stuff said above (nothing worked)
- Tried to add d3d9.dll from SwiftShader 3.0 (not worked - unused by game?)
- Tried to add d3d8.dll from SwiftShader 3.0 (used a manually build version)
- Also in the meantime have found "Gothic I systempack" here: 

https://forum.worldofplayers.de/forum/threads/1340357-Release-Gothic-%C2%BD-%C2%97-SystemPack-%28ENG-DEU%29

With swift DLLs in place and the playerpack 1.08, playerpack 2.7, then system
pack 1.7 installed I can run the game flawlessly on my asus laptop which was
mid-tier machine in 2007. No lag, no freeze, nothing. I am in the beginning of
the game, but already seems like everything is working!

I am not sure if only the systempack is needed or SwiftShader is needed too. I
will try to remove the swiftshader DLLs (I still have both of them) to see if
everything works without them too.

In case other people also want to have DirectX 8 version of the SwiftShader
DLLs you can find them on this discussion by someone hosting it on mediafire:

https://www.vogons.org/viewtopic.php?f=9&t=36412&start=120

^^These are handy anyways (I use them to play Nexus: Jupiter incident too)

In order to use these DLLs, I changed winecfg to make d3d9 and d3d8 APIs always
native if existing - and fallback only to the build in ones. This way was
good-enough for me, but you can set a specific setup just for games that really
need it.

I will come back with news to tell if the systempack is enough or both hackz
are needed, but I have a feeling the syspack can be enough as it had some fix
on a resource garbage collection background thread according to its release
docs that "might" freeze the game by completely starving other threads. Maybe
this was the core issue...

-- 
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.