slows down other rendering

[gilescope]

Maybe this is expected as this is new but if I add in

	app.add_plugin(IndirectRenderingPlugin)
          .add_plugin(BasicMaterialPlugin)
          .add_plugin(CustomMaterialPlugin)
          .add_plugin(TextureMaterialPlugin);

to an existing app with lots going on then the frame rate drops right down from 90-100fps to 1-2 fps. This is without adding in any instanced entities. Any thoughts on what's going on? Would love to try out the instancing but ideally don't want everything to be rendered that way.

[ProfLander]

I've not dug in and profiled yet, but this is almost certainly down to some of the internal queries not being filtered aggressively enough - all of my development / testing has been instances-only so far, so chances are that your non-instancing-relevant entities are getting incorrectly considered by one or more of the new systems.

[gilescope]

Tbh I ripped out bevy and did the wgpu instancing calls myself. Frame rate went up from 60 on a good day to 660 fps which is more like it because now I can do it all in a handful of instanced indexed draw calls. For what I needed I guess bevy was overkill.

…

On Wed, 22 Feb 2023 at 19:01, Shfty ***@***.***> wrote: I've not dug in and profiled yet, but this is almost certainly down to some of the internal queries not being filtered aggressively enough - all of my development / testing has been instances-only so far, so chances are that your non-instancing-relevant entities are getting incorrectly considered by one or more of the new systems. For now, it's best to consider this repo as not production ready. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGEJCDXBOHSY2Q4SRG3DK3WYZPAVANCNFSM6AAAAAAQBYX23Q> . You are receiving this because you authored the thread.Message ID: ***@***.***>