Fix crash with bevy_dev_tools
#21873
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
janhohenheim
approved these changes
Nov 17, 2025
janhohenheim
added
A-Dev-Tools
atlv24
approved these changes
Nov 17, 2025
atlv24
added
S-Ready-For-Final-Review
weihnaxbaum
approved these changes
Nov 18, 2025
kerkmann
approved these changes
Nov 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
The
bevy_dev_toolscrate has some UI widgets to display FPS metrics and stuff, but thebevy_dev_toolsfeature doesn't enable any UI features, so the UI plugins aren't added and it crashes at startup.Fixes #21851
Solution
Enable "bevy_ui" and "bevy_ui_render" features when "bevy_dev_tools" is enabled.
Maybe the
bevy_dev_toolscrate needs more feature gates, or should be split up into "bevy_dev_tools" and "bevy_dev_tools_widgets" or something, eventually.