Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Core] Huge FrameworkUpdate CPU cost (~0.600ms) addition, dropping FPS quite a bit. #266

Open
PhoenixtheII opened this issue Jan 2, 2025 · 0 comments
Assignees
Labels
Bug Something isn't working

Comments

@PhoenixtheII
Copy link

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.

@zbee zbee self-assigned this Jan 2, 2025
@zbee zbee added the Bug Something isn't working label Jan 2, 2025
@Akechi-kun 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants