You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently experimenting with a couple ways of writing shaders in TypeGPU, but no matter which path we take, incorporating that API into existing WebGPU projects is essential.
Nowadays, WGSL shaders are either written in template strings or imported from a .wgsl file.
Use cases:
A helpful TypeGPU library exists, and somebody wants to use it in their vanilla WebGPU project.
Somebody wants to start writing their shaders in a type-safe way, incrementally.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are currently experimenting with a couple ways of writing shaders in TypeGPU, but no matter which path we take, incorporating that API into existing WebGPU projects is essential.
Nowadays, WGSL shaders are either written in template strings or imported from a
.wgsl
file.Use cases:
Approach 1: Typing a whole module at once
Approach 2: Typing each function individually
Beta Was this translation helpful? Give feedback.
All reactions