6beb4634f6
Since the new renderer, no frustum culling is applied to 2d components (be it Sprite or Mesh2d), the stress_tests docs is therefore misleading and should be updated. Furthermore, the `many_animated_sprites` example, unlike `many_sprites` kept vsync enabled, making the stress test less useful than it could be. We now disable vsync for `many_animated_sprites`. Also, `many_animated_sprites` didn't have the stress_tests warning message, instead, it had a paragraph in the module doc. I replaced the module doc paragraph by the warning message, to be more in line with other examples. ## Solution - Remove the paragraph about frustum culling in the `many_sprites` and `many_animated_sprites` stress tests |
||
|---|---|---|
| .. | ||
| bevymark.rs | ||
| many_animated_sprites.rs | ||
| many_buttons.rs | ||
| many_cubes.rs | ||
| many_foxes.rs | ||
| many_lights.rs | ||
| many_sprites.rs | ||
| README.md | ||
| transform_hierarchy.rs | ||
| warning_string.txt | ||
Stress tests
These examples are used to stress test Bevy's performance in various ways. These should be run with the "stress-test" profile to accurately represent performance in production, otherwise they will run in cargo's default "dev" profile which is very slow.
Example Command
cargo run --profile stress-test --example <EXAMPLE>