Soundtrigger
Posted: 22 Dec 2006, 04:16
Please ignore if this has been fixed in .74 or a subsequent SVN edit, I haven't even had a chance to boot Spring up in the last two months.
This post is concerning the SoundTrigger=[0/1] tag in weapon definition files. Its purpose is to be used in conjunction with burstfire weapons to make the weapon emit only one sound per burst, rather than per shot. It saw a lot of utility in the OTA days, with things like Flashes using special sound effects of four sequential EMG shots, thereby reducing the lag induced by these types of weapons by 75%.
In Spring, it could see similar use, or, more importantly, be used to reduce the number of simultaneous sound effects which get exponentially louder and eventually wreck speakers. I've got 2 borked-up sets of speakers and 3 sets of headphones, over $120 in equipment, all basically destroyed by extensive use with Spring. The use of Sountrigger would not completely eliminate this problem, but it would *massively* decrease it. I cannot emphasize this enough. Since there's no dedicated sound system programmer to solve this issue through other methods, implementing soundtrigger seems like a good alternative.
To give a real-life and verifiable example, take the Pyro. Every time it fires a stream, it emits the flamethrower sound effect 20 times (22 in AA, if I'm not mistaken), designed by Cavedog to be used only once. This can be seen by the presence of soundtrigger=1; in the FLAMETHROWER weapon.
With each overlapping flamethrower effect, the loudness, logically, should be doubled. So you're hearing it 20x louder than it ought to be. That's for one pyro. Nobody uses one pyro. More like, 10? 20? 50? You can see where the problem can escalate quickly.
"Flamethrower" is only one example, but it's probably the worst one in OTA. Please consider adding the Sountrigger variable to Spring.
Thanks
This post is concerning the SoundTrigger=[0/1] tag in weapon definition files. Its purpose is to be used in conjunction with burstfire weapons to make the weapon emit only one sound per burst, rather than per shot. It saw a lot of utility in the OTA days, with things like Flashes using special sound effects of four sequential EMG shots, thereby reducing the lag induced by these types of weapons by 75%.
In Spring, it could see similar use, or, more importantly, be used to reduce the number of simultaneous sound effects which get exponentially louder and eventually wreck speakers. I've got 2 borked-up sets of speakers and 3 sets of headphones, over $120 in equipment, all basically destroyed by extensive use with Spring. The use of Sountrigger would not completely eliminate this problem, but it would *massively* decrease it. I cannot emphasize this enough. Since there's no dedicated sound system programmer to solve this issue through other methods, implementing soundtrigger seems like a good alternative.
To give a real-life and verifiable example, take the Pyro. Every time it fires a stream, it emits the flamethrower sound effect 20 times (22 in AA, if I'm not mistaken), designed by Cavedog to be used only once. This can be seen by the presence of soundtrigger=1; in the FLAMETHROWER weapon.
With each overlapping flamethrower effect, the loudness, logically, should be doubled. So you're hearing it 20x louder than it ought to be. That's for one pyro. Nobody uses one pyro. More like, 10? 20? 50? You can see where the problem can escalate quickly.
"Flamethrower" is only one example, but it's probably the worst one in OTA. Please consider adding the Sountrigger variable to Spring.
Thanks