![]() |
|
|
|
#1
|
|||
|
|||
|
Interesting, although not unexpected considering the detroyed trigger task is to activate on object destroyed, I mean how many times must it be kaput!
Probably a worth while exercise to look at all triggers in a similar way to see what "features" they have. For example, for the pass through trigger, from what I've seen it can be handled in a number of ways. if (shortName.Equals(shortName) && active) { //do somthing GamePlay.gpGetTrigger(shortName).Enable = false; } if you use only the following ,You can use the trigger in both true and false and it is always live. if (shortName.Equals(shortName)) { //do somthing } if you use only the following , it appears to only activate on true if (shortName.Equals(shortName) && active) { //do somthing } if you use only the following , it appears to only activate on true and disabled after use if (shortName.Equals(shortName) && active) { //do somthing GamePlay.gpGetTrigger(shortName).Enable = false; } So with that in mind, maybe leaving the following out of the destroy trigger it will stay live. GamePlay.gpGetTrigger(shortName).Enable = false; |
|
#2
|
|||
|
|||
|
That is a very good point. I have completed the scripting and have it working for the moment, and is now uploaded on the ATAG test system (Destroy or defend the convoys).
But this find up here could tidy up the script a little or make for easier implementation. I think i have to read the above or draw some diagrams to get my head around it hehehe. Will run your test tonight
__________________
__________________ Win7, 64bit Ultra Asus P8P67Pro MB Intel i7-2600K Coursair 16GB (4x 4GB), DDR3-1600MHz Gainward Nvidia 580GTX 3GB DDR5 850-Watt Modular Power Supply WIN7 and COD on Gskill SSD 240GB 40" Panasonic LCD TrackIR5 + Thrustmaster Warthog stick, throttle & pedals |
![]() |
| Thread Tools | |
| Display Modes | |
|
|