And here’s another example that @shakao made on how to use it to make shadows for sprites
warning: the more of the screen you shade, the slower your game will be! that GIF above runs at 15 FPS on my pygamer and it only has two sprites. To make your game faster, use shaders lightly and use rectangles where possible (they are much faster). Also, avoid double-shading the same area.
If I set a shader sprite to be invisible, will it stop “shading” so that it will use less resources? Or can you add a block to turn shading off for a particular shader? (So it disappears, but I enable shading, then it would be right back there?)
@UnsignedArduino oh boy, sorry for the super late response but an invisible shader sprite does prevent it from using more resources. If you don’t see the shader effect, it isn’t happening.
@mmoskal would this extension work well on a Kitronik Arcade???
I’m asking in relation to the Biggest Game since we want to use @kwx’s Space Rocks 3D, which can plummet the FPS alone, so I’m wondering whether shadows will break the game.
Shadows will probably set your Meowbit on fire if you pair it with the his space rocks 3D game. Or just won’t load because of insufficient memory. The Meowbit is already pretty tight compared to the PyGamer and PyBadges.
The Kitronik Arcade uses the same MCU as the Pygamer I believe, so it should be more powerful than a Meowbit. That being said, the best way to test these things usually is just to try it out!
Anyways, I can bet that the FPS on something even as great as the Arcade would plummet to a downright 10-20! I think that the Arcade is the best piece of hardware for MakeCode Arcade right? If so, that means that there needs to be a version 2!
