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

Initialize View Frame Time estimates to match 120 FPS #80124

Merged

Conversation

Calinou
Copy link
Member

@Calinou Calinou commented Aug 1, 2023

When View Frame Time is freshly enabled, this prevents the estimation from being extremely high (close to 100,000 FPS) until enough time has passed to display an accurate estimation.

With #75512, this is still relevant for the CPU time and GPU time display.

Preview

Play the videos at 0.5× speed by right-clicking it and choosing the speed in the browser's context menu.

Before

simplescreenrecorder-2023-08-01_17.41.31.mp4

After

simplescreenrecorder-2023-08-01_17.43.03.mp4

@Calinou Calinou requested a review from a team as a code owner August 1, 2023 15:44
@Calinou Calinou added enhancement topic:editor topic:3d cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release labels Aug 1, 2023
@Calinou Calinou added this to the 4.x milestone Aug 1, 2023
@Calinou Calinou force-pushed the 3d-editor-frame-time-initialize-fps branch from ca8537f to 1f373e3 Compare August 18, 2023 09:50
@clayjohn
Copy link
Member

I think it looks a bit jarring for the numbers to start orange and then fade down. Maybe we should use a middleground like 8 ms to start so the numbers start green and have a reasonable value to scale up or down from

@Calinou
Copy link
Member Author

Calinou commented Aug 28, 2023

I think it looks a bit jarring for the numbers to start orange and then fade down. Maybe we should use a middleground like 8 ms to start so the numbers start green and have a reasonable value to scale up or down from

Done 🙂

This prevents the estimation from being extremely high (close to 100,000 FPS)
until enough time has passed to display an accurate estimation.
@Calinou Calinou force-pushed the 3d-editor-frame-time-initialize-fps branch from 1f373e3 to 15b31f0 Compare August 28, 2023 15:26
@clayjohn clayjohn modified the milestones: 4.x, 4.2 Aug 28, 2023
@Calinou Calinou changed the title Initialize View Frame Time estimates to match 60 FPS Initialize View Frame Time estimates to match 120 FPS Aug 28, 2023
@akien-mga akien-mga merged commit 1ffc24e into godotengine:master Aug 29, 2023
15 checks passed
@akien-mga
Copy link
Member

Thanks!

@Calinou Calinou deleted the 3d-editor-frame-time-initialize-fps branch August 29, 2023 22:45
@YuriSizov
Copy link
Contributor

Cherry-picked for 4.1.3.

@YuriSizov YuriSizov removed the cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release label Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants