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

FPS drop #98077

Closed
prfiredragon opened this issue Oct 11, 2024 · 8 comments
Closed

FPS drop #98077

prfiredragon opened this issue Oct 11, 2024 · 8 comments

Comments

@prfiredragon
Copy link

Tested versions

  • Reproducible in: v4.4.dev.custom_build
  • not reproducible on : 4.3 Stable

System information

v4.4.dev.custom_build foward+

Issue description

Hi, Just to let you know.

the first problem was that the plugin don't load but with the #98041 now I have the plugin working. but now the fps has drop from 141 in my case to 25. If I am not wrong the issue began after i sync the sources Yesterday.

If i build a test scene with a Terrain 3d Default terrain, a label for de fps and a camera I get 60 fps.

20241010_20h35m21s_grim

Steps to reproduce

If i build a test scene with a Terrain 3d Default terrain, a label for de fps and a camera I get 60 fps.

code:
`extends Node3D
@onready var label: Label = $Label

func _process(_delta: float) -> void:
label.text = ("%s FPS" % str(Engine.get_frames_per_second()))
pass
`

Minimal reproduction project (MRP)

fps-test.zip

@fire
Copy link
Member

fire commented Oct 11, 2024

Can you check if this fails on 4.4 dev 3?

@prfiredragon
Copy link
Author

Can you check if this fails on 4.4 dev 3?

20241011_03h24m12s_grim
20241011_03h24m23s_grim

@prfiredragon
Copy link
Author

with Engine.set_max_fps(0)

20241011_03h32m42s_grim
20241011_03h35m25s_grim

@clayjohn
Copy link
Member

Are you comparing a custom build to the official build? Remember that official builds are compiled with many optimizations that you have to specify manually in your scons build command.

Custom builds are therefore expected to be much slower than stable builds.

Can you test from a manually compiled version of 4.3 stable to rule out the regression coming from build settings?

@prfiredragon
Copy link
Author

Are you comparing a custom build to the official build? Remember that official builds are compiled with many optimizations that you have to specify manually in your scons build command.

Custom builds are therefore expected to be much slower than stable builds.

Can you test from a manually compiled version of 4.3 stable to rule out the regression coming from build settings?

20241011_11h03m01s_grim
20241011_11h03m22s_grim

@prfiredragon
Copy link
Author

20241011_21h22m58s_grim
20241011_21h23m12s_grim

@prfiredragon
Copy link
Author

prfiredragon commented Oct 15, 2024

Now is working and i have more questions. I detect that my Home Hard-drive has damage sectors and the 4.4 copy was in then. I decide to change my root hard-drive to a M.2 and use another mechanical for my home. I make a few tests. My Question here is when i am using the editor the project is reading and writing constant from the hard-drive ? and when is exported not?

on a M.2:
20241014_19h42m24s_grim

Exported project running from the M.2:
20241014_20h04m41s_grim

Godot on a M.2, the project on a Mechanical HardDrive
20241014_20h32m58s_grim

@prfiredragon
Copy link
Author

Ok, I changed to MTerrain and now the FPS is the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants