Far-Beyond-Pulsar/Pulsar-Native

Engine framerate adjust curve needs to be smarter

Closed

#515 opened on Aug 6, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Rust (29 forks)auto 404
Cleanupdifficulty: mediumenhancementgood first issuehelp wantedperformancepriority: high

Repository metrics

Stars
 (348 stars)
PR merge metrics
 (PR metrics pending)

Description

The engine's level editor viewport currently defines a system wherein the framerate gradually climbs back to high FPS after a prolonged slowdown in order to avoid overloading low end hardware. The FPS after a drop should aggressively increase toward its highest stable framerate only going down from there if the framerate becomes unstable.

Contributor guide

Research direction
Investigate the engine's viewport framerate control logic, identify where the current gradual climb back curve is implemented, and understand how the target FPS is adjusted after slowdowns to implement a more aggressive recovery while maintaining stability.
Tech stack
rust
Domain
backendgame dev
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitRustFramerate control
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55