In the needle.tools website, why do you need so many different scenes?

How can Needle Engine developers benefit from WebGPU in Chrome 113 when it drops? I see Babylon JS will have it fully implemented straight away.

by user 276719669878980608

When threejs has support for it :slightly_smiling_face:

Do you know if they are working on it? Any ETA you’ve heard?

by user 276719669878980608

They are working on it Commits · mrdoob/three.js · GitHub
Don’t know about ETA right now

they have some samples already on threejs but I’m not sure how far they are

I’ve back shelved some data visualization waiting on that to be available. Particle Systems don’t give me the interaction needed to populate data on hover, touch, click for the thousands of objects I need in the camera frustum, at any one time. :sob: .

by user 276719669878980608

Thanks for the point of direction to follow along! I’ll tell them to hurry up, Marcel says so. I’m sure that will push it along but good. :slightly_smiling_face: j/k of course. 8-D

by user 276719669878980608

We always want more. You know the drill. :blobaww:

by user 276719669878980608

Here are some examples too: three.js examples
You need the chrome beta 113 for it and maybe try to assign the WebGPU renderer (this.context.renderer = ...) :slightly_smiling_face:

Thanks! I just tested with Edge Canary as well, works. I shared with my team a status update. NE is our choice still over BJS. You guys just have a better end-to-end dev flow to launch in our opinion. We love the timely support you give here. Pretty impressive for a small team. (gaslighting off :-)). We’re still in testing phase. (read, I’m learning lol).

by user 276719669878980608

Thank you! Appreciate the kind words! :slightly_smiling_face: