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
"When another plugin is controlling a Wrath setting, it will be "blued" out and show an indicator, with which plugin it is"
The FrameWorkUpdate gets hit by an extra ~0.600ms incurrence.
This is with autoduty 0.0.0.0.182, but they also spam wrath with config updates during battle every FrameWorkUpdate.
To be sure it's from wrath only, I patched out this autoduty behavior calling Wrath IPC on every FrameWorkUpdate. And it still happens.
If I remove the claim by autoduty, by hitting the (X) inside the blue bubble, wrath ofcourse turns off, but then I myself reenable it manually. And this extra incurrence of 0.600ms, will not occur.
The text was updated successfully, but these errors were encountered:
Akechi-kun
changed the title
Huge FrameworkUpdate CPU cost (~0.600ms) addition, dropping FPS quite a bit.
[Core] Huge FrameworkUpdate CPU cost (~0.600ms) addition, dropping FPS quite a bit.
Jan 3, 2025
When this state occurs in wrath, 1.0.0.8:
"When another plugin is controlling a Wrath setting, it will be "blued" out and show an indicator, with which plugin it is"
The FrameWorkUpdate gets hit by an extra ~0.600ms incurrence.
This is with autoduty 0.0.0.0.182, but they also spam wrath with config updates during battle every FrameWorkUpdate.
To be sure it's from wrath only, I patched out this autoduty behavior calling Wrath IPC on every FrameWorkUpdate. And it still happens.
If I remove the claim by autoduty, by hitting the (X) inside the blue bubble, wrath ofcourse turns off, but then I myself reenable it manually. And this extra incurrence of 0.600ms, will not occur.
The text was updated successfully, but these errors were encountered: