• 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

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Engine Sound File Configuration Help

B

Browncoat

SOH-CM-2023
Years ago someone here had a very clever method of creating an engine sound file within CFS2, and then aliasing the aircraft sound folders to what ever engine was needed.

In years past this had the advantage of keeping CFS2's file size smaller as you would only need one set the 'large' (for the time) sound files rather than copying them to each aircraft. It also made it easy to move aircraft in and out of storage 'hangers' because the sounds were also in the main CFS2 file structure and not a part of individual aircraft.

Now I'm wondering if anyone knows how I can go about doing this.

Is it as simple as creating an 'engine sounds' file within the main CFS2 structure and they adding individual sound file there as aliasing the aircraft sound config to the appropriate file there?
 
You mean making a sound.cfg and than having it read sounds from another folder?
 
Jaxon did supply the outline on how to do it. I made one while back and it took some time to do. I scoured the internet and d/l almost every pertinent sound that I could find. Then classified them by manufacturer and sub-foldesr indicating whether single \dual\quad engines. On some instances I even then made further folders within the classification by plane type. ie; Corsair, mustang, etc. Then it was only a matter of making up a .cfg for each. When required you put the cfg in the game plane and it will (should) work.
One big sound file that can be referenced for any theater plane. Sample cfg IIRC was Drive\ Programs\Microsoft Games\cfs2\ Sounds. I have the file somewhere but will have to look for the thumb drive with it. The game setup was loss when my computer crashed awhile back.
Hope this little missive helps.
 
Create a folder for engine sounds. It can be in the CFS2 game you're running or it can be a stand alone folder if you have multiple installs. Place all of the engine sounds (for example from the stock Zero) into that folder. Then simply alias the sound files from your different engines to that new folder.

Here's the Betty sound file from a stock install:
[fltsim]
alias=A6M2_Zero\sound

Note that it aliases to the stock Zero sound. To do it on a big scale you're new sound file might look something like this:
[fltsim]
alias=C:\Program Files\Microsoft Games\Engine Sounds\WWI_Inline\Sound

This is from an Albatross in my WWI install. The sound is aliased to a folder outside the game. In my case I have sounds for rotary engines, twin engine and four engine planes as well as a whole assortment of other engines.

With at least eight different installs and hundreds of planes it saves disk space by aliasing to an outside sound file. It means you have to modify each individual sound file, but that's a small price to pay for the space it saves.
 
You must log in or register to reply here.
Back
Top