Trouble with multisource Created 16 years ago2008-11-16 03:17:43 UTC by Soup Miner

I want to create a makeshift random teleporter with 6 possible exits.
To do it, I'm trying to toggle between 6 trigger_teleports. I'm using a multisource for each trigger, and a looping multimanager to control the toggle.
But the teleporters are all disabled, all the time, and trigger_changetarget is far too process-intensive to be a practical solution.

Tell me what I'm doing wrong:
-6 trigger_teleports named tele1, tele2... with masters set to master1, master2...
-6 multisources named master1, master2... with no global state master set.
-1 multithreaded multimanager triggered on startup with these properties:
Name: changeme
master1 - 0.25

master2 - 0.50
master1 - 0.50 (to disable tele1 and make way for tele2)

master3 - 0.75
master2 - 0.75

master4 - 1
master3 - 1

master5 - 1.25
master4 - 1.25

master6 - 1.5
master5 - 1.5
changeme - 1.5

master6 - 1.75 (coincides with 0.25 seconds after relooping, thus tele6 is disabled when tele1 is reenabled)

I think you're not giving the teleporters enough time to actually turn on and then off. I could be wrong though...

Try this:

master1 - 0.30

master2 - 0.50
master1 - 0.55 (to disable tele1 and make way for tele2)

master3 - 0.75
master2 - 0.80

master4 - 1
master3 - 1.05

master5 - 1.25
master4 - 1.30

master6 - 1.5
master5 - 1.55
changeme - 1.55

master6 - 1.75

Crap, sorry about never getting back to this.
Giving them more time didn't do the trick, but trigger_changetarget turned out to work fine.

Apparently there was another problem that I didn't know about causing "process lag", so I assumed the trigger_changetargets were to blame.

Thanks anyway.