Obsessively exploring simulations, graphics, machine learning & AI. This is my demo space & devlog for side projects in WebGPU, WebGL, Metal & MLX/CUDA.
Real-time @threejs meshlet #pathtracer journey in the ruins for milestone 3.
Better caching & auto-exposure + less smearing. Walk controller. Pop-in needs work. Neural denoiser still v0.5.
Running in the browser on my M1 Pro.
Showcase to follow.
#WebGPU#gamedev#raytracing
@garrettkjohnson@threejs This is how I’m doing it as well. Light tree with cleanup is actually pretty fast. Though I’m experimenting with a few other things as well. Had some recent regressions to fight while adding features.
@YuanmingH Awesome to bring three to desktop/mobile but its not browser based, right? I thought it was hardware raytracing for devices that support that in a custom shell or app using a custom build or mod of threejs?
It's a new age of game development! This is the Unreal Engine 5.9 preview, consisting of huge improvements to AI acceleration ported from unfinished Unreal Engine 6, plus entirely new support for play inside web browsers.
@dangreenheck@victor_vibing I find that all the names for things often come from some kind of historical sense of the thing & usually depart from that original meaning. We don’t need to get metaphysical about it, just mentioning that it’s confusing 🙂
@dangreenheck@victor_vibing meshlets are often a part of the cluster pipeline. It’s confusing because of the way we shorthand things when we speak colloquially about these things.
I'm building a open source little physics lab in @threejs to experiment with viscous and non-Newtonian fluids.
First experiment: runny mud. Playing with surface deformation, flow, and object interactions.
Still a work in progress, but it's getting there! #threejs
@mrdoob This is also one of my secrets I haven’t mentioned yet. Most of my demos are huge files, but I have a whole procedural recreation pipeline that enables endless remixing & tiny files sizes for the same content. But it takes a lot of time to generate. Awesome work!
@PashaIGooD @threejs This was a little bit of my point with the path tracer too. I spent forever using the latest ‘tricks’ & methods to avoid the thing that you’re ’not supposed to’ do that I realized it was costing more & making it harder than actually just figuring out a real brute force approach.