Hello!
When I open the demo on the main page, it always show this “No mapping …” error, and I can’t close it or interact with anything.
I have tried open it with different browsers: Chrome, Firefox, Edge, … All of them show the same errors as below.
This is a gamepad related error, but I’ve never seen anyone have it so not sure what’s up. I remember at some point a version of Firefox had a weird implementation of gamepad API that caused bugs but I fixed it back then.
Did you have / not have a gamepad plugged when you tried it? Or multiple ones or ones with different buttons/axis than normal? I’m not sure what could be causing it without more info.
You can also open browser devtools on that page (right click and inspect) and look in the console to see what errors it says and post them here
Hello there! Just got the same issue, here is the stacktrace:
chunk-LMGEWYT7.js?v=c8068287:27753 No mapping found for axis 5
| se | @ | chunk-LMGEWYT7.js?v=c8068287:27753 | |
|---|---|---|---|
| mapAxisToGamepadButton | @ | chunk-LMGEWYT7.js?v=c8068287:23010 | |
| undefined | ---- | ---- | ---- |
| mapAllAxisToGamepadButtons | @ | chunk-LMGEWYT7.js?v=c8068287:23015 | |
| undefined | ---- | ---- | ---- |
| updateAllNarratButtons | @ | chunk-LMGEWYT7.js?v=c8068287:23042 | |
| undefined | ---- | ---- | ---- |
| updateGamepad | @ | chunk-LMGEWYT7.js?v=c8068287:22978 | |
| undefined | ---- | ---- | ---- |
| update | @ | chunk-LMGEWYT7.js?v=c8068287:23134 | |
| undefined | ---- | ---- | ---- |
| (anonymous) | @ | chunk-LMGEWYT7.js?v=c8068287:22973 | |
| undefined | ---- | ---- | ---- |
| (anonymous) | @ | chunk-LMGEWYT7.js?v=c8068287:22561 | |
| undefined | ---- | ---- | ---- |
| emit | @ | chunk-LMGEWYT7.js?v=c8068287:22561 | |
| undefined | ---- | ---- | ---- |
| t | @ | chunk-LMGEWYT7.js?v=c8068287:22575 | |
| undefined | ---- | ---- | ---- |
It started to show up randomly after running pnpm install while trying to debug a build issue. No gamepads are attached at all. The chunk file in question (referenced in the stack) is located under node_modules/.vite/deps. The issue reproduces in Firefox and Chrome. Happy to provide any extra details that may be useful to you. For now, I have just removed the error from the narrat dist script in question to allow further work.
I think I will just remove the error yeah. I don’t know what is making some systems return so many axis (could it be VR support or something?), but ignoring them is probably the best thing to do
1 Like
in the interest in helping you figure this out, here’s what i’ve got! i set-up narrat a couple days ago and also got this error. i use firefox and at the time had a ps5 pad and a fight stick plugged in.
specifically i got this error when opening the localhost link in the get-started section. i got it to work by just telling powershell to open a browser up (o + enter).
after reading this post i just tested disconnecting my controllers and restarting the server and then the link works just fine. not sure if any of that information is new, but there it is! hope this helps the devs or anyone checking the forums in the future for a workaround (workaround in bold).