sound problems...

  • If you're asking a question make sure to set the thread type to be a question!

Artesia

L6: Sharp Member
Nov 11, 2008
278
72
I need to trigger sounds to play for only one team and not the other... I've done a search on this and found this post... I can type the play vo/announcer_we_captured_control.wav in the console and it plays fine, but when I trigger to a point_clientcommand with the Command input play vo/announcer_we_captured_control.wav parameter... nothing happens, I can see the command appears in developer 2... has anyone gotten this to work or know how to play a sound for only one team? this is vital to my map :(
 

Armadillo of Doom

Group Founder, Lover of Pie
aa
Oct 25, 2007
949
1,228
Unfortunately, such elaborate filtering is broken for TF2. Unlike DM, we still can't target based on team, weapon, etc. Sorry m8 :(
 

Artesia

L6: Sharp Member
Nov 11, 2008
278
72
I actually got it working using the meathod someone posted here but modified... 2 point_clientcommand entities, one for each team. 2 giant trigger brushes that engulf the whole map, one for each team filtered to each team. 2 logic_relay entities for each sound one for each team. I used 9 sounds so I had 18 relays. 2 math_counters one for each team. 2 Logic_case entities once again one for each team... what I did was start all the logic_relays disabled (their output is to send the point_clientcommand a play soundname.wav). start the giant trigger brushes disabled. when the event I want to play a sound for happens, I have that event send a number to the correct team's math_counter, right after which it sends a getvalue to that mathcounter. the math_counter on getvalue sends that team's logic_case its value as an invalue, the case the number is associated with then enables the correct logic_relay. the giant trigger brush is then enabled which attempts to trigger all the logic relays for that team, but of course only the one is enabled so the sound plays. the giant trigger and the logic relays are once again disabled and ready for the next event.

I used the logic string to prevent having to have more than 2 giant triggers... as I find them incredibly annoying, but I just have a visgroup named "Giant Annoying Brushes" that I hide when I'm working ;)

if needed I could always write this in a more organized visual manner as a tutorial if there is demand for such a thing.