http://bugs.winehq.org/show_bug.cgi?id=20177
--- Comment #19 from Chris chris.kcat@gmail.com 2009-10-03 23:02:22 --- (In reply to comment #18)
I tried to run UT3 again - it hung as expected. This time I ran an strace on the pid after I launched it. This is what I got.
futex(0xb63e7bd8, FUTEX_WAIT, 16040, NULL
I guess the FUTEX_WAKE never comes.
Hmm. That's oddly reminiscent of a problem with 1.8 using PulseAudio. Can you provide a longer trace?
As a side note, shouldn't software OpenAL work? I'm going through all this because I'm trying to get Hardware OpenAL working due to Software OpenAL vanishing. I'm I off base with that claim? I think Michael B's post confirms it, no?
You won't get any hardware OpenAL under Linux. The Windows drivers can't access any Creative hardware you may have, and Linux's OpenAL is software based. That said, though, using Linux's OpenAL does provide some benefits, such as greater configurability, surround sound mixing, more effects, and fewer intermediary steps (App->Linux OpenAL->Hardware, vs App->Win32 OpenAL->Wine DSound->Hardware).
Additionally, OpenAL doesn't actually specify whether you're getting hardware or not (just like OpenGL likes to hide that). I would imagine using Hardware OpenAL makes it try to open "Generic Hardware" or some other known hardware device name. Current GIT of Wine will accept the "Generic Hardware" device name, and try to open whatever device is available. Windows would fall back similarly.