Since @2DArray is working on a pico8-to-burst (lua-to-HPC#), I borrowed his parser so I could join the fun.

Source

URL: https://x.com/mike_acton/status/1673189328330317824
Author: Mike Acton (@mike_acton)
Posted: 2023-06-26 04:39:56

Thread

1/ @mike_acton

Since @2DArray is working on a pico8-to-burst (lua-to-HPC#), I borrowed his parser so I could join the fun. Let me present my first pass on pico8-to-shadertoy (lua-to-glsl):

Branches: 2023-06-29-eigenbom-oh-nice-id-love-to-bridge-the-gap-between-my-lua

2/ @mike_acton

Another example:

3/ @mike_acton

4/ @mike_acton

And @2DArray’s goblet tweetjam:

5/ @mike_acton

6/ @mike_acton

Fixed a couple of the pico8 specific fiddly bits and it matches the original much better.

Branches: 2023-06-27-tom_forsyth-am-i-right-in-thinking-this-is-running-the-entire

type	archive
source	twitter
date	2023-06-26
tags	archive, twitter, mike_acton
description	Since @2DArray is working on a pico8-to-burst (lua-to-HPC#), I borrowed his parser so I could join the fun.

Threadwell

Explorer

Recent Notes

DemetriSpanos

NOTimothyLottes

bonzajplc

Since @2DArray is working on a pico8-to-burst (lua-to-HPC#), I borrowed his parser so I could join the fun.

Source

Thread

@mike_acton @2DArray Oh nice, I'd love to bridge the gap between my lua mesh generator and vertex shader while staying in lua.

@mike_acton Am I right in thinking this is running the entire Pico8 program at every pixel and then discarding all but the specific pixel it cares about? This is...