Exa, never surely complete

 messing about in pixel composer again

#pixelcomposer

Feb 18 at 9:36pmWeb
Show threadExa, never surely completeFeb 18
 closeup on the outputs
Show threadExa, never surely completeFeb 18
 i love how pixel composer handles arrays. if you pass an array into most kinds of node, it just runs the node once for every entry in the array and outputs an array in the same order. so you can do a lot of repetitive processing without duplicating flows
Show threadExa, never surely completeFeb 18
 this even applies for the file export node. there being one node for each direction is a convenience for visualization, it is not load-bearing
Show threadExa, never surely completeFeb 18
 the name of the file to be exported is itself a node input
Show threadExa, never surely completeFeb 18

 if the input surface and the input filename are both arrays, it just. matches them up. no fuss

i love this program

Show threadExa, never surely completeFeb 18
 nvm in order to make spritesheets i need to create spaghetti
Show threadExa, never surely completeFeb 18
 NOPE skill issue use Render Spritesheet instead of Stack
Show threadExa, never surely completeFeb 18
 yay
Show threadExa, never surely completeFeb 18
 Render Spritesheet is like Cache Array + Stack but with better behavior and also only one node
Show threadExa, never surely completeFeb 18
 and ingame
Show threadLykrastFeb 18
@exa oh that's so cool
Show threadLykrastFeb 18
@exa