bevyengine / bevyengine/bevy

Promote delta time debug log to warning

Open
#10,146 0 comments 1 reaction 0 assignees View on GitHub
A-Assets A-Rendering A-Time C-Usability
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 16h
Merged PRs (30d)
171

Description

## What problem does this solve or what need does it fill?

In https://github.com/bevyengine/bevy/pull/10145 I demoted this to a `debug!` log because it is regularly triggered when doing things like loading scenes.

This _is_ a useful warning (as it is an indicator of doing too much work in Update / it means a hitch occurred), but it is currently unactionable for this common case, which is why we opted to disable it.

## What solution would you like?

Ideally we can move the work from our scene / rendering code that causes this hitch out of Update and onto a separate thread. This would both solve a hitching problem and allow us to promote this log back to a warning without spamming peoples' consoles.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the delta-time debug log and the scene and rendering work triggered from Update. Reproduce the hitch while loading scenes, then identify which work can be moved to a separate thread without breaking rendering or scene loading. Done means the common case no longer hitches in Update and the diagnostic can be promoted to a warning without console spam.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
game-dev, performance
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.