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

Recent area optimization commit causes massive FPS swings. #26149

Closed
Ace-Dragon opened this issue Feb 22, 2019 · 2 comments
Closed

Recent area optimization commit causes massive FPS swings. #26149

Ace-Dragon opened this issue Feb 22, 2019 · 2 comments

Comments

@Ace-Dragon
Copy link

Ace-Dragon commented Feb 22, 2019

Godot version:
v3.1.beta.calinou.8b231b9

OS/device including version:
Win10 64 bit, Ryzen 2700X processor, GTX 1060 6gb GPU.

Issue description:
Massive FPS swings in complex levels within this project of mine (because of physics checks).
http://www.mediafire.com/file/96cv304s5mw9w26/Collect_The_Gems%25280.13%2529.zip/file

Based on experience, it's due to physics-related stuff, so my guess is this patch merged by Akien.
ced77db

Steps to reproduce:
Open the project in Godot and press 'shift ~' to go to the level where the issues are most acute. This happens in builds done at commit 8b231b9. FPS sees major swings between 7 and 60.

Open the project again in a Godot build done at commit 16934c7, go to the same level. Notice how buttery smooth the FPS is, a near-constant 60.

Minimal reproduction project:
Already posted, sorry it's the whole game, but this type of thing can't be reproduced with simple scenes.

@slapin
Copy link
Contributor

slapin commented Feb 22, 2019

I confirm the area bug, but I tried to use movable areas and it was even worse result.

@akien-mga
Copy link
Member

For anyone testing the upcoming 3.1 beta 6: this bug will still be valid in beta 6, which has been built from a comment prior to #26153.

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