• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning

Cleaning up the "Goose"

Steve,

that Beaver looks most excellent, it deserves to be liberated from it's dev status! :jump: I love the bump mapping and detailed texturing, as I already do on the Redux Goose. Excellent work, thanks!

Cheers,
Mark

Hey Mark

Thanks for the kind words :)

Now that Shade is out there im hoping to get back into doing some HD reduxing/repainting,i also have a Redux of the extra 300's external bumping/detailing pretty much done just gotta find time to get around to getting my crayons out again

Cheers
steve
 
Ehehe, yeah, I love suing people for nothing.:icon_lol:
The original Goose has a dead wav link in the sound.cfg that's fixed with this downloadable update. Forgot about that, sorry.

So, I adjust each Wav? There's a bunch....
 
So, I adjust each Wav? There's a bunch....

TeaSea, as napamule correctly suggests, the Goose can be fixed by just dropping in the corrected sound.cfg.
There are other third party planes that have this hanging sound due to inproperly formatted wav sounds, and yes, these need to be resaved.
Goldwave can do that as a batch job.
You would open all wav files from a sound folder and just run a batch job on it.
And no, I'm not affiliated with Goldwave in any way. :icon_lol:


http://www.goldwave.com/
The site makes it appear as if it was payware but it's shareware really.
It has a trial version that never seems to expire. It'll just remind you to buy it from time to time.
 
Mathias,
You said: '..as napamule correctly suggests, the Goose can be fixed by just dropping in the corrected sound.cfg.' Sorry but I never did say any such thing. I have no way of knowing what you did to it, and thus I can't vouch that it 'works' as a fix.

Looking at your 'fix' sound.cfg and the Goose sound.cfg I can't SEE as there is any difference AT ALL. Is it 'hidden'? Is the 'dead link' still there?

I realize there have been numerous methods used (since FSX came out) and lots of talk in forums. But no one ever pointed out the EXACT 'error'. For some reason some think that pressing 'Q' twice will fix things (I disagree-but that's only my opinion).

It has been suggested that one use the DC-3 cfg formating to format the Goose sound.cfg in order to fix it. Haven't tried it as I am not 100% on SDK when it comes to sound. But it sounds like one could just use the DC-3 sound and be done with it.
Chuck B
Napamule
 
Okay, fair enough guys....tell you what....

I'll try all of them sometime this weekend, and I'll let you know how it comes out.

I did have Goldwave, and yes, there is a batch option. I just had to look for it.

Thanks for the help, I'll let you know what I end up with.:guinness:
 
Reading all this ............ I just checked mine. For some reason all the sound files are 32 bit. I think I copied all of them from FS9. Don't remember why I did this, but I don't have that problem.
 
Ok guys, that'll teach me to blather off of faded memories.:mixedsmi:
Just checked the sound.cfg and what I remembered as being a blind wav link turns out to be just fine.
That "updated" config just replaces one of the left engine external sounds with the corresponding right engine sound. Wonder why?

Anyway, I resaved them many moons ago and don't have that problem since then.
Same trick worked so far on any other aircraft that had those issues (our very own Fw190, also verified by our beta testers and users, the new Storch and a couple others).
 
Mathias,
Sorry, but I still don't know what it is we are supposed to do to fix the Goose sound problem.

You said: 'Same trick worked so far on any other aircraft that had those issues..'. What / which 'trick'? Please elaborate. Or not. Your choice. I will understand.
Chuck B
Napamule
 
Well,

Here's what I did.....

Replaced the sound files with the updated one from above. Note, the Sound folder in the Goose I have is actually "Soundai", with another separate "Sound" folder:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Grumman_Goose_G21A\soundai

and....

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Grumman_Goose_G21A\Sound

respectively.

I've learned a bit from this process, but not why these files and folders are arranged this way. If someone could enlighten me I'd be most appreciative.

I tried putting the suggested sound.cfg file in several different places and played with it a bit. This eliminated the issue with throttle mismatch when switching views, however now the engines were more or less heard as cruise no matter what position the throttle was in. Why it pulled this particular wav I do not know and it may be that I simply messed up the transaction.

In any case I then backed up the original folders and copied in the sound files from the GAS Lockheed 12A, which I felt would be a close approximation to the Goose (If this is not "fair use" from my purchase, then someone needs to tell me and I will reverse the process--my review of the EULA seems to indicate I'm okay). These files work quite well and I've left it at that.

BTW, toggling the "Q" key did not seem to work for me. Can't tell you why.

I appreciate everyone's suggestions, and in no way was this request for assistance meant to be a critique of the Goose or those who worked it.
 
Chris ......... the soundai is for when it's used for AI aircraft. The sound folder is used when you fly it.
 
Back To Basics

TeaSea,
Will you try this? Load the C-172 and save IT as your 'Default' (ie: start up) flight. Exit FSX. Re-Start FSX. When the C-172 loads the Sim Engine will load certain parameters (perhaps including Ram address space for Sound?). Now load the Goose, set view to 'Locked Spot View', and then pan all the way around it a couple of times (using hat switch). Now go fly. Is the sound how it should be? Then you found a 'work around' that actually works. Forget about the 'Q' toggle.

But, the secret is having C-172 as 'Default' (start up) flight. If you start FSX with a 3rd party airplane (with 3rd party panel-making it even worse) then all bets are off. Simmers can't seem to accept that FSX after all is a computer program and not an XBox or console game. So, it's 'C-172 as default start up flight'- to set FSX up (profile?)-or be doomed (as there could be other 'issues' if you don't). Too easy.
Chuck B
Napamule
 
Chris ......... the soundai is for when it's used for AI aircraft. The sound folder is used when you fly it.

Thanks Joe! That explains it.

napamule, I may give that a try next weekend when I get some time to play with it.
 
Back
Top