New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graphical output canvas is affected by a separate kernel #802
Comments
It seems that kernels created from the same GPU instance shares the same canvas. If you want different canvases then you'll need to create another GPU instance for the other kernel. const gpu2 = new GPU()
const renderKernel = gpu2.createKernel(...) |
i've been through the same problem. and i don't want a second canvas, i really need different-sized textures. my workaround is to set canvas.height and canvas.width explicitly to the correct values after calling the other kernels for the first time. |
What is wrong?
It seems as if one kernel's output size can affect the size of a canvas created by another. This means that the canvas created by a kernel is larger than should be expected.
Where does it happen?
GPU.js running in browser in Chrome on a Mac (WebGL2 enabled)
How do we replicate the issue?
The output looks like this:
You can see that the canvas is 64x64 pixels, the size of the
imgKernel
but the red section is 32x32 inside that which is the output ofrenderKernel
despite the two having no relationship other than both of them are called.How important is this (1-5)?
5 This is a pretty limiting bug if you want to use multiple kernels.
Expected behavior (i.e. solution)
Should show a 32x32 red canvas as far as I can tell.
Other Comments
Thank you for your time looking at this.
The text was updated successfully, but these errors were encountered: