It is called the MJ rule because MJ first stumbled upon it.<\/p>\n
*events *autofx In this example the total wait times for event #3 is \u00a0(3+4) = 7. While it is less than the event time on event #3 (9), this is not the event that is applied. It is always the difference between the\u00a0PREVIOUS\u00a0\u00a0<\/strong><\/span>event and CURRENT <\/span><\/strong>event when ELAPSED time is used \u00a0which is the DURATION of Event #3, which is the most common type of EVENT TYPE used.<\/p>\n Subtract Event #2 time (5) from Event #3 Time (9). \u00a09 – 5 = 4<\/p>\n Event #3. Its duration is only 4. \u00a0And so 7 seconds is greater than 4\u00a0seconds. There is not enough time for the WAITS to happen. This is an ERROR!<\/p>\n What we found out is that the consequences often happen many events later so its not obvious that the problem is on Event #3 because functions attached to event #3 might work fine. \u00a0In the real life case, the emote\u00a0attached to event #7 did not fire. Where the behaviour will falter and suffer is complex and unpredictable.<\/p>\n This was argued to me. But once I\u00a0found the problem and fixed the WAIT times so they were less than the duration of Event #3, the problem in Event #7 was fixed<\/p>\n ======================<\/p>\n *events When using DURATION as the Event Type, it is a lot easier and intuitive to detect. The DURATION for EVENT #3 is 4.<\/p>\n","protected":false},"excerpt":{"rendered":" It is called the MJ rule because MJ first stumbled upon it. *events TRACE,on ELAPSED 1,”Event #1″,3 2,”Event #2″,5 3,”Event #3″,9 4,”Event #4″,21 5,”Event #5″,37 6,”Event #6″,44 7,”Event #7″,52 8,”Event #8″,79 *autofx 3,r15=Shoot$WAIT=3$r15=Holster$WAIT=4$ In this example the total wait times for event #3 is \u00a0(3+4) = 7. While it is less than the event time … Continue reading The MJ Rule – Excessive Wait Times in an AutoFX Line Entry<\/span>
\nTRACE,on
\nELAPSED
\n1,”Event #1″,3
\n2,”Event #2″,5
\n3,”Event #3″,9<\/strong>
\n4,”Event #4″,21
\n5,”Event #5″,37
\n6,”Event #6″,44
\n7,”Event #7″,52<\/strong>
\n8,”Event #8″,79<\/p>\n
\n3,r15=Shoot$WAIT=3$r15=Holster$WAIT=4$<\/p>\n
\nTRACE,on
\nDURATION
\n1,”Event #1″,3
\n2,”Event #2″,2
\n3,”Event #3″,4<\/strong>
\n4,”Event #4″,12
\n5,”Event #5″,16
\n6,”Event #6″,7
\n7,”Event #7″,8<\/strong>
\n8,”Event #8″,27<\/p>\n