Which OS/config is good on Raspberry Pi 4

[s-mayrh]

I have a simple small game based on bevy 0.10.1. I was developing it on my Intel Atom (see below) before, and I tried it now on my Raspberry Pi 4 running Twister OS (Raspberry Pi OS/Debian 10 ARM 32 bit):

as you can see the game uses a lot of CPU even when idle (even with a blank project) and i have glitches when moving around (camera centered on player, everything else moves):

So I switched SD cards and tried a different OS, something more up to date with 64 bit ARM - Manjaro Plasma - a fresh install. The glitches are gone now and CPU usage of my game is lower:

but now my terminal is flooded with thousands of these while the game is running:

2023-09-01T20:15:21.966301Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT4)    
2023-09-01T20:15:21.966387Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT5)    
2023-09-01T20:15:21.966417Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT6)    
2023-09-01T20:15:21.966444Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT7)    
2023-09-01T20:15:21.967039Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT4)    
2023-09-01T20:15:21.967121Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT5)    
2023-09-01T20:15:21.967149Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT6)    
2023-09-01T20:15:21.967175Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT7)    
2023-09-01T20:15:21.967490Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT4)    
2023-09-01T20:15:21.967551Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT5)    
2023-09-01T20:15:21.967580Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT6)    
2023-09-01T20:15:21.967608Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 1 : GL_INVALID_OPERATION in glFramebufferTexture2D(invalid color attachment GL_COLOR_ATTACHMENT7)    

Do you know how to fix this?
is there an OS or configuration that works out of box with bevy for the Pi4?

(My only other machine I have is this Intel Atom Windows 10 one where I cannot use bevy 0.11 because of a bug with Intel graphics and I am stuck with bevy 0.10.1 for now (and it uses all CPU even when idle) - #8395 (comment) - in 3D also lighting/shadows are broken in bevy 0.11)

Sorry, I don't have "usual" hardware at home but I'm happy to help tracking down bugs if any of the issues are still unknown to you.

[s-mayrh]

some updates:

• vulkan drivers are missing by default on manjaro: vulkan-broadcom is needed to get rid of these errors
• having vulkan also means the glitches have reappeared. EDIT: also cpu usage went above 100% again
• the glitches seem a bit less pronounced using a wayland build (see https://bevy-cheatbook.github.io/platforms/linux.html#x11-and-wayland) in a wayland session
• while on windows (using my 1.44 ghz intel atom abacus) performance was ok and free of glitches, movement on the raspberry is way choppier although it's overclocked to 2 ghz (cpu) & 600 mhz (gpu). on this platform most of the glitches and choppiness could be reduced by making the player movement part of a system set running before that one that lets the camera follow the player, but it's still noticeable: parts of the player sprite flicker while moving like having horrible performance and no vsync. the raspberry gpu (broadcom videocore 6) shouldn't be that bad for moving sprites around in a 2d environment
• i'm still using bevy 0.10.1 because of this and that issue with my intel gpu on the atom, which hopefully get fixed in the future as this outlook seems promising.