Originally Posted by ZOS_DanBatson
Are you calling DelayedPOIPins repeatedly? Cause if so, you'd be re-registering repeatedly, which would keep reseting the delay clock, making it never ultimately fire.
There was a change to RegisterForUpdate recently (to account for a crash) that could result in some changed behavior if you were previously relying on subsequent calls to RegisterForUpdate (without an unregister first) to simply "drop on the ground silently." Now calling RegisterForUpdate again "replaces" whatever is currently registered (including replacing the delay time), rather than silently dropping it on the ground if something is already registered. This can mainly cause weirdness for anyone who was doing the register on a loop, which is not really something you should be doing anyway.
|
It's an addon I am maintaining, there are some sort of loops of RegisterForUpdate exiting to an unregisterForUpdate by a condition.
So the new rule for RegisterForUpdate is :
- Always unregister before registering again otherwise the new register replaces the previous one with it's own milliseconds value restarting from scratch.
Am I right?
I will try to see what I can do.
Thanks Dan!