Open Aeolus4444 opened 9 months ago
Re-tested with v135 on latest Windows 11 (Binary), Arch Linux (aur), and MacOS Sonoma [M1 Pro Macbook Pro] (Binary).
Rumble still only works on Linux SDL, Windows and MacOS SDL input works great, but no rumble.
I can't get rumble to work on v141 / Win11 either. I tried a Saffun N64 wireless in X mode, and an Xbox One controller.
What is supposed to be the purpose of assigning rumble to a button in the input UI? Is that what enables it in emulation?
ares allows different inputs to be mapped to the same emulated controller; on the N64 you could have the face buttons mapped on an Xbox pad, the shoulder buttons mapped to the keyboard, and the analogue stick mapped to a DualShock. When the emulated system wants to rumble the emulated controller, which real controller should rumble?
ares' solution is: whichever controller the "rumble" button is mapped to, is the one that rumbles.
Rumble does not work when using an OEM n64 controller and rumble pak through a raphnet adapter on windows
connect an OEM n64 controller and rumble pak to your computer through a raphnet adapter open ares choose SDL or windows as your input driver (reload driver if switching) configure your controllers buttons, sticks, and dpad in the input window configure rumble by setting any button (or stick direction? not sure if that also works) as the rumble option open a rumble enabled n64 game (I used f-zero x) play up to where rumble would normally trigger (bumping into a wall for f-zero) rumble does not work
rumble should work as well as it does on linux with sdl (udev seems to have the same problem as windows)
tested with ares v134 binary on Windows 11 Pro x64 23H2 22631.3007 also tested with ares v134 built through the aur on Arch Linux (Kernel 6.7) KDE Wayland (amdgpu) PC used is a Zen 4 7950x cpu in a X670e motherboard, and a 6950xt gpu