No SOUND!!! Red Baron II 3D. HEEEELLLLP!!!!!

Red Baron 3d by Dynamix. After install sound works. . . After game restart. . . No sound!!!!! I love this game and this stinks. There has to be a reason for this issue. The install program runs a system test and plays a Digital Wave file.

Windows Games 5469 This topic was started by ,



data/avatar/default/avatar28.webp

3 Posts
Location -
Joined 2003-03-12
Red Baron 3d by Dynamix. After install sound works... After game restart... No sound!!!!!
 
I love this game and this stinks.
 
 
 
There has to be a reason for this issue. The install program runs a system test and plays a Digital Wave file .wav (and then asks you if you hear it. The game works fine for the first run...... Then NO SOUND!!
 
(After reinstall without restarting XP Sound returns)
 
Odd aint it. (I assume it has somthing to do with the system test)
 
I have an Athalon 1.3
Nvidia Gforce 4 TI
Soundblaster Audigy TI
And XP Home Edition - Full version (not OEM)
 
 
Help needed and thanks to all who answer back!

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic



data/avatar/default/avatar28.webp

3 Posts
Location -
Joined 2003-03-12
OP
The answer to my question was found on this URL.
 
http://www.wings-of-valor.org/
 
Look under the Documents Link.
 
Its called: XP Workarounds (by Brooks Martin)
 
Here is what he said... And I quote:
 
Workarounds for XP/USB joystick/missing sound.
Collected by Brooks Martin, March 10, 2002
bkmart@hotmail.com
The Problem:
 
Red Baron and Windows XP don’t get along with regards to sound. As XP
users with USB joysticks soon discover, the program works fine the very
first time they play. Subsequent play is marred by the complete absence of sound. Players with old-style, gameport joysticks, don’t usually have this problem. Unfortunately, USB joysticks are the only ones commonly found in stores now.
 
This problem appears to be related to Red Baron mis-analyzing the
computer’s hardware. Specifically, RB seems to think there is a conflict
between the USB joystick and the soundcard. For subsequent play events,
RB disables sound; perhaps thinking that of the two, users would rather have an operable joystick. Since both joystick and sound worked fine the first time, clearly the RB-discerned conflict is imaginary, though real enough to RB, alas.
 
Workarounds:
I call these workarounds, rather than solutions, since they involve more-orless inconvenient actions by the player. You can have both sound and USB joysticks. You just have to decide which of the following workarounds is less onerous to you.
 
Several people in the RB community are responsible for developing these
workarounds, including McHaggis, AATrouble4you, Charles de Thielt, and
myself. I am sure there are others that helped, and I will gladly add your
names to this list if you will notify me.
 
Hardware workaround:
Unplug the USB cord of your joystick before starting RB. Plug back in once
you reach the RB main menu. You may hear a chime sound from your
computer, signifying it has recognized the “new hardware,” namely, your
joystick. Make your selection from main menu and go fly, with both joystick and sound. If your joystick has an electric cord also (Microsoft Force Feedback, for instance), you needn’t unplug that cord.
Advantage: You retain your preferences data files (see below).
 
Disadvantages: Inconvenient location of USB port. Wear and tear on USB
connector.
 
Software workaround #1:
Delete “rbprefs.dat” from your “Sierra/RedBaron3D/Data” subdirectory
before each play of RB in single player mode.
Delete “mpprefs.dat” from your “Sierra/RedBaron3D/Data/Multi”
subdirectory before each play in multiplayer mode.
This also works for the older, superpatched, RedBaronII game, just
substitute RedBaronII for the RedBaron3D name when searching for the .dat files.
 
Advantage: Saves USB connectors.
 
Disadvantages: You will have to re-select all your preferences each time you play. You have to erase .dat file each time.
 
Software workaround #2:
After deleting the .dat files as above, make new, empty file folders in the
same subdirectories with the .dat names. In the /Data subdirectory, make a folder named “rbprefs.dat” (the .dat is required). For multiplay, in the
/Multi folder make a new folder named “mpprefs.dat”.
Again, this works for the older RBII version, per above.
 
Advantage: Only have to do this once.
 
Disadvantage: Re-entering preferences each time you play.
 
 
 
---------------------------------------------------------------------
 
 
Could this forum update the Uncompatable with XP status with this info?
 
Thanks!
 
MR2spyder


data/avatar/default/avatar24.webp

1 Posts
Location -
Joined 2004-05-15
I had the same problem but took a slightly different approach. I created a DOS Batch file to replace the corrupted file (rbprefs.dat) with a fresh file each time the program is loaded.
 
I also have a force feedback joystick, but the force feedback no longer works. Which data file keeps this information?
 
Thanks,
Mark