Dragoș Tiselice
Dragoș Tiselice
@yisibl, it's fixed on Chrome 112+ and Firefox 114+. I updated the issue. There's still an issue on Safari though.
The issue on Safari seems to be caused by a discrepancy in the wasm128 SIMD implementation. The "visualize partial updates" button also seems to be broken.
Thanks for reporting this. This is a known limitation on GPU: if too many layers overlap in one pixel, it will create artefacts. Right now, we don't have a way...
The number of layers that can overlap inside of a tile is not limited, only the layer that cross tile borders. These are limited by the [queue](https://github.com/google/forma/blob/main/forma/src/gpu/painter/paint.wgsl#L26) that's passed from...
For now, the queue will always be 128. Even when not enough memory is available, the shader should be able to simply spill this to global memory. Once the error...
That makes sense. This is definitely a use case we care about. I think the global memory spill approach would basically solve this issue almost completely and we should focus...
Thanks for reporting this. I'll take a look at the high memory consumption and report back.
Part of the issue with the memory usage is the large atlas size for textures (4096 x 4096), but also the format, which is rgbafloat16. This easy to improve upon,...
About the cropping, I don't think I understand the issue. If you're trying to crop the geometry that lies outside of the screen, this should be something we optimize anyway....
I merged #29 which should improve performance when zooming in. We can slowly improve on the other issues as well.