LarryG on 22/9/2014 at 02:40
FYI of apparent interference between NVRelayTrap and AnimLight
I recently tried to put an NVRelayTrap on an object with the Animlight script set to
flip between min in max. The design note was
Quote:
NVRelayTrapOn="Null"; NVRelayTrapOff="Sim"; NVRelayTrapTDest="[Me]"; NVRelayTrapCount=1
This was to force the light off at the start. But when I did so, the light stopped behaving as
flip between min in max was set, and instead acted like it was set to
minimum brightness. That is, it didn't flicker at all when turned on. If I use a marker for the NVRelayTrap with a CD link to the light, everything works fine. For some reason having NVRelayTrap on the same object as AnimLight seems to interfere with the functioning of the AnimLight script.
john9818a on 23/9/2014 at 02:36
I tried your example and got a different (maybe same result). I used a MechHangLamp as my light fixture. When I start the test mission the light is off, but when I turn it on the glass portion lights up constantly, but the metal base and surrounding terrain light up as they should.
LarryG on 23/9/2014 at 03:52
Different behavior, but still an indication of "not good" happening. My suggestion is not to mix the scripts on the same object.
john9818a on 23/9/2014 at 07:52
I agree with you on that suggestion, and I'm guessing you wanted to implement the setup without using extra objects. I usually use a lever to start a light off and not worry about using additional scripts.
LarryG on 23/9/2014 at 08:19
I generally try to minimize, having run out of objects a few times in the past. It was a real pain to overcome. I suppose with the NewDark increased object limit, there's no need, but old habits ...
qolelis on 23/9/2014 at 13:41
I tried your set-up and it works for me. I might be missing something, but I put the AnimLight script as the first script and NVRelayTrap as the second (or the other way around, but with a delay on the NVRelayTrap), and the light is turned off at sim start and starts "flipping between min & max" when turned on.
LarryG on 23/9/2014 at 17:48
I had Animlight on the archetype. I think it may be a memory related thing, as it seems to behave differently in different situations.
qolelis on 23/9/2014 at 20:52
In that case, adding a small delay may help - it did for me anyway. Maybe AnimLight needs to finish some initialization before being able to properly respond to TurnOffs!?
ZylonBane on 23/9/2014 at 21:08
Many of the animated lighting modes definitely have a "heartbeat". Throw an NVSpy on there and you'll see it spewing messages.
