gl_FragColor = texture2D(tex, uv);
http://caa1211.github.io/webOAcard/?m=castle
do anyone know any similar project? or some reference about the math behind this?
frameCount instead of tick in the default context variables, even though that seems to have been changed back in 0.9.0 or so, and it also still lists deltaTime which no longer exists. are the docs on regl.party not kept in sync with those in the repo?
frameCount seems to have been replaced quite some time ago
Heya, in case anyone is still here - I'm trying to apply some blur passes to a texture.
I have a command that has:
{
...,
framebuffer: regl.prop('framebuffer' as never),
viewport: regl.prop('viewport' as never),
}I do N passes and each time i generate two draw calls:
return [
hBlur(
cubeUVRenderTarget.texture,
pingPongRenderTarget.fbo,
lodIn,
lodOut,
sigma,
'latitudinal',
poleAxis
),
hBlur(
pingPongRenderTarget.texture,
cubeUVRenderTarget.fbo,
lodIn,
lodOut,
sigma,
'longitudinal',
poleAxis
),
]for (let i = 1; i < PARAMS.totalLods; i++) {
blurCommand(getBlurDrawCall(cubeUVRT, pingPongRT, i))
}And for some reason this is able to read the cubeUVRT buffer only every other time. Like, from these totalLods passes, every command renders (i can fill my final texture with color) but the ping pong thing doesn't work, it just reads black.
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})
1 reply
