-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
Add GPU.sb3 extension #1762
base: master
Are you sure you want to change the base?
Add GPU.sb3 extension #1762
Conversation
It fails to get WebGPU adapter |
What does the extension do |
what browser are you on, and what os |
it's like pen+ but with numbers instead of colors and it all happens at the same time |
Chrome, Android, Why did you ask? |
That would be more hard but ok |
WebGPU is experimental and doesn't work on some devices. Seems like android wouldn't be supported based on webgpu.io. |
Oh ok |
well this is rough, make it more readable. |
that's fair, I will work on that |
I'm excited to see the extension coming out as it means that we could now perform GPGPU calculations on TurboWarp, meaning that 3D applications will be blazingly fast and AI is now possible. |
this isn't really intended for 3d, I think vertex/fragment shader implementations such as those in webgl would be far faster than anything custom made |
added a bunch of comments, removed profanity, and I think I reordered stuff in a way that makes more sense but I don't remember |
i have finally updated documentation to add the 3 new blocks |
what the sigma why lint fail |
important: this commit makes pretty much all the webgpu blocks async, so there's a 1 frame delay when they are run or something like that
The latest commit(84c7b87) adds error handling in case the device was lost or the project was run before it was finished getting the adapter+device. this makes pretty much every webgpu block async, which is pretty cringe. I could alternatively:
Should I keep it as is or do one of the above? |
chose the last option as suggested |
This adds blocks to use compute shaders in a Turbowarp project. This uses WebGPU(which is experimental!), and only supports compute shaders. From what little research I've done it seems like it would be a pain to add any of the other types, so I'm not doing that.
Notes: