Lau Posted December 21, 2020 Posted December 21, 2020 Good Day, Currently using TIME MORE 30 (read short delays) without problem. Make that TIME MORE 5400 (read long delays) and I am not getting any positive outcome Any limitations hard coded in the engine? Best, Lau F4E, F14B, F18C, F16C, M2KC, A10C, C101, AH64D, BSHARK3, SA342M, MI8, P51D, SPIT, MOSSIE PG, NTTR, SYR, NORM2, WW2PK, CMBARMS, SCVN Asus F17 RG I9 RTX3060 64RAM NVME 2To, TMWarthog, Saitekpedals, TrackIR,
Flappie Posted December 21, 2020 Posted December 21, 2020 Hi Lau. I've just tested it: no issue on my side. Here's a track if you want to test it (I've accelerated time in the track). The first vehicle will explode after 30 seconds, and the second vehicle after 5400 seconds. Change the timer of your trigger to 10 seconds to test out your condtions. Once you're sure it will work, make it 5400 seconds long. Time_more_5400.trk ---
Lau Posted December 22, 2020 Author Posted December 22, 2020 Hello Flappie, Thanks for the feedback, my initial post mentioned succesfully trying what you suggested but thank you. There is something in my mission preventing it from working. Meanwhile I am using a rather satisfying alternative: I am using a vehicle with precise waypoints times to trigger the mission options, just make sure nothing can hit it and it works like a charm. Best, Lau F4E, F14B, F18C, F16C, M2KC, A10C, C101, AH64D, BSHARK3, SA342M, MI8, P51D, SPIT, MOSSIE PG, NTTR, SYR, NORM2, WW2PK, CMBARMS, SCVN Asus F17 RG I9 RTX3060 64RAM NVME 2To, TMWarthog, Saitekpedals, TrackIR,
Recommended Posts