http://bugs.winehq.org/show_bug.cgi?id=28448
David Finch david@mytsoftware.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |david@mytsoftware.com
--- Comment #14 from David Finch david@mytsoftware.com 2011-10-04 00:03:01 CDT --- I thought it was a bug when I didn't see the audio driver selection options anymore, and it's not selecting the correct driver on its own (on 10.04), and was selecting nothing instead (correct choice would have been alsa). The test button somehow worked (despite it reporting that no driver was selected), but in Fallout: New Vegas and Oblivion audio was gone after the title screen, apart from occasional crackling. I hadn't tested other games.
With audio broken, I switched back to 1.3.24 which had worked, but somehow .29 had corrupted my wine prefix (never figured out in what way) so New Vegas would refuse to run (oddly claiming it wasn't installed) and I had to restore a full backup. But that'd be another bug and I doubt backwards compatibility with itself is high up in the priorities, apart from difficulty it causes with regression testing.
If the winecfg audio tab is reporting none incorrectly, is there another way to see which driver it's using? Or another way to set it (the registry key didn't seem to work).