Timer Created 20 years ago2004-07-04 04:21:28 UTC by [VDC] Rad Brad

I've searched for something on timers and found nothing that helps. Everything seems to be based on triggers, not on time. What I'm looking to do is trigger an ambient_generic and I'd like it to play every 40 seconds. I have an env_beam that fires every 40 seconds and lasts for 5. The .wav file lasts for 5 seconds, so, if I can trigger the .wav to start every 40 or 45 seconds, depending on how it is counted out, it'll all line up. Is there a way to do this without setting up a lot of multimanagers, buttons, a trigger_counter, and a trigger_multiple?

multimanagers can sort out timers with their nifty 'value'.
Make something target a multimanager who targets;
beam value 0
sound value 0
mm2 value 45

Make multimanager2(mm2) target exactly the same as the first, except mm1, instead of 2.

A multi_manager can trigger itself, so for a loop you don't need a second multi_manager. However, you then need to set the Multithreaded flag, to avoid problems with this looped multi_manager.

I'd change the '0's to '0.1' to avoid possible problems.

0.01 or 0.001 for me, 0.1 can still be quite long for very neat time-schedules...

Not really when you add .1 to everything. Accounts for very slow PCs

Wich means on faster PC's your neat timing is done with?

a little off topic but, "seconds" in half-life arent real seconds... right? how long are the seconds really in half life?

Seconds are seconds.

Although I can imagine a low fps is somewhat disturbing for very small times.

ok, i guess i lose all concept of time when playing hl

Thank you very much. I'm not sure I understand it, but I have a different direction to go than I expected. I'll let you know.

Ah! Captain P! Targeting a second MM and looping it! That will fit the problem! Thanks!

(Had to read it a few times)

Well... I had it working, but the sound triggered every other time the laser fired. Just an update.... Happy 4th!

That 'every other time' problem means you need to tick the 'not toggled' flag on your ambient_generic. Then it will fire every time. Also make sure the multithreaded flag is ticked in both your multimanagers.

I'm actually using only one MM, but I'll kick that flag. Thanks!

Ok... it took two MMs and I didn't rename the button to match all the name changes I did... DOH!