Sound bug , not fixed

[DarkCheetah]

crap..... i guess these sound bug will be lurking at random persons

off-topic: the graphics and animations where smoothly , like a 40 fps screen , and even tough it crashes after a while, but a totaly crash (Blue Screen)

[t3ddy]

i think i'm one of the unluckies with sound problems
i'm using linux and i have the Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

when i disable sounds, the game is smooth (FPS=60), but with sound enabled the game is slow (FPS=1-9)
i've also taken a look to system's logs, but i've not found anything strange

[Thyranim]

crap..... i guess these sound bug will be lurking at random persons

off-topic: the graphics and animations where smoothly , like a 40 fps screen , and even tough it crashes after a while, but a totaly crash (Blue Screen)

when it crashes as bluescreen there is also another fault, outside of warzone
do you know which bluescreen it was? which error-code (0x000000ED for example) ?

[DarkCheetah]

when it crashes as bluescreen there is also another fault, outside of warzone
do you know which bluescreen it was? which error-code (0x000000ED for example) ?

not what i know off, btw the blue screen acoured with WorldOfWarcraft , not Warone, read the comment again ^^

[Thyranim]

ah ... eh ... oh .... :rolleyes:

my fault ^^

[ThomasCarstein]

Ok guys, this is probably more serious than i thought: i just ran the tutorial and fast game a few times and they all crashed after a certain amount of time, around 5 min or so... i hope it is just on my machine though, but i think i should make a bug ticket anyway

I also tried running the game paused and it happens all the same, after 5 or even less minutes it just went poof O_O - but i only tried it in tutorial and fast game, i will let you know how it behaved in campaign mode :-S

EDIT: yep, confirmed. The game crashed 3x and once reported some problem with the openAL library, but due to my stupidity and too fast clicking I didn't save the report :rolleyes: Anyway, i'll take a look for some diagnostic tools around here and try to make a more detailed bug report, also a ticket - since for me it's impossible to play anymore

EDIT 2: I just tried it out with the latest nightly build as is written in the "how to debug" section; the result is the same, but the game simply shuts down without any windows error report, also no error report in stderr file

[DarkCheetah]

i only have the sound crackle problem , but crashing? not here

[Kaldera]

Some crackles are part of the music. (because of radiation?)
Match with external ogg-player.
Latest openal for windows is from 2007 (also the included), so maybe newest hardware isn't supported (and vista).
Interference with soundcard drivers are also possible. Try newest or only the internal windows drivers. Disable all soundcard-related programs (mixer etc...).
Try setting windows to only 2 speakers (not surround).
Crashing needn't be a fault of openal, in windows errorlogs usually all open drivers are mentioned. Try to get some errorlogs from management console.

[DarkCheetah]

i'v a laptop , my speakers are inside my laptop , and i have only warzone running , the music is disabled to

[ThomasCarstein]

UPDATE: everyone please disregard the ticket i made in TRAC. I solved my problem: I needed to exchange the normal 1.1 openAL driver with the 1.7 openAL soft driver - problem is solved. Sorry for the hasty report, next time I'll try to be more patient :-S

[lav_coyote25]

that may be able to assist others in tracking down their problem... thanks for being impatient and solving the problem.

[Buginator]

Just a few notes, warzone *can't* cause a BSOD.

BSODs are from crappy drivers. (Be it audio or video)

If you have sound issues, then you can update the drivers, try a newer openAL driver from Creative, or try openAL soft from here: http://kcat.strangesoft.net/openal.html#download
Download the binary, and stick the .dll at the same location as warzone2100.exe is! Do *NOT* replace the one in your system32/64 directory, unless you know for sure it works OK.

[ThomasCarstein]

If you have sound issues, then you can update the drivers, try a newer openAL driver from Creative, or try openAL soft from here: http://kcat.strangesoft.net/openal.html#download
Download the binary, and stick the .dll at the same location as warzone2100.exe is! Do *NOT* replace the one in your system32/64 directory, unless you know for sure it works OK.

True. Only one more notice from me - the reason why it took me over 5 days to figure out what the heck is wrong with openAL (this is for anyone with similar problems) :rolleyes:
The funny thing was this: I firstly installed the openAL 1.1 with the Warzone 2100 Instalation, and it worked. After I put my discs in to my new machine, the new hardware configuration did not recognize the openAL32 .dll driver even though it was installed and reported no errors.
When sound didn't work, i uninstalled openAL and it reported: "some files were in use - a reboot is needed". Now the problem was, that even after the reboot (since the driver was not recognized as installed by the computer) the same driver did not get deleted out of system32 and at the reinstalling of openAL the installer simply generated an "openAL.NEW" file in system 32, which it then deleted again at uninstall
So, how did I solve this exactly? Step 1: I uninstaled openAL 1.1 and manually deleted the openAL32.dll and openAL.NEW from my system 32 folder (do not mess with drivers if you are not sure what you are doing - you could cause serious problems by doing these things). Step 2: I downloaded the openAL soft 1.7 driver (found on the link in Buginator's post), extracted the package and READ THE README (always an urgent thing to do), where it says, that if we are sure we don't want to use the normal driver, we can just rename the 1.7 .dll found in the package to "openAL32.dll" and put it in the same location it was before - system32. Step 3: I made a backup and then i replaced the driver.

Result: every game that requires openAL to run, works flawlessly now (I had also major problems with running "FreeSpace 2 open source" becouse of this - working now as well). BUT I recommend that you try the method written by Buginator first - and if it works, leave it like it is; I may be just lucky that it worked my way, who knows

EDIT: I found out just yesterday, that IF you uninstall openAL 1.1 and just put the new 1.7 driver in to system32 like I mentioned above, chances are that the system will delete it on computer restart, but once I have installed openAL 1.1 and after that exchanged the driver, all is ok.

[DarkCheetah]

in the RC1 version of v 2.2 this crackle sounds are a bit less damaging to the ear(lol) the crackles are a bit downsized besides the v 213

so.... the problem lies some where in the sofware

[Buginator]

in the RC1 version of v 2.2 this crackle sounds are a bit less damaging to the ear(lol) the crackles are a bit downsized besides the v 213

so.... the problem lies some where in the sofware

Hate to break it to you, but no changes at all have been done to the sound code since the release of 2.1

If it crackles, then it is the drivers--unless you have used up all the sources, then yeah, it is in the code. But normally, it should sound good.