TextureAtlas usage | Bevy | Page 1

smoky gulch Oct 16, 2022, 12:36 PM

#

In my previous non-Bevy OpenGL projects, I always extensively use texture atlases for almost everything to increase performance (since the glDraw* methods are relatively really slow). But when I look into Bevy codes, most of the codes and external crates directly use Image, and even when they use TextureAtlas-es, it's really minimal (benimator for example, uses a single TextureAtlas for individual animations).

What's the reason behind this? Won't it be much more performant if more sprite renderings are batched? And does the performance cost really matter in Bevy (or wgpu, I guess)?

ocean sundial Oct 16, 2022, 12:55 PM

#

This is likely just the result of prioritizing ergonomics and ease of implementation over performance

#

A lot of these are early crates and jam games

smoky gulch Oct 16, 2022, 1:10 PM

#

Well, ... i guess. would the performance matter on most devices though?

ocean sundial Oct 16, 2022, 2:03 PM

#

Depends what else your game is doing! And which devices

#

On mobile, it might

smoky gulch Oct 16, 2022, 2:04 PM

#

ah, okay

smoky gulch Oct 20, 2022, 2:56 PM

#

actually, https://github.com/bevyengine/bevy/blob/b995b4662a9481e8d6fd984b2d2fd02e1c2d1a5d/crates/bevy_sprite/src/render/mod.rs#L226-L289 seems promising

GitHub

bevy/mod.rs at b995b4662a9481e8d6fd984b2d2fd02e1c2d1a5d · bevyengin...

A refreshingly simple data-driven game engine built in Rust - bevy/mod.rs at b995b4662a9481e8d6fd984b2d2fd02e1c2d1a5d · bevyengine/bevy

#

actually, wait, the sprite.wgsl file doesn't use texture arrays (aww) so it can only render 1 image at a time

#

meaning each Sprite components aren't batched, presumably

#TextureAtlas usage