Cleaning up the "Goose"

[TeaSea]

Something I'm sure someone's taken care of and I've just missed it. The issue with the default sound files in the default MS Goose.

FS9 these worked quite well, however in FSX the Goose get's confused as to how many RPM's are running and what the throttle settings are. Hence the sound as though at full RPM's when one is idling.

How have you guys addressed this?

[Killbilly]

A poor patch job is just to hit the "Q" key twice whenever you get the stuck high RPM sound (usually after switching views). That resets the sound until you switch views again.
I downloaded the HD Goose Redux from OZx, and haven't noticed the sound problem since (plus the Goose has never looked nor flown better). So that may be a better solution.

[TeaSea]

Thanks Killbilly -- I will use the "Q" fix for now.

I also have the HD OZx version, but it has not cleaned up that particular issue for me although the aircraft looks fantastic.

Your description of the issue is dead on. I had not realized it, but switching views is when that occurs for me.

I was thinking of swapping sound files with the GAS Lockheed 12....'course if the error is in the aircraft config file that wouldn't necessarily help.

[Mathias]

You can try to resave the wav files in the goose sound folder in PCM signed 16b format.
Goldwave can do that, it comes with a trial version.

[Daube]

I think I have read somewhere that the solution for this RPM sound problem consisted in editing the default FSX cameras.cfg to remove the top-down (sattelite) view... I can't remember exactely where I read that, though, so do not do it until you find "reliable" info, please.

[FAC257]

It's an FSX thing.

I have to use the "Q" key trick on quite a few aircraft from time to time to reset the sound. It does seem like it is almost always brought on by switching views. I think in some cases even panning the view triggers it.

FAC

[Mathias]

Try the reformatting thing, it'll fix it.

[warchild]

One thing i can assure you all is that this particular error does not originate in the aircraft.cfg file.. I'm not saying i did a perfect job on the flight model, but the flight model has absolutely no relation to the sound file..
I'm afraid that when we reworked the plane, the sounds were not something we did anything with at all.. you'll find the same sounds in the default goose.

The aircraft uses a double wasp engine, so early lockheeds, beechs and boeings are all good candidates for replacing the sounds..

[lazarus]

On the FSX Sound thing- it has seemed to me that the sound driver for FSX is a bit of a bottleneck as far as loading drag and fps hit. Or am I imagining that?

[TeaSea]

One thing i can assure you all is that this particular error does not originate in the aircraft.cfg file.. I'm not saying i did a perfect job on the flight model, but the flight model has absolutely no relation to the sound file..
I'm afraid that when we reworked the plane, the sounds were not something we did anything with at all.. you'll find the same sounds in the default goose.

The aircraft uses a double wasp engine, so early lockheeds, beechs and boeings are all good candidates for replacing the sounds..

That's good info Warchild. At least I know that there's no relationship to the files.

[Gizmo]

Gotta echo what pam said here we really didnt look at the sounds for the goose

while re-texture/normal mapping can be done quite well from a collection of static pics and the FM from stats and flight manuals and feel,new sounds was something that would have needed us to have access to a running wasp and some good quality recording kit

I did mail a guy who could have gotten some access to a running wasp via a local transport company but he didnt have any good recording kit so i never brought the suggestion to the rest of the team

The default Beaver was up next for a Redux and i got the normal mapping/test scheme about 95% done but i had a few RL issues that prevented me from having the time to work as part of a team so it kinda die a death as a project,i still have the dev files so it might see the light one day when i get some time to crack out the crayons again

Laters
steve

btw heres a few shots of the halted beaver Redux as a tease

Attachment 47727Attachment 47728

[PhillRoath]

Something I'm sure someone's taken care of and I've just missed it. The issue with the default sound files in the default MS Goose.

FS9 these worked quite well, however in FSX the Goose get's confused as to how many RPM's are running and what the throttle settings are. Hence the sound as though at full RPM's when one is idling.

How have you guys addressed this?

Folks are correct in the sound problems but it's more a Windows 7 than FSX. Under XP I did not have that problem but now on rare occasion have to use the "Q" fix.

That being said, there was also a known problem with the Goose and it was fixed via the sound.cfg file. I've attached a copy of the one I got off the internet (AVSIM?) that you can give a try. Rename the original first and you can compare with yours to see the changes made.

Phill

PS - had to add the .txt on the end of file name so the forum uploader would work.

[Helldiver]

The Goose needs more cleaning up than the mere sound files. Why doesn't someone do something about the retractable wing floats and those atrocious spinners? None of them were used by Military JRFs. For that reason, I won't fly the funky FSX version
Attachment 47748

[mmann]

I feel the same way about the FSX Acceleration P-51! I guess it's a matter of what you expect from a model; the original aircraft versus a modern version of the original.

[warchild]

unfortunately, the floats and the spinners are part of the copyrighted model owned outright by microsoft. unless they change the actual model itself, theres no way for anyone of us to legally change it. I dont care for the retractable floats myself, but in point of fact, they exist in real life, as does the spinner. It's what prompted me to create a second higher power version of the flight model in order to reflect changes in the more modernized plane.


Originally designed to accomodate wealthy business men who lived in the richer areas of new england but worked in new york city It was adopted for use by the military, and became a legend.