runs on any GPU – even in the browser

Seems pretty clickbaity and dishonest when that's just what webgl and webgpu means. Just say webgpu.

Also the roughness doesn't apply to the environment map.

If you click into the code you can see that it depends on `wgpu`, which is a wrapper that uses whichever native API would be appropriate for the platform you're working with. If you run the native compiled version you won't be using WebGPU.

	▲	CyberDildonics 3 days ago \| parent [-]
		wgpu is based on webgpu, what is your point here? The title implies that the reason this exists is because it "runs on any gpu, even in the browser". People have been making raytracers using gpu apis in the browser over and over for the last decade. That would be like someone claiming their program "multiplies huge matrices using SIMD" and then wrapping eigen. Why make a claim that is just happening because you call the same library as everyone else?

▲

yunnpp 3 days ago | parent | prev [-]

I think you're getting lost in the weeds there. I do not see malice in the claim.

The irony is that it does not actually run on my GPU, nor much of other people's, judging by the comments. I don't know where people get this idea that WASM and WebGPU are the holy grail of portability; they are the opposite and the whole ecosystem is a fucking disaster. No offense to OP, though; I can understand the temptation to target that platform.

Anyway, I left more positive feedback in another comment.

▲

CyberDildonics 2 days ago | parent [-]

Are you sure you aren't the one "lost in the weeds there"? What you're talking about has nothing to do with anything, it's a matter of software updates.

▲

yunnpp 2 days ago | parent [-]

Do you have a technical background?

WASM offers a false sense of portability only because it is basically useless. It's not even POSIX-compliant (WASIX is a WIP). By the time it becomes useful, they will have realized they have re-implemented Java. And even then, it'll only offer a half-assed subset of functionality that you'd get from going native.

WebGPU is a similar story. It's based on a decades-old API, lagging severely behind present-day Vulkan. And it's not even well-supported across browsers. Again, you'll get better portability and more functionality from just going native.

To suggest that all of this is a "sofware update" away seems very naive. The kind of thing somebody without a technical background would suggest.

	▲	CyberDildonics 2 days ago \| parent [-]
		Do you have a technical background? Do you? WASM offers a false sense of portability only because it is basically useless. That doesn't have much to do with this project or what I talked about. It is a bytecode meant to be JIT compiled. It has nothing to do directly with supporting an API, and none of this has anything to do with running on the GPU. lagging severely behind present-day Vulkan. So what? What does this have to do with anything? What point are you trying to make? And it's not even well-supported across browsers. It's new and already works in chrome. What is your point? To suggest that all of this is a "sofware update" away seems very naive. The kind of thing somebody without a technical background would suggest. There is no substance here, just you saying "nu uh". My recommendation, as someone with a technical background, is that you try it with chrome. It's easy to install, just search for install chrome then download the executable, then double click. I think you misunderstood everything that I was saying though, your reply doesn't seem to connect to the idea that using an API then making the benefits of the API the unique aspect of the software is a bad idea.