Open johnryan465 opened 1 year ago
I'm a complete typescript noob and since the code to bind a compute shader output to a canvas is substantially different from that of a classical render pipeline, I never had it in a form where it's easy to switch between the two. Let me know if you're interested, I can open a repo where the compute shader lives in a stale branch and you can try it out and integrate in here if you have the time.
I am wondering if adding ThreeJS as a dependency to this project would help simplify or avoid having to re-implement the wheel for certain things.
I'm a complete typescript noob and since the code to bind a compute shader output to a canvas is substantially different from that of a classical render pipeline, I never had it in a form where it's easy to switch between the two. Let me know if you're interested, I can open a repo where the compute shader lives in a stale branch and you can try it out and integrate in here if you have the time.
I'm quite interested to try to merge the two if needed. Implementing such things are completly behind my scope but a typescript refactor may be in my range ^^. This code base is by far the most organize yet available
It is mentioned in the readme that a compute shader implementation was written and had lower performance. It would be nice to be able to have both implementations in the repo, perhaps with a launch flag to select the implementation.