Greetings to all and Merry Xmas and Happy New Year. I simply have a small sweet problem and is hoping anyone of you might know the answer.When I start my game, the FS9 loads up and this problem only occurs when I try to use my B717 plane. Funny tho on the Sun Valley it does not show up but on Air Canada or others it does.I can still use the plane but do not notice anything missing as of sound overall that I can think of.Here is what I get:DEBUGDirect Sound Object Not Found. After hitting OK several times, then this comes up:SOUNDLIB-ERRORSound file not foundWhat is going on here and does anybody know where this problem is coming from in the game. Like I said as to the other aircraft in my game I have no problem with this kind of message showing up.Would appreciate if someone can help.ThanksChanRak

Hi ChanRak,I haven't seen this particular error message before so I don't know what will fix it for sure. Have you tried putting this in your FS9.cfg file?[OldModules]FSSound.dll=1The look in the main FS9 folder for fssound.dll to be sure it is located there.Hope this helps,Merry CHRISTmas! Happy New Year!Earl

Hi, and thanks for responding.To answer your question, yes it is in the FS9 CFG file. I checked that out. Hmmm, better yet let me remove this FSSound.dll from the modules folder and also in the FS9 CFG and see if this cures this hiccup.Will let you know.ChanRak

Nope that was not the problem, in fact it killed a lot of gauges since now I suspect the FSSound is dll 126.I also checked this out with the panel shop I have here.ChanRak

For the benfit of those who may not yet know how to alias and re alias sounds. Panels are aliased in the same fashion.Go to the sound folder of the plane giving the problem. Open the sound folder. If there is nothing there but a sound.cfg file, open the sound.cfg file with notepad. "//" out the alias reference that is already there and type in: alias=b717_200Deltasoundlike this:(fltsim) //NOTE: these are square brackets around "fltsim"//alias=b717_200soundalias=b737_400soundOR...If the plane giving the trouble has the sound files in it's sound folder along with a sound.cfg file:right click on the sound.cfg and a menu will open. Choose the "rename" option.left click on the right side of the blue highlighted "sound.cfg" name. This will give you a cursor to the right of the name. Type in orig and then click in the open area of the folder where there are no other files. This will bring up a dialog box asking if you really want to change the file name. say yes.Next. Right click in the open area again to open the options menu. Choose "New" and then Text Document. When it opens, the words "New Text Document" will be highlighted in blue. Type sound.cfg which will rename the new file to "sound.cfg". Then, open the sound.cfg file you just made and copy and paste the example I gave you above into it and save the file. If this fixes the problem, you are missing a wav file, or there is something wrong with the sound.cfg, etc.There are several new sound files available for the 717. You might try a different one...Hope this helps.Earl

Hi Earl;Again thanks for your response. Here is an update. I re-installed the FSsound.dll back into the modules folder, and updated again that fs9 cfg under old modules.I did change the sound of which I noticed it had B 717 sound wave files in it, and I put in a sound cfg alias to my fsconv which I know works well with the others. So something in that sound file must be corrupt or was missing something.So I reloaded this again, and it looks like we are getting somewhere. I still get that Debug error and sound file missing but not as much. Just about 2 or 3 clicks now. Before I had a bunch. So that tells me I have made some amount of progress.I am still stumped as to where the rest of this problem lies at. At least that sound file took care of it a lot, so I think it has to go to the panel where those gauges are in that is being used like you mention in your reply. Somewhere along that panel cfg says it needs this file or something of which I suspect but cannot figure it out. I suppose a trial and error thing might work by putting // in front of each gauge in Windows 0, and it just might point me to the culprit. But before I begin to do that, what do you advise and suggest.ThanksChanRak

I don't think a sound problem will be solved by working on the panel... but, ok. Alias another panel to your 717. Use the 737-400 default panel. If the problem goes away, you know it is in the panel.What version 717 plane are you using? What ver panel? You are not trying to use a 200 file in 2004 are you? I know most will work in an ok fashion but there are problems sometimes. Maybe this is one of those times.Have a great night.Earl

Hi Earl;Again and wow you responded quickly. But I got good news for you. I did find the culprits involved and yes it is in the Panel believe it or not. Here they are as follows://gauge07=pg.mdxx.ee.firepanel, 700,341,160,86 ;CD/PG//gauge08=pg.md87.hh.firetest!firetest, 771,393,20,19 ;CD/PG//gauge41=GEARTLK3, 0,0,1,1 ;FPDA/PGI did go one by one in sets starting from Windows 0 and some others that I thought caused this problem. But no, so I went back to the Windows 0 and eliminated the gauges that you would least suspect that would be causing my problem. What you see above is the three culprits that gave me the headaches.So I guess for those who encounter this problem in the future here is my suggestion. Check your sound file folder first and replace it with a known good one for your test as Mr. Earl said here, and if that problem does not go away, then by all means check out that panel CFG and its gauges and do a process of elimination by doing sets of 5 by putting this---> // in front of the gauge line as you see above here and don't forget to save the changes to your CFG. While your in the game itself first choose another aircraft and let that load and then go back again to your problem aircraft. Once that problem gets eliminated you will not see this Debug or Sound file not found anymore.When that happens double check it again unload and reload the same aircraft to be sure. Now once this is done put back the others into your panel by deleting that >// in sets of 5 to be certain your culprit does not come back up again. If it is not showing up anymore you found the holy grail of your headache and problem. After that up to you to decide if it is worth keeping or simply keep those // right there and continue to play your game.As to Earl, he is one good person and most certainly helped me get pointed in the right direction when he tipped me off concerning it being sound files and possibly the panel itself on that aircraft.I really would like to know what Geartlk3 is all about???????? I suspect it means Gear ? lock 3. Not sure. Hate those abbreviations cause they can sure throw you to left field.Keep up the good work folksChanRak

Good morning ChanRak,Thanks for the kind words. I am very glad you found your problems. I would not have guessed a sound error would have come from the panel. That stoke of genious was your own :). I learned from you, sir!I use Ken Mitchell's B717 panel. It does not have any of the problem guages you listed. You may want to check it out, 717km_p.zip at Flightsim.com.Good job ChanRak!Merry Christmas everyone!