François Mockers

> Maybe we should put the flight helmet into the lighting scene. Or just put together a test scene which has a whole bunch of features enabled all at once...

We re trying to avoid shellscripts to be cross platform. Could you add it to the ci rust script?

probably related to https://github.com/bevyengine/bevy/issues/13208

how the example looks like: https://user-images.githubusercontent.com/8672791/195031790-b3a0c314-32f1-4c58-bb6b-c2c868a2a2ed.mp4

Googling the error code or error message seems to be either about a port being already used, or a process needing increased privileges from Windows... I don't have access to...

> I think the potential confusion for typical or new Bevy users can be avoided with clear wording. The website already has a link to docs.rs, clearly labeled Bevy Rust...

Until Bevy has a way to adapt batch size at runtime, I'm not very confident in using `par_for_each` or `par_for_each_mut` in the engine

codes looks good in the loader, but the example could do with a lot more explanation of what's going on, why there is a custom attribute, how it's used, ...

Some of the features you added are already present in the default feature set: https://github.com/bevyengine/bevy/blob/e96b21a24a7fe17a64e52b7bba81e00145ea1756/Cargo.toml#L27-L40 Doesn't docs.rs use those? Otherwise https://docs.rs/bevy/latest/bevy/animation/struct.AnimationClip.html shouldn't be present as it's behind the `animation` feature

I still don't understand the point of this? Bevy pretty much doesn't have any public items that are behind features not already enabled by default. What does it change for...