| 04-15-2007, 11:50 PM | #2 |
Hmm, I'd be interested to see how this one turns out. I can't see what's wrong with the trigger either. Try adding in text messages at seperate parts of the trigger to see which parts are running properly. Oh and I don't know if it's a good idea to have a periodic event that turns on a trigger. |
| 04-16-2007, 12:00 AM | #3 |
I want to say something .03 isn't an good value to work with. 0.1 is better. (For perodic timers) -Av3n |
| 04-16-2007, 12:02 AM | #4 |
I usually prefer .5 or .4 whenever doing a periodic event. Its fast enough so that it happens each frame on most computers, and if its a big trigger it doesnt make much lag. |
| 04-16-2007, 12:30 AM | #5 |
Most computers should be able to take .1 fine. |
| 04-16-2007, 01:09 AM | #6 |
Ok, a little more testing reveals that the trigger DOES work. The problem is that the final periodic timer just turns it self off after the first loop. EDIT: Never mind, the problem was within the 'If' statement. I removed it, now it works fine. |
| 04-16-2007, 01:35 AM | #7 |
Gah, i meant .05 and .04, not .5 and .4 -.- |
| 04-16-2007, 03:16 AM | #8 |
Moving it towards it's facing? So if it faces directly opposite the VoidSource it can get knocked back? And you do not turn off the Void trigger after the Void Interval, which means it keeps running. So I'm assuming you want a permanent 'black hole' effect that can push units backwards if it's facing the opposite angle. |
