3 ms·
As I recently started playing with WASM as well for my emulator, it's fun to see the pitfalls I run into are the same for everyone, like the AudioContext being
by Aissen 3y ago
As I recently started playing with WASM as well for my emulator, it's fun to see the pitfalls I run into are the same for everyone, like the AudioContext being forbidden without user interaction, forcing me to add a "Start" button.
Gamepad support on browsers is abysmal as well. It works, but the buttons are not interpreted properly leading to the wrong button being reported (but the OS reports the correct ones!), even for the most standard xbox controller. It seems like the wheel that is sdl gamecontroller db will have to be reinvented on the browser again... while making it a bit harder since the browser might not tell you the exact gamepad model (it would add fingerprinting bits).
- AlecSchueler 3y agoInteresting that the pitfalls for developers are both wins for the end user. I don't want my browser to know what kind of peripherals I'm using or be able to play audio I didn't explicitly ask for. How would something like the sdl gamecontroller db work in this context?
- Aissen 3y agoI tend to agree for Audio; this is why I did write the Launch button. For the Gamepad API, if the browser does not want to expose model information, it should either: - expose the buttons as sent by the OS, and let the OS to the mappings - or build its own internal game controller db for mappings. Right now it's doing neither, and that's an issue.