You need a specialised program to split the processing power over multiple computers, and the thing you want to do has to support being split up over multiple computers. And I don’t think MakeCode on RPi will do that.
I think de should file a feature request for this.
@richard?
But who is gonna use it? If they implement it, I probably still won’t use it.
this is great
I think @UnsignedArduino is right- ‘stacking Pi’s’ would be hard for MakeCode to decipher, and also like @UnsignedArduino said, no one is really going to use 5-10 Raspberry Pi’s to just help with a heavy game
Use shader extension when you make mineshaft tilemap
Can you add a feature where you can change what color is darker than another? This would be useful if someone were to use a custom color palette
good idea! I should do that at some point. Need to figure out what the block for that should look like, though. Something like “set [pink] shade level [one] to [orange]” would be pretty tedious to use
I think some things have to be manually defined. Although I think you should make the shader enums poppable so you can add your own presets, and you can map each color in that shader preset so you can have as many as you want
it definitely would be manually defined, but it might be easier to use an image like this:
the problem with this approach is just that it would require documentation, since i don’t think i could communicate this in the space of one block. way easier to use though
in case it was unclear, that image has 1 column for each color and the colors get darker as you move down.
This could be useful for a lightening an image instead of darkening it
this might be possible if you add a plus button that allows you to change multiple colors
What about using the help button? It could pop out one of those pages where you could line out the docs for it.
there will be some major updates to this extension in the near future!
in particular, i moved the performance intensive code into C++ so it will be quite a bit faster.
here’s a preview, but don’t try using it yourself yet (this is a debug build of arcade):
also, that code should run on hardware! pygamer at least, meowbit might not have enough memory but that’s just because of the demo and not the shader code
I was just reviewing this the other day when I was experimenting with some colors, and I realized that this actually has repeating within it… (for example)
I thought that this might be another approach which would involve less redundancy
Here, you don’t need to define
yellow → orange → brown → purple → black
and orange → brown… black
separately because orange is included in the first “shader map” (that’s how I’ll refer to it)
As you can see I significantly reduced the number of columns needed here, since you can just recycle some maps for other colors (as shown in this simple diagram)
@Sarge that’s true, but i feel like there might be some color palettes where you could include a color in more than one ramp with different colors coming after it. For example you could have:
orange → red → brown
and in the same palette:
pink → red → purple
Hmm… maybe a block to toggle between using normal maps (your way) and compact maps?
You don’t have to include this obviously, I understand it might get a little complicated
Btw scaling is broken for shaders