In the Aces High II/Sounds directory, there are numerically numbered files for most "game sounds" (non plane-specific). So, for example, there is "hit_1" through "hit_7", all of which are slightly different sounds of your plane being impacted that when you are strafed by multiple .50 cals or .303's, those sounds all play randomly in quick succession and the resulting sound is pretty believable.
So far so good.
However, there are also numerically numbered files which NEVER get used. "damage" is one. I have "damage1" and "damage2", both are supposed to be the files that play when my plane takes significant damage (a piece falling off), however only damage1 ever plays. The same clunky sound for a wing falling off, flaps being bent in place, or a pilot wound.
Same thing with "explode". For whatever reason I have 14 (!) numerical progressions of "explode", and I can only recognize three of them from hearing them in game. One is puffy ack exploding, the other is 5 inch shells exploding, and the other is an enemy plane exploding. 11 of my "explode" sounds never get used, and it's a shame too because some of them sound pretty nice.
Here is my wish: clean up the sound root directory
Point A: There exists the ability to run multiple sounds for the same game event (see "Hit.wav" sequence as described above)
Point B: We already HAVE many great sounding file multiples in our directory that are unused
Case: Therefore, why not give us some striations in sound for certain key events?
-I would like to hear more than one exact same explosion every time a plane explodes.
-I'd really like to hear different sounds indicating critical damage has been taken (please differentiate between structural components, oil line, fuel tank hit, and especially pilot wound)
-I'd like to hear more than one sound for hitting debris.
-I'd like multiple sounds for when the plane comes in contact with the physical environment (the crash sound is the same every time, even though you only hear it briefly before going to the tower, and the scrape sound for belly landings is the exact same every time, no matter what plane you are in)
Maybe I'm just getting dinged up too much, but I'm really sick of hearing "CLUNK" then "uh oh, better check ctrl+D to see what it was". A real life pilot would have a generally better idea of what was hit, why not give that to us in game? All of these suggestions would really help with immersion.