You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Queue Lock Threshold is currently bugged and allowing oGCDs to take priority and interrupt the queue. The Queue Lock Threshold should only apply to GCDs.
Ideally you would want to set the Queue Lock Threshold to 0.1 so you have the most amount of time to change your GCD at the last second if needed. However since it currently lets oGCDs take priority and interrupt the queue, this can cause major clipping issues. This is most apparent on Monk which spams an oGCD nonstop and relies on the Queue Threshold (usually 0.6-0.7) to prevent it from clipping.
The text was updated successfully, but these errors were encountered:
The Queue Lock Threshold is currently bugged and allowing oGCDs to take priority and interrupt the queue. The Queue Lock Threshold should only apply to GCDs.
Ideally you would want to set the Queue Lock Threshold to 0.1 so you have the most amount of time to change your GCD at the last second if needed. However since it currently lets oGCDs take priority and interrupt the queue, this can cause major clipping issues. This is most apparent on Monk which spams an oGCD nonstop and relies on the Queue Threshold (usually 0.6-0.7) to prevent it from clipping.
The text was updated successfully, but these errors were encountered: