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

Resmon "Total" value not matching the sum of displayed value #3031

Open
Mathu-lmn opened this issue Dec 23, 2024 · 3 comments
Open

Resmon "Total" value not matching the sum of displayed value #3031

Mathu-lmn opened this issue Dec 23, 2024 · 3 comments
Labels
bug triage Needs a preliminary assessment to determine the urgency and required action

Comments

@Mathu-lmn
Copy link
Contributor

What happened?

Looking at this image : https://i.imgur.com/URbI2VB.png
I noticed that 0.73+0.03+0.03+0.02+0.02+0.02+0.01+0.01 = 0.87ms (!= 1.29ms)

Expected result

Either showing the correct value, or adding a value that is currently not displayed somehow

Reproduction steps

  1. Open resmon
  2. Do basic maths

Importancy

Slight inconvenience

Area(s)

FiveM

Specific version(s)

FiveM canary client

Additional information

No response

@Mathu-lmn Mathu-lmn added bug triage Needs a preliminary assessment to determine the urgency and required action labels Dec 23, 2024
@DaniGP17
Copy link
Contributor

I noticed it when I started my server with only one script, I assumed that the consumption that was left over came from the fivem itself

@outsider31000
Copy link
Contributor

same happens on RedM side

@d22tny
Copy link

d22tny commented Dec 26, 2024

I think it's just the overhead given by the engine. So most probably the remaining time is just some computation done directly by C++ which isn't attributed directly to any resource, but yet the resource manager tick still has to wait for it. So yeah, basically i think it's just FiveM's runtime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triage Needs a preliminary assessment to determine the urgency and required action
Projects
None yet
Development

No branches or pull requests

4 participants