by A nub is In Ur Forum on Tue Oct 06, 2009 10:13 pm
Most likely the crash is just preventing the value change from saving. Start JKA, turn EAX off immediately, and close JKA normally as soon as that's done; as long as it doesn't crash on you first, EAX should save as "off". Also bear in mind that this value is stored separately in jampconfig.cfg for every mod you have, so to ensure it doesn't crop up again, you need to turn it off in each mod and verify that it did in fact turn off; you can do it through the GUI for each (tedious), or you can go through all your copies of jampconfig.cfg, look for "s_UseOpenAL" and make sure the relevant line is 'seta s_UseOpenAL "0"' in each.
Once you have EAX off, you shouldn't crash, and the Korriban sound glitch should be much less frequent; I haven't had the EAX problem myself, but the sound glitch crops up perhaps 1 in 5 Korribans; with EAX off, "snd_restart" or toggling quality between high and low twice fixes it for the entire round consistantly in my experience (usually the torches just go silent when 'fixed', but that's fine by me.)
Just a guess off the top of my head, but I suspect the cause is that there are just too damn many torches making noise in the 2nd O spawn on Korriban; that's always where the problem starts up in my experience, can anyone else confirm/deny that? I believe the sound components are serverside entities, so it's possible I could 'fix' this (but not the EAX part of it) in a Korriban server patch by removing some or all of the torch noise in that particular room. Anyone with ideas/comments on this, by all means speak up; I suspect practically everyone would rather have the torches permanently silent than deal with having to snd_restart mid-game at all, assuming it fixes it, correct? If enough people want this solution, I'll research it sometime and see if it'll work.