noclip.website VS naga

I know this is definitely not what you’re talking about because it’s a website and not a book but it’s a link always worth sharing https://noclip.website/

As far as I know, yes.. Besides simple differences like register allocation, it's difficult to prove that your code behaves the same as the target if its nonmatching. It's also just really satisfying when you get a match.

When doing standard reverse engineering, you might use something like Ghidra or Hex-Rays. This is what the developer of noclip.website [1] did to reimplement a lot of Mario Galaxy code, such as enemy AI.

[1] https://noclip.website/#smg/AstroGalaxy

I don't know where to get what they used in that video, but the closest thing I could suggest is a site called "noclip" ?

You might also be interested in: https://noclip.website/ (not quake maps)

I also know https://www.halospawns.com/app used to have quake maps (dm6 at least), but can't find it now.

This isn't Ross's "Dream Software", but I find it somewhat related - at least its output. Check out noclip's website here.

https://noclip.website/#snap/1A;ShareData=AUsPn92;%5eVT:h=19... , or to hook up the first one to the second (although the system to signal between distant pokemon, which it probably uses, is mostly implemented). There are a few other instances of things that are supposed to be spawning conditionally which aren't handled yet, like extra lapras in the beach.

I'll leave an article from Pikipedia with a demonstration gif, plus a picture of the whole title screen from The Models Resource and a small comparison I made myself, using noclip.website.

That wouldn't have been all that different from WGSL though, the most important thing is that whatever WebGPU uses for its shaders can be translated to and from SPRIV (and WGSL does that too (e.g. via https://dawn.googlesource.com/tint and https://github.com/gfx-rs/naga).

Hey all, wanted to put this link in here, where I'm proposing changing the API for errors in naga, so Naga can take ownership of error presentation and actually Make Shader Compilation Messages Comfy™: https://github.com/gfx-rs/naga/issues/2317

EDIT: There is also naga but it does not take HLSL as input: https://github.com/gfx-rs/naga but you can use DirectXShaderCompiler to compile to SpirV, then use naga to compile to Metal.

And it seems that naga https://github.com/gfx-rs/naga Already has a working front/backend for wgsl.

This is basically Ray Tracing support in Blade. So far, only ray queries are supported. Unlike prior work on ray tracing in Rust, this is original due to all shader code being WGSL, see the Naga PR.

There's a compiler that can translate from WGSL to SPIR-V called naga. Having such a compiler is essential, since WebGPU is planned to use WGSL and browsers are expected to implement rendering via Vulkan (and probably Metal and DX12).

Not sure about on the CPU, but naga is a shading language transpiler you can write custom front/backends for.

The spec docs are actually pretty useful https://www.w3.org/TR/WGSL/ besides that I was using naga's tests for reference https://github.com/gfx-rs/naga/tree/master/tests

For cross-platform support look at WebGPU and Vulkan (e.g,: [0] [1]. Essentially, you would need to write the func in WGSL or GLSL, HLSL or MSL. Each of these can be cross-compiled to SPIR-V (what Vulkan needs) with cross-compilers such as spirv-cross and naga.