Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

Script job using the "timeChanged" event always executes...even when time hasn't changed

mcw0
Advisor

Script job using the "timeChanged" event always executes...even when time hasn't changed

mcw0
Advisor
Advisor

I have a bifrost setup that is using previous frame values to calculate velocities.  I have conditionals to reset everything based on a startframe value.  But even with that, I still need to kick the system with a "dgdirty" command.  So I thought I'd use a scriptJob to run the "dgdirty" command for me whenever the current frame is less than or equal to my startframe.  I save the file at my start frame.

When I reopen the file, the scriptJob is created and then it runs the "dgdirty" over and over again.  Even though time has not changed.  I was expecting it to run once only.  Why is it running when time hasn't changed?  

0 Likes
Reply
169 Views
0 Replies
Replies (0)