"Sound-file ungueltig"?

W

wsmwsm

Charter Member
After installing Mauro Giacomazzi BF109E3, I receive this error message which, I think, means sound file void or null. The game also freezes. After hitting escape a few times, the plane will fly (and with sound), but this is rather annoying.

I've tried switching out the sound file and installing others, but no luck. Anyone have an idea how to correct this?
 
Yeppers, that means the sound file is invalid.

Can you post the sound cfg as a text on here so we can see it?
It should be bigger than 1kb. If not, it is the aliased to one of the stock aircraft.
 
Hi wsmwsm,
It's a gauge problem.

Some gauges require sound files, you have the gauge installed but not the accompanying sound file.

Cheers :ernae:
Lindsay
 
The problem is a gauge in the panel.cfg. I can't recall the name of the gauge off hand....but if you post the text from the panel.cfg file I will now it when I see it. OBIO
 
The sounds the brakes make seem to come to mind since I had the same problem a long time ago but I may be wrong. It's been a long time ago.
 
I may have found your problem. When you downloaded your plane it had a sound folder with it and inside that sound folder is a wave sound file titled "Brakes Sound" I believe that file should go in your main CFS2 sound folder and I think that should solve your problem. I hope I'm right, like I said it has been awhile but it makes sense to me. Good Luck!
 
All the gauge files you installed for this plane included a gauge file titled "HGHB_BRAKE_SOUND" and that wave sound file I was talking about has to be installed in your main sound folder or else you will get that error message. Hope I'm right.
 
KWB you are right. In addition to Brakes_Sound.wav I think there is also a Click.wav that can cause the ungueltig error, they're usually in the same download of any panel that uses the HGHB brake sound gauge.
 
SOUND FILES

Recently while incapacitated from surgery , I downloaded just about all the sound file that I could find. I then made a cental folder for them in my CFS2 folder outside the theaters ( hat tip to Obio here on a long ago post). I then made sound.cfgs ( by engine) for each one to be just dropped into the appropiate aircraft sound file and they work great. If I can get a zipper going would anyone be interested?
 
I did see the additional sound file. I assume it should be installed in the aircraft sound file. I'll move it to the CFS2 file and see what happens.

Addendum: I moved it, but the error remains. Here is the Panel CFG:

// This Panel.cfg file created by CfgEdit
// Built Saturday, July 20, 2002 at 22:14 Build:16969
[Window Titles]
Window00=%window_title_00%
Window01=%window_title_01%
Window02=%window_title_02%
Window03=%window_title_03%

[VIEWS]
view_forward_WINDOWS=MAIN_PANEL,THROTTLE_PANEL,COLLECTIVE_PANEL,COMPASS_PANEL
VIEW_FORWARD_ZOOM=0.5
VIEW_FORWARD_EYE=0.0
VIEW_FORWARD_DIR=2.1, 0.0, 0.0
VIEW_REAR_RIGHT_WINDOWS=32
VIEW_REAR_RIGHT_ZOOM=0.5
VIEW_REAR_RIGHT_EYE=0.1
VIEW_REAR_RIGHT_DIR=0.0, 0.0, 150.0
VIEW_REAR_WINDOWS=33
VIEW_REAR_ZOOM=0.5
VIEW_REAR_EYE=-0.2
VIEW_REAR_DIR=0.0, 0.0, 180.0
VIEW_REAR_LEFT_WINDOWS=34
VIEW_REAR_LEFT_ZOOM=0.5
VIEW_REAR_LEFT_EYE=-0.1
VIEW_REAR_LEFT_DIR=0.0, 0.0, 210.0

[Window00]
file=BF109F2_640.bmp
file_1024=BF109F2.bmp
size_mm=640,480
window_size_ratio=1.00
position=4
visible=1
ident=MAIN_PANEL
sizeable=1
render_3d_window=1
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
gauge00=BF109e!Airspeed, 122,414,60,66
gauge01=BF109e!Altimeter, 124,347,60,66
gauge02=BF109e!Boost_Pressure, 321,345,56,55
gauge03=BF109e!Clock, 370,286,42,41
gauge04=BF109e!Heading_Indicator, 191,337,66,76
gauge05=BF109e!Oil_Pressure, 325,412,50,51
gauge06=BF109e!Tachometer, 259,344,62,61
gauge07=bf109e!Attitude, 187,411,70,70
gauge08=fw190a!Vertical_Speed, 259,412,62,61
gauge09=jwb_divebrake!divebrake, 455,368,20,19
gauge10=a6m2_zero!Icon_Map, 377,332,19,18
gauge11=bf109e!Magneto, 89,386,30,90
gauge12=bf109e!Starter, 48,448,30,26
gauge13=bf109e!Flaps, 452,388,32,93
gauge14=MAPE_Prop_Feather!Feather Prop 1, 98, 367 ,20,19
gauge15=rww2-stall-lt, 159,326,20
gauge16=a6m2_zero!Master_Switch, 62,422,15,24
gauge17=HGHB_BRAKE_SOUND, 597,439,40,41
gauge18=f4u1a_corsair!Icon_Engine_Controls, 399,333,18,17
gauge19=concorde!Fuel-Panel-Display-Toggle, 423,333,18,17
gauge20=f4u1a_corsair!Fuel_Selector, 496,432,50
gauge21=JWB.analog_canv, 244,278,12,49
gauge22=JWB.analog_gunv, 260,278,12,49
gauge23=concorde!Compass-Display-Toggle, 127,326,18,17
gauge24=bf109e!Oil_Temperature, 385,356,58,57
gauge25=bf109e!Engine_Temperature, 387,414,54
gauge26=bf109e!Fuel, 545,432,50,50
[Window01]
size_mm=95,132
window_size_ratio=1.00
position=6
visible=0
ident=THROTTLE_PANEL
sizeable=1
window_size= 0.148, 0.276
window_pos= 0.000, 0.726
gauge00=bf109e!thrust_controls, 8,9,72,111
[Window02]
size_mm=280,480
window_size_ratio=1.00
position=7
visible=0
ident=COMPASS_PANEL
window_size= 0.360, 0.800
window_pos= 0.640, 0.200
gauge00=concorde!ADF, 5,378,85,84
gauge01=concorde!Radio-Adf, 91,378,175,86
gauge02=concorde!Radio-Comm1, 89,289,174,82
gauge03=concorde!Radio-Transponder, 88,211,172,70
gauge04=concorde!Radio-Altimeter, 4,287,84,83
gauge05=VW_Autopilot, 12,160,64,119
gauge06=concorde!VOR, 89,118,74,83
gauge07=concorde!Radio-Naviagtion-1, 169,119,87,83
gauge08=b29autopilot, 11,7,253,65
gauge09=mooney_bravo!Fuel Flow, 90,74,94,43
gauge10=mooney_bravo!Clock, 189,76,65,38
gauge11=mooney_bravo!Nav GPS Switch, 14,79,21,37
[Window03]
file=714PopUp.BMP
size_mm=260,70
position=6
visible=0
ident=COLLECTIVE_PANEL
sizeable=1
window_size= 0.303, 0.100
window_pos= 0.340, 0.900
gauge00=jwb_dtank!DumpTank, 4,3,56,62
gauge01=jwb_trim!Trim, 103,4,66,62
gauge02=JWB!cg_pct, 63,35,34,16
gauge03=concorde!Pitch-Trim, 176,2,24,64
gauge04=concorde!Yaw-Trim, 204,44,54,23
gauge05=concorde!Roll-Trim, 213,3,34,36
[Vcockpit01]
Background_color=0,0,0
size_mm=512,512
position=7
visible=1
ident=Vcockpit01
pixel_size=512,512
texture=$main
gauge00=BF109e!Airspeed, 41,329,75,82
gauge01=BF109e!Altimeter, 40,245,76,83
gauge02=BF109e!Boost_Pressure, 303,191,86,85
gauge03=BF109e!Clock, 310,115,49,48
gauge04=BF109e!Heading_Indicator, 119,191,94,108
gauge05=BF109e!Oil_Pressure, 324,324,70
gauge06=BF109e!Tachometer, 212,191,92,91
gauge07=bf109e!Attitude, 129,313,102,101
gauge08=fw190a!Vertical_Speed, 233,324,92,91
gauge09=jwb_divebrake!divebrake, 416,232,27,26
gauge10=a6m2_zero!Icon_Map, 354,166,19,18
gauge11=bf109e!Magneto, 10,279,30,90
gauge12=bf109e!Starter, 4,372,37,31
gauge13=bf109e!Flaps, 467,309,30,93
gauge14=MAPE_Prop_Feather!Feather Prop 1, 71, 222 ,20,19
gauge15=HGHB_BRAKE_SOUND, 234,453,56,57
gauge16=rww2-stall-lt, 156,110,20,19
gauge17=a6m2_zero!Master_Switch, 401,196,25,34
gauge18=JWB.analog_gunv, 215,110,12,49
gauge19=JWB.analog_canv, 200,110,12,49
gauge20=bf109e!Oil_Temperature, 401,267,58,57
gauge21=bf109e!Engine_Temperature, 401,326,57
gauge22=concorde!Fuel-Panel-Display-Toggle, 402,166,20
gauge23=concorde!Compass-Display-Toggle, 91,196,20,20
gauge24=f4u1a_corsair!Icon_Engine_Controls, 377,166,20
[Vcockpit02]
Background_color=0,0,0
size_mm=256,512
position=6
visible=0
ident=Vcockpit02
pixel_size=256,512
texture=$left
gauge00=bf109e!Gear, 68,110,92,182
gauge01=MAPE_cowl_flap!Cowl Flap 1, 12,52,40,150
gauge02=fsd_he111.pitot, 57,52,170,56
gauge03=PARKBREMSE, 12,294,147,137
[Vcockpit03]
Background_color=0,0,0
size_mm=256,512
position=8
visible=0
ident=Vcockpit03
pixel_size=256,512
texture=$right
gauge00=f4u1a_corsair!Fuel_Selector, -2,41,80,160
gauge01=bf109e!Fuel, 76,41,80,160
gauge02=bf109e!Fuel_Warning, 154,41,35,70
gauge03=VW_Autopilot, 75,199,80,160

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=5165
[Strings]
"window_title_00"=Main Panel
"window_title_01"=Engine Controls
"window_title_02"=ADF Instruments
"window_title_03"=Fuel CG Trims

It's aliased to the George, which is there.
 
That should do it!

Fibber,
Yes, would be. I've had a mind to do the same, but if you have already then great! When you changed the association 'by engine' I take it by some macro, allowing you to do it en-mass? Would be interested in in that as well.

Cheers

Shessi
 
Here's an update. Problem solved. I had misdirected the brakes sound wave file. It's now where it belongs and the error message has vanished.

Thanks for all of the help.

How would anyone know this, however, by simply looking at the aircraft? No mention of this in the readmes.
 
Good news MSN, glad to hear it solved your problem. I agree with you that without any mention in the readme's how would anyone know.It is not the normal install that most of us are use to. I made the exact same error you did and only got it corrected by trial and error.
 
Yes, Fibber, I am very interested, because I always wanted to do the same but I shrunk from the amount of work.

Cheers

Achim
 
Sound Files

To make a central sound folder, just make a folder (name it something like "Engines") in your C://Program Files/Microsoft Games folder (same folder that CFS 2 is usually in. Then organize it how you want. I have two main sub folders in it named "Jet Engines" and "Piston Engines" with the numerous individual engine folders in one of these two main sub folders within the central engine folder.

Now you can alias your various planes (from any or multiple CFS 2 installations) directly to the central sound folder of you choice via the plane's sound.cfg file.

Here is an example of an alias from an Me 109G that will access the central engine folder:

[fltsim]
alias=\..\..\Engines\Piston Engines\DB 605

By the way, this will work for CFS 1, FS 7, 8 and 9 planes too.

You can also do this with commonly used 2d panels too, although I've never done it.
 
kwb737 said:
Good news WSM, glad to hear it solved your problem. I agree with you that without any mention in the readme's how would anyone know.It is not the normal install that most of us are use to. I made the exact same error you did and only got it corrected by trial and error.
Click to expand...
 
achim27619 said:
Yes, Fibber, I am very interested, because I always wanted to do the same but I shrunk from the amount of work.

Cheers

Achim
Click to expand...

Hi Achim,

Bearcat246 also suggested a while ago to centralize our sound and panel files by creating two main sound and panel subfolders, then, inside of them, subfolders for each sound pack and panel.

As mentioned above by Jagdflieger too, after that, every aircraft can have aliased panels and soundfiles.

It makes it easier managing our hangars since aircrafts can be moved, copied or deleted around and their panel.cfg + sound.cfg files always point in the same direction.

Not only, according to Bearcat, the computer itself will run better with all of those files located in one place. That also includes creating external centralised folders for our scenery libraries, instead of clogging up CFS2 root \scenedb legacy folder.

I must say that, with this kind of file organisation, I never encountered lots of CFS2 running bugs often mentioned by several members in these pages.

Cheers!
KH :ernae:
 
Jagdflieger said:
To make a central sound folder, just make a folder (name it something like "Engines") in your C://Program Files/Microsoft Games folder (same folder that CFS 2 is usually in. Then organize it how you want. I have two main sub folders in it named "Jet Engines" and "Piston Engines" with the numerous individual engine folders in one of these two main sub folders within the central engine folder.

Now you can alias your various planes (from any or multiple CFS 2 installations) directly to the central sound folder of you choice via the plane's sound.cfg file.

Here is an example of an alias from an Me 109G that will access the central engine folder:

[fltsim]
alias=\..\..\Engines\Piston Engines\DB 605

By the way, this will work for CFS 1, FS 7, 8 and 9 planes too.

You can also do this with commonly used 2d panels too, although I've never done it.
Click to expand...

I've tried this method to no avail. I have created an ENGINES file within CFS2 and placed Lawdog's DB 601 sounds there. But I have been unable to direct the aircraft sound CFG there and, therefore, the plane does not appear in the game.

Here is what the aircraft sound CFG looks like:

[fltsim]
alias=C:\Program Files\Microsoft Games\Combat Flight Simulator 2\ENGINES\DB 601

Can anyone advise if I need to correct the path in some way.
 
Suggestions...

Here's how I have mine set up:

E:\CFS2 Sounds\Aircraft Sounds\Allied\...... << This is the name of the individual sound file

The rest of the files are installed as shown in the capture shot.

A Typical sound.cfg file reads like THIS:

[fltsim]
alias=e:\CFS2 Sounds\Aircraft Sounds\Axis\He177 Dual


Hope this helps !
SC
:kilroy:
 
You must log in or register to reply here.
Back
Top