[Bug 29744] STALKER-SoC/CoP hangs at splash screen due to OpenAL32

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=29744

--- Comment #13 from Plüss Roland <roland at rptd.ch> 2012-01-31 14:26:47 CST ---
(In reply to comment #12)
> Wine does not open any devices with built-in OpenAL. All calls are forwarded to
> system OpenAL library. You have broken 32-bit library installed. And you
> verified that it belonged to a different then 64-bit version.
> 
> Wine's openal is a thin wrapper around system's opanal library. It does not
> replace it. As I said earlier, test your setup with 32-bit Linux program.
I hate to repeat myself. I said that I tested (quote)"32bit and 64bit
binaries". So the 32bit OpenAL is "perfectly" fine and running with 32bit games
or apps. Only wine seems to have a problem both with these games as well as the
OpenAL SDK samples as I just tested. I don't know what the problem is but since
everything else (32bit) works with the very same openal 32bit library but wine
doesn't I just have a hard time believing every other game/application has a
lucky time running and wine is the correct working guy in the rink.

Anything with which further tests can be made to narrow down where wine messes
up? If the layer is thin then there has to be a way to debug where the problem
comes from. Maybe the thin layer has a bug somewhere and doesn't forward
properly? Can it be wine loads a different library than the one (the system
one) it has been linked against? In my last post I showed that there are
special wine openal libraries around. Are they just adaptors or why are there
wine versions of the openal library if it is just a wrapper? Just trying to
narrow down the problem as only this is going to fix wine not claiming
everything else is faulty.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.