@arroyjose then it sounds like an issue with the USB adapter rather than a RetroPie/Raspberry Pi problem.

@YFZdude You are right that the N64 was released before the Dreamcast.
But the development of the FF-Function in Input-Devices was initiated by SEGA for the Saturn, but came later with the dreamcast.
Nintendo was the first to bring it to the market after copying the idea (similar to the development of the mouse-controlled interface, which was seen by Bill Gates & Steve Jobs at their neighbour XEROX in Silicon Vally back in the 70s :D)

@unknown nah the memory is emulated, don't think a proper emulator could read the data from a real memory card; that would be cool though.

@mitu Ah! That makes more sense now. Thank you!

@cyber said in RPI4: Kodi version update, N64 stuttering, no rumble pack:

I have selected there now the first one (lr-mupen64plus-next).

I cannot find any config files "lr-mupen64plus*" - thats why I took now pictures of the settings which I can see with the retroarch core menu:
https://1drv.ms/u/s!AnFpCl7HpNVtg9s3sr_EwOEzchjJRw
https://1drv.ms/u/s!AnFpCl7HpNVtg9s2ejenqrrrORMhew
https://1drv.ms/u/s!AnFpCl7HpNVtg9s10tfvMXtuttTlPA
https://1drv.ms/u/s!AnFpCl7HpNVtg9s0Up0aFFn_PBBQ7A

i don't think there's much point testing lr-mupen64plus-next as it's going to be slower than standalone, but there's a few settings you can change:

native resolution factor = 1x Overscan = Disabled

be mindful to change only these, and exactly these. some others are named similarly.

graphical issues: compared with mupen64plus-gliden64-highres I have e.g. in the menus black lines: https://1drv.ms/u/s!AnFpCl7HpNVtg9s4IPgzfQ90i32wrQ

comparing what to what? please be specific. if it's to lr-mupen64plus-next, again this is not optimal. use mupen64plus-gliden64

I'm glad to hear everything is working for you now!

Please add some more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Are the L2/R2 triggers working with jstest from the command line ? Exit EmulationStation, then run

jstest /dev/input/js0

and then test if your buttons/triggers are registering. Interrupt the test with Ctrl+C. If you have more than one gamepad connected, replace js0 with js1 or js2, depending on how many gamepads you have connected.

@soda-inc said in How do I enable force feedback / rumble?:

Also, I found some old posts which indicated that the Retropie Kernel might not be setup for controller vibration support.

There's no RetroPie kernel and there's no special configuration that disables controller vibration support (as you've noticed with N64).

When starting a PS1 game, check if you have 'Enable Vibrarion' in the Core settings and also set the Pad 1 Type to Dualshock.

@mitu Many thanks for your prompt response. I was away a few days and just got back. Your recommendation completely fixed my situation with the rumbling. As an added bonus, I was able to set up the controller via Bluetooth, which I was also unable to do prior.

My apologies for not including enuf info on my system/setup. I've reviewed the instructions and will be guided accordingly in future.

Again, my apologies and many thanks!!

@BuZz Indeed! 😄

I have several joysticks identified as DragonRise Inc. Generic USB Joystick (one of them is completely new). And joysticks identified as Personal Cummunication Systems, Inc. PlayStation Gamepad. None of them has vibration in PSX games (Vibration is enabled in RetroArch menu and in the game; type of the joystick were changed to analog). Should I install some drivers or what (just curious; I can't say, I really need that)?

anyone?

I'm pretty sure I've got this sorted out now. It's set up pretty close to how the N64 layout was. I changed the rumblepak switch to requiring a hotkey to be activated. Current setup is below.

DPad R = "button(13)"
DPad L = "button(14)"
DPad D = "button(16)"
DPad U = "button(15)"
Start = "button(9)"
Z Trig = "button(6)"
B Button = "button(1)"
A Button = "button(0)"
C Button R = "axis(2+)"
C Button L = "axis(2-)"
C Button D = "axis(3+)"
C Button U = "axis(3-)"
R Trig = "button(5)"
L Trig = "button(4)"
Mempak switch = "button(11)"
Rumblepak switch = "“J0B8/B12”"

Analog axis configuration mappings

X Axis = "axis(0-,0+)"
Y Axis = "axis(1-,1+)"
Joy Mapping Stop = "J0B8/B9"

@TMNTturtlguy yup. But if i need a bulk set of games that use the same core options or same retroarch.cfg options, i have their individual configs pointing to a different core-options or retroarch.cfg file that i created. So for example psx games that use analog option, i would point their individual config to a different core-options config that i created just for psx that has the analog enabled. That way if the core options ever have any changes made, i dont have to change each config, just the one.

@hansolo77 you're confusing linux drivers with retroarch input drivers.

udev driver in retroarch supports rumble IF

the core does (pcsx does) your controllers linux driver's udev implementation does (?)

@edmaul69
After doing a shitload of searching I found this: https://retropie.org.uk/forum/topic/8228/how-to-install-force-feedback-support-for-pantherlord-greenasia-usb-ps1-2-dualshock-adapters

I will try it when I get home :)

With default = "lr-pcsx-rearmed" I get a weak rumble in Tekken 3 (when enabled in in-game-options) and CTR. But it is way less prevalent than expected.

It seems that rumble was added in a git-commit, but the wiki is not completely up-to date.

I would still like to get rumble like to work with lr-beetle-psx .