Add mesh tag feature to release notes.

[tychedelia]

No description provided.

[JMS55]

First paragraph reads a little weird to me.

Users can already have per-material-instance data (that's kinda the whole point of AsBindGroup).

However separate material instances breaks instancing of course...

I think we should explain it like that, and also probably talk about how the material/AsBindGroup API is kinda flawed and doesn't support these kind of workflows atm, and that we're brainstorming how to improve it.

I feel like mesh tag might end up being more of a temporary fix long run, but who knows.

[tychedelia]

Users can already have per-material-instance data (that's kinda the whole point of AsBindGroup).

I'm not sure I understand. Semantically to me, an instance of a material means a concrete entity. Per-instance data in that sense would be per-entity. AsBindGroup allows defining the data for the entire class of instances.

[JMS55]

Generally we use instance to mean a bevy entity, and material instance to mean a Handle.

[superdump]

Yeah, we generally consider entities to be instances of drawn things, material instances would be instances of material assets, and we unfortunately sloppily refer to Frankie mesh entities as mesh instances. Per instance data is used exclusively for per drawn thing instance data though. I’ll now actually read the PR and comment more directly.

[superdump]

Maybe just change it to ”all instances using the same material”.

[tychedelia]

I do understand how there might be some confusion in terms of an instance of an asset type being a "material instance", but will note that we use "material instance" in our own code, e.g. here bevyengine/bevy#18734, to refer to collections of entities rather than an instance of an asset. I'll try to make it more clear.