bevyengine / bevyengine/bevy

Variable frametime during user input

Open
#4,691 6 comments 3 reactions 0 assignees View on GitHub
A-Input C-Bug C-Performance
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 16h
Merged PRs (30d)
171

Description

## Bevy version

0.7

## Operating system & version

Win11

## What you did

Use the tracing features to observe frame timings.

## What you expected to happen

Frametime should be consistent with an empty app.

## What actually happened

Extreme variability in the un-instrumented time between runs of the system graph while moving the mouse.

## Additional information

Using immediate mode (vsync off).
I started moving my mouse in the second half of the capture:

![image](https://user-images.githubusercontent.com/2632925/167261939-4476d52f-186b-4d3b-90ee-56427ec2c1fb.png)

A closer look at the time in question:
![image](https://user-images.githubusercontent.com/2632925/167261975-eb83454b-3df4-4031-bd6c-fc0ba7d31437.png)

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in a Bevy 0.7 empty app on Windows 11, using the tracing features to capture frame timings. Compare an idle run with a run while moving the mouse, keeping immediate mode enabled and vsync disabled. Done means the unexplained variability in un-instrumented system-graph time is identified and frametimes are consistent or the remaining limitation is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.