FlakNine
Members +
All the dropbox links showed as "deleted" except "That's All Brother" - I assumed you'd changed your mind and wanted to keep Irish Angel as is. Send over whatever you've got and I'll add it to the package.
-
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
Flight Réplicas Douglas Dc-4 and B-24 free Released
- Thread starter diegoxs
- Start date
Something went wrong with dropbox. It should now be ok. https://www.dropbox.com/scl/fo/e7a9...ey=l5azdv9fv0nxaiokh6xfs1mwk&st=0k378196&dl=0
I'm having some issues with the B-24. The engine sound doesn't change from idle to full power, it sounds like it's constantly at full chat. The throttles are moving and other aircraft work fine so not sure what's happening here. Can anyone advise on the issue? I'm using a T.16000 Thrustmaster, nothing fancy. Thanks
FlakNine
Members +
It's just the way the sounds are on this FSX conversion. I'd love to improve the sounds on this aircraft but that would need a new dedicated WWISE sound pack - which realistically isn't going to happen on a freeware project. Your best option is to follow the readme instructions to map it to the DC6 sound pack, if you own that aircraft.
lagaffe
Members +
If I understand Guzler's remark correctly "The engine sound doesn't change from idle to full power,", here is my opinion.
If we look carefully at the sound.cfg file in this pack, we notice that there are several files of the type xB24_rpm0x.wav [01 - 043] and that each of these files is called by the sound.cfg file depending on the power required via throttles.
When listening, these files are all different in terms of bass and amplitude, so the fact that they come from an FSX conversion has no impact: the sounds even FSX, that is to say Legacy, should work under MSFS 2020. That one wants to improve them with a WWISE pack is one thing but that these Legacy sounds do not work is another.
The first sounds we used on the Stearman were Legacy sounds and no one remarked that the sounds did not change according to the RPMs.
If we look carefully at the sound.cfg file in this pack, we notice that there are several files of the type xB24_rpm0x.wav [01 - 043] and that each of these files is called by the sound.cfg file depending on the power required via throttles.
When listening, these files are all different in terms of bass and amplitude, so the fact that they come from an FSX conversion has no impact: the sounds even FSX, that is to say Legacy, should work under MSFS 2020. That one wants to improve them with a WWISE pack is one thing but that these Legacy sounds do not work is another.
The first sounds we used on the Stearman were Legacy sounds and no one remarked that the sounds did not change according to the RPMs.
FlakNine
Members +
OK thanks for this, I assumed that we were stuck with what we have, since we have barely touched the sound.cfg. Thanks for the guidance I'll see if we can make some improvements with the legacy sounds; it's encouraging news that you think we can! I just need to do some learning about legacy sound methodology.
Any sound fixes won't be in V18 since that's hopefully going to be released imminently, but it'll be on the shortlist for V19!
lagaffe
Members +
In the past, there was a very practical tool called FS Sound Studio (http://www.fssoundstudio.com) It is still on sale and not very expensive (20$ USD). It allowed to work on WAV files in a very intuitive way (Online manual: http://www.fssoundstudio.com/help)
Even if the WWISE system seems to impose itself, we still have the possibility to add Legacy sounds to a WWISE set to correct it or if we cannot modify it directly (in case we use an existing pack on another aircraft for example).
PS: The price of a WWISE package creation is between 1500 (mono engine) & 2000 $USD.
Even if the WWISE system seems to impose itself, we still have the possibility to add Legacy sounds to a WWISE set to correct it or if we cannot modify it directly (in case we use an existing pack on another aircraft for example).
PS: The price of a WWISE package creation is between 1500 (mono engine) & 2000 $USD.
Last edited:
FlakNine
Members +
Thanks @lagaffe - I already made some good progress understanding how the sound works - I'm rebuilding it using sound.xml instead of sound.cfg, but with the original WAV files. I wrongly assumed there wasn't much we can do, but I stand corrected!
Out of interest, I'm looking for some generic WAV sound files for switches, levers, fuel pumps, etc. Is there any good source for these? Obviously need to be open source.
Out of interest, I'm looking for some generic WAV sound files for switches, levers, fuel pumps, etc. Is there any good source for these? Obviously need to be open source.
FlakNine
Members +
An evening spent playing with the engine sound curves was (in my opinion) successful. Hopefully we can get the new sounds to you all soon!
Here's an example of how (for a single engine) 4 different samples are blended together based on engine RPM. The vertical axis is the volume parameter. Each colour line is one engine sample sound: the blue line is the rough barely idling sound, progressing through red and yellow as the engine RPM increases into cruise range, then blending in the buzzy high RPM of the green line.
Here's an example of how (for a single engine) 4 different samples are blended together based on engine RPM. The vertical axis is the volume parameter. Each colour line is one engine sample sound: the blue line is the rough barely idling sound, progressing through red and yellow as the engine RPM increases into cruise range, then blending in the buzzy high RPM of the green line.
FlakNine
Members +
If I find myself needing to do more sound than just this single project then I might buy it since it does look useful, but for now I'll stick with a spreadsheet plus some trial-and-error reloading in the sim. Thankfully I have a bare-bones MSFS 2020 install on my PC so I can easily reload the aircraft from the SDK after making changes to the sound xml (I don't have the project itself).
I've created some formulas in my spreadsheet to build chunks of XML for the sound curves, which minimises my copy-pasting!
jankees
SOH-CM-2025
FlakNine
Members +
Very nice! Is that a new one or had I just missed it before?
jankees
SOH-CM-2025
no, a new one, done after a request, I just haven't uploaded it yet.
More on this aircraft and its pilot F/O L.A. Trigg VC here: https://airforcemuseum.co.nz/blog/flying-officer-lloyd-allan-trigg-vc-dfc-submarine-hunter/
More on this aircraft and its pilot F/O L.A. Trigg VC here: https://airforcemuseum.co.nz/blog/flying-officer-lloyd-allan-trigg-vc-dfc-submarine-hunter/
Bushpounder
SOH-CM-2024
That bottom shot is a beauty!!
RandallSnow
Members +
With regard to the sound.xml, something I've just learned is possible thanks to "SV-001/R" in the FS2 Discord is using multiple volume curves on each <Sound> tag. The VolumeCurve section which reads the "INTERACTIVE POINT OPEN" value allows us to "fake" door/window sound deadening without being forced down the WWISE path. Figured others might find it helpful.