Dave Pagurek
Dave Pagurek
@ksen0 because this splits tests into two steps, the regular tests and the webgpu tests, even though the webgpu ones aren't run, I think the change in test steps has...
@limzykenneth that'd be this I think! https://github.com/processing/p5.js/blob/d010b450f1215ad06080c9189e1789e5f4d78fb3/src/webgpu/p5.RendererWebGPU.js#L1926-L1938
Actually I'll have to give this a tad more thought, since it needs more than just the webgpu renderer -- it also needs basically everything else included in the webgl...
@limzykenneth I made an update to make `p5.registerAddon` stop early if it's been passed in the same function instance. It's not bulletproof but is maybe good enough for now. We...
Update: added a WGSL backend for p5.strands! This silly little demo is running this shader: ```js baseMaterialShader().modify(() => { const time = uniformFloat(() => millis()) p.getWorldInputs((inputs) => { inputs.position.y +=...
Update: filter shaders now work in WebGPU! also the base filter implementations are now in p5.strands so that we get both implementations "for free"
### Returning results I like the `.set()` idea! I'll take a crack at implementing that later. ### Renaming `get*` prefixes That is what it would look like, yes! ### Global...
I think using a mode does make the changes in `input`'s interpretation more consistent, e.g. how we interpret an angle number also changes based on a mode. Although because it's...
Yep go ahead!
@limzykenneth do you think there's anything more to do here or is this issue safe to close now?