Define and document a minimum hardware spec
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 161
Description
After going through a huge number of issues, it's surprisingly common for users to find that Bevy is crashing due to unsupported hardware or is running exceptionally slowly due to poor hardware support of our algorithms. For example, https://github.com/bevyengine/bevy/issues/11133 and #10581. targeted a mobile GPU that is over 10 years old now.
We should define a common minimum requirement hardware spec. Perhaps informed by metrics like the [Steam Hardware Survey](https://store.steampowered.com/hwsurvey/Steam-Hardware-Software-Survey-Welcome-to-Steam). This should allow us to define a reasonable floor for what the engine can support.
These requirements may need to evolve over time as we add new features that may be hardware reliant. GPU-driven rendering is one potential example of this.
Other external examples:
* Unity outlines a minimum set of hardware requirements for both their editor and runtime https://docs.unity3d.com/Manual/system-requirements.html
* Unreal does too: https://docs.unrealengine.com/5.0/en-US/hardware-and-software-specifications-for-unreal-engine/
* Godot does too: https://docs.godotengine.org/en/stable/about/system_requirements.html
Contributor guide
Assessment
This issue has not been assessed yet.