2 kids now and not much time
Thanks for responding! I noticed it's been a bit slow, but it seems like it's still active?
I started working with a framework called WebViz which relies on regl under the hood, it seems to be really popular in robotics.
(at least in san francisco heh)
For any future readers, i came across this:
https://stackoverflow.com/questions/69250608/is-my-webgl-fbo-color-attachment-being-cleared
I'm still not actually sure what caused it, but basically i was using React.useState to store a texture, the moment i pass the "raw" texture reference (whatever is the result of calling regl.texture() the texture would be reset. Took a while to realize that calling this function will "reset" the texture to 1x1.
Basically:
const [texture, setTexture] = useState(null)
....
const myTexture = regl.texture()
//barfed
setTexture(myTexture)
//worked
setTexture({myTexture})
pailhead: yeah, it's still active but not my main priority now. things are pretty stable so doesn't require as much attention
But you might find regl-project/regl#561 interesting
1 reply
I feel like the problems a regl-like API would solve for webgpu are slightly different. for webgl, its goal is basically to manage statefulness. For webgpu, a lot of the API already looks a lot easier to manage, e.g. https://github.com/austinEng/webgpu-samples/blob/e4f0831a56454dc78a62cb4444ea968d1547d45c/src/sample/instancedCube/main.ts#L44-L97
but there's also a lot of low level control around pipelines and encoders. I'm not really familiar enough with it to understand exactly the ways in which you might be able to abstract those concepts so you can use them but so your code isn't dominated by boilerplate
its a thing i would love to have, but not sure if i have enough time to build it right now
A little overwrought maybe, but my first module in a long time: https://github.com/rreusser/regl-gpu-lines
tl;dr you provide a vertex and a fragment shader.
#pragma statements in the vertex shader specify attributes and varyings as well as functions for computing line geometry (vertex position and width). It sets up the correct attributes, strides, etc and handles all the other details
Feels overwrought, but I'm pretty happy with how usable it actually seems in practice
seems very handy!!
Still making progress! Reworked the geometry and got the varyings unskewed by computing the projected offsets—so that you can do dashes!
Reminds me of Slimey
@rreusser You may enjoy this paper from Nicholas Rougier, about adding dashes to gl-rendered lines https://jcgt.org/published/0002/02/08/paper.pdf . Not sure if it's the same approach you're using
i love both of these ideas, so many potential applications