
Originally Posted by
Xandros
This brought me back here, and I just have to mention two things, then I'm off again. First of all, that workaround was posted in this very thread multiple times years ago. Secondly, it isn't a solution, it has exactly the same effect as if you go into UT's settings and turn off hardware acceleration because you're essentially breaking OpenAL by doing it. Some people seemed to think you still got hardware acceleration by doing this and swore blimey that they could hear the difference but, they really couldn't. Seriously, the two files are different and perform different functions, renaming one file as the other is breaking those functions, not magically fixing a relatively obscure bug, hence the metric fukton of errors that come up in the log when it is done.
The actual fix was always to use beta drivers provided by Creative that allowed you to turn off the X-Ram usage, because the bug is in actuality when a sound file gets stored in X-Ram, however, that file apparently either gets corrupted or misnamed somewhere or along the line or simply doesn't get put in there when it is supposed to and the result is UT3 eventually tries to load it, fails, and instead of saying "oh well that didn't work I'll carry on as normal" it has a spaz attack and crashes.
Bookmarks