FAZ beta testing still going on?
Testing is actively on going but we have not called for a 'large' test yet.
As Pook said, hopefully next Wed we will have a release candidate ready and that will need to be run through at least one large (well at least medium size) game (20 vs 20). To get that many people we'll advertise the time and day.
However, for the most part, the beta test server is up and running and you can check the sticky in the FAZ forum to get the latest client and info.
I'd like to see at least a 3 versus 3 game every Wed, if only for an hour. I usually try and log in at 9 (EST) as do a few others like FreeBeer, SaiSoma, Cortex, etc (sorry if I missed your callsign and you regularly drop by the beta).
As Pook said, hopefully next Wed we will have a release candidate ready and that will need to be run through at least one large (well at least medium size) game (20 vs 20). To get that many people we'll advertise the time and day.
However, for the most part, the beta test server is up and running and you can check the sticky in the FAZ forum to get the latest client and info.
I'd like to see at least a 3 versus 3 game every Wed, if only for an hour. I usually try and log in at 9 (EST) as do a few others like FreeBeer, SaiSoma, Cortex, etc (sorry if I missed your callsign and you regularly drop by the beta).

DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]
Great -- 9 am or pm EST on Wednesdays?
Also, the wav files should be put into the regular allegiance artwork file? WIll that affect functionality in regular servers?
TYin advnace for your reply (I think) /huh.gif" style="vertical-align:middle" emoid=":huh:" border="0" alt="huh.gif" />
Also, the wav files should be put into the regular allegiance artwork file? WIll that affect functionality in regular servers?
TYin advnace for your reply (I think) /huh.gif" style="vertical-align:middle" emoid=":huh:" border="0" alt="huh.gif" />

Robin: "Gosh, Batman, this camel grass juice is great."
Batman: "Beware of strong stimulants, Robin."
9pm EDT.
Overwrite the .wavs already in your Allegiance\artwork folder - it will not affect regular Allegiance.
Right now, Allegiance reads the wav files and converts the stereo ones to mono and then pipes them through the right speakers to achieve a 3D sound effect.
The wavs you download are mono versions to replace the stereo ones in your artwork. Since the existing stereo sounds are never played as stereo anyways, you won't notice any difference.
--TE
Overwrite the .wavs already in your Allegiance\artwork folder - it will not affect regular Allegiance.
Right now, Allegiance reads the wav files and converts the stereo ones to mono and then pipes them through the right speakers to achieve a 3D sound effect.
The wavs you download are mono versions to replace the stereo ones in your artwork. Since the existing stereo sounds are never played as stereo anyways, you won't notice any difference.
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.
Right now with DirectSound4, Allegiance quietly merges the left/right channels of stereo .wavs into a single mono channel before positioning the sound in the 3D landscape.
Unfortunately DirectSound8 does not do this - when it encounters a stereo .wav it simply ignores it. This is why there are missing TF minigun sounds, as well as a few others. Replacing them fixes it.
This issue is separate from the sound problem where sounds are heard but slowly start to stutter out until they drop out entirely for the rest of the session.
The beta client that was released today increases the streamed sound buffer size in the hopes that this may resolve the problem. Although no concrete reasons have been found for the problem (which is why it hasn't yet been solved), there are indications that it may be related to improper buffer sizes for streaming sounds.
That's what we're testing today.
--TE
Unfortunately DirectSound8 does not do this - when it encounters a stereo .wav it simply ignores it. This is why there are missing TF minigun sounds, as well as a few others. Replacing them fixes it.
This issue is separate from the sound problem where sounds are heard but slowly start to stutter out until they drop out entirely for the rest of the session.
The beta client that was released today increases the streamed sound buffer size in the hopes that this may resolve the problem. Although no concrete reasons have been found for the problem (which is why it hasn't yet been solved), there are indications that it may be related to improper buffer sizes for streaming sounds.
That's what we're testing today.
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.
To add to what Tiger said, the number of effected files total 15 (including the TF ones) and are in the sticky in the first post in the FAZ public forum called FAZ_MonoSounds.zipPook wrote:QUOTE (Pook @ Jul 12 2006, 05:23 PM) ... I'm going to have to push down a whole bunch of wav files over AU and piss off a lot of people.
Yes they will need to be pushed via AU, but the update will be small and it won't effect the current clients so it can be pushed before the release of the new client.
To add more to what Tiger said, we were testing with modified sounds as while dx8 should ignore the stereo sounds we are not 100% that they were not causing problems so at a cost of 15 files it was a worth a shot, and you get the sounds back to boot.
Last edited by Dogbones on Wed Jul 12, 2006 9:54 pm, edited 1 time in total.

DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]
