Author Topic: Sounds  (Read 1261 times)

0 Members and 1 Guest are viewing this topic.

Hey guys,
      I've posted on this forum a few times, and everyone continues to amaze me by making this game even better. But ever since I've played FSO, I have noticed that some of the sounds are missing or fail to load. When I am in the mission where an NTF Orion tries to make a suicidal collision with the Colossus, I am to protect a Leviathan. However, when the two Fenris cruisers move in range of the Leviathan, there is no charging-up noise of the SGreen. The same applies to the Mjolnirs, and the Aeolus cruiser when it charges up its dual SGreens. I do not know if this is just a situation with me, or if it applies to everyone else. Its a minor issue, but those beam charge-up noises are one of the most greatest sounds in the game. I looked through the wav files on the sparky_vp file, and I was wondering when are the BT_up_2.5 and 3.5 ever used? Same goes with the beam_shot2. I do not know, I was just curious if this only applies to me. Thanks guys.

BTW, I think I asked this before but no one answered.... has anyone thought of producing a supernova ani in the final mission?

 
I also noticed that the SRed beams in-game do not have a warm up sound, as well. I would think that they would use the wav file BS_up_1.5, however I do not think I have ever heard this sound in-game. Is everyone else not getting all of the warm-up sounds for the beam weapons?

 

Offline redmenace

  • 211
Government is the great fiction through which everybody endeavors to live at the expense of everybody else.
              -Frederic Bastiat

 

Offline CP5670

  • Dr. Evil
  • Global Moderator
  • 212
This is a long standing issue in FS2 and can be corrected to some degree by the changing the distance values for the beam sounds in sounds.tbl. 2.5 is used for the SGreen and 3.5 for the BGreen. I think the beam_shot things are actually used but you never hear them since they are drowned out by the beam looping sounds. You can hear them if you cheat and fire beams out of your fighter in the original retail FS2.

 

Offline WMCoolmon

  • Purveyor of space crack
  • 213
You can hear them if you fly really close too. I first noticed them in "High Noon" on anything besides the Sathanas. :D
-C

 
Thanks for the builds; however, they did not work in this case. As for changing the distance values, that is something that I do not know how to do. What wav file is supposed to be the warm-up sound for the SRed? Is there any other way that this issue can be fixed? I'm sorry, I know that it is not a big issue at all, but it has been constantly catching my attention.

 
Code: [Select]
$Name: 150 BT_up_1.wav, 0, 0.60, 2, 1500, 3000 ; 1 sec warm up
$Name: 151 BT_up_1.5.wav, 0, 0.60, 2, 1500, 3000 ; 1.5 sec warm up
$Name: 152 BT_up_2.5.wav, 0, 0.60, 2, 1500, 3000 ; 2.5 sec warm up
$Name: 153 BT_up_3.wav, 0, 0.60, 2, 1500, 3000 ; 3 sec warm up
$Name: 154 BT_up_3.5.wav, 0, 0.60, 2, 1500, 3000 ; 3.5 sec warm up
$Name: 155 BT_up_5.wav, 0, 0.60, 2, 1500, 3000 ; 5 sec warm up

Since all the beam warmup sounds should be heard at the same ranges, according to the original sounds.tbl, not hearing them seems to be a bug. I don't think I've ever heard the 3.5, 2.5, 1.5 or 1 second warmup sounds in-game.

 

Offline CP5670

  • Dr. Evil
  • Global Moderator
  • 212
I think those values are about right actually, but the loops can be heard much further away than their corresponding numbers would indicate. Maybe the loops originates from the entire length of the beam or something. I've noticed that you just need to be near some part of the beam itself rather than the turret it originates from to hear the sound at full volume.

Anyway, if you make all those values three or four times higher, it's usually possible to make out those sounds.

  
I understand now, however; I am unfamiliar with changing those values. Just like what Sid was saying, I do not think I have ever heard those noises in-game, including the warm-up sound for the SRed. So is this an undeclared bug that I should report? Initially I was curious if I was the only one with this problem, and now I know I am not alone.