awsm-web VS beatmapper

I wrote an opinionated WebGL wrapper in Rust/WASM here: https://github.com/dakom/awsm-web

The idea is that it does more cacheing of things like uniform locations and such so you do very fast in-memory lookups in WASM without hitting the JS Api as much.

In the future this will be obsolete since WebGPU has a more optimal API to begin with, and Rust/WASM won't need to go through the JS layer due to "interface types"

There are tools out there that do a half decent job of converting songs automatically. I use https://beatsage.com for example. This creates a basic map and quality varies wildly, usually you'd want to spice it up and do some fine tuning with a map editor like https://beatmapper.app

After you download your songs from Beatsage, upload them into beatmapper. (Click on "import existing map").

I've built "vanilla" Three.js projects, and worked with react-three-fiber. It is incredibly useful.

Having a new set of "primitives" that map to three.js objects and being able to render them in a React application makes so many things easier. It's also just way less code to write compared to standard three.js.

RE: animation performance, I haven't had any issues with it. I presume either they're doing a bunch of optimizations, or the concerns are greatly exaggerated. You can check out an app I built using it if you want some proof: https://beatmapper.app/

I use a web-based map-making tool called Beatmapper, and there's some great tips and tutorials on the Beat Saber Modding Group wiki!

You can try BeatMapper, but it might not turn out well for you w/o a pc.