Bernhard Schelling

I think this was fixed in 1c7ad4f. It should get released soon, I don't know when yet though. Some big changes since the last release. Controlling something with a gyroscope...

Ok, looks like there's this part in the libretro code interface ```c /* Id values for SENSOR types. */ #define RETRO_SENSOR_ACCELEROMETER_X 0 #define RETRO_SENSOR_ACCELEROMETER_Y 1 #define RETRO_SENSOR_ACCELEROMETER_Z 2 #define RETRO_SENSOR_GYROSCOPE_X...

Problem I can see is that it would need a lot of special options. There are 6 axis available (gyro XYZ and accel XYZ). How to set which one does...

I really have no idea how it could be happening. Somehow an unknown key arrives inside the emulator code at a point where that really shouldn't be happening. I can...

All these cases you mention end with ``` [libretro WARN] [DOSBOX] Crash: Unsupported key press ``` or ``` [ERROR] [Environ]: SET_MESSAGE_EXT: DOS crashed: Unsupported key press ``` in the log?

To maybe figure out what that certain mapped button on the Razer Naga Pro does I wrote a simple input event logging tool. Can you try to do this for...

Thank you! So it is quite similar to what I get from pressing just a regular volume up keyboard key. One more thing, can you check in RetroArch what you...

Interesting. I can't reproduce it by faking an input event that matches what your mouse is emitting so I'm still a bit lost. I just committed the only idea I...

Ah, now it all makes sense 😅 https://github.com/libretro/RetroArch/pull/16502 This happened 4 months ago and it was what extended the range of possible key events which then all had the possibility...

This fix is now released in the newest version [1.0-preview1](../releases/tag/1.0-preview1) available here and from the RetroArch online core downloader, so I'm closing this issue.