Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote RetroPad: 11 of 24 buttons does not work #16263

Closed
davidhedlund opened this issue Feb 19, 2024 · 17 comments
Closed

Remote RetroPad: 11 of 24 buttons does not work #16263

davidhedlund opened this issue Feb 19, 2024 · 17 comments

Comments

@davidhedlund
Copy link
Contributor

davidhedlund commented Feb 19, 2024

Description

Tested with PlayStation DualSense in Ubuntu 20.00 based distro.

  • 24 of 24 buttons works in the games.
  • but only 11 of 24 buttons worked with the Remote RetroPad.

Expected behavior

[What you expected to happen]

Actual behavior

[What is actually happening]

Steps to reproduce the bug

These controllers don't work with the "udev" controller driver:

  • L2
  • R2

The thumb sticks didn't work at all, but they have now been added:

  • L3 up
  • L3 down
  • L3 left
  • L3 right
  • R3 up
  • R3 down
  • R3 left
  • R3 right
  • Menu button

Bisect Results

[Try to bisect and tell us when this started happening]

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.17.0 Appimage

Environment information

  • OS: [The operating system you're running]
  • Compiler: [In case you are running local builds]
@zoltanvb
Copy link
Contributor

In current RetroArch, remote retropad should be able to display also analog sticks, can you check if this brings an improvement?
I have not changed actual packet transfer (i.e. the remote part), but analog axes were sent also earlier, just not displayed.

@davidhedlund
Copy link
Contributor Author

davidhedlund commented Mar 24, 2024

In current RetroArch, remote retropad should be able to display also analog sticks, can you check if this brings an improvement? I have not changed actual packet transfer (i.e. the remote part), but analog axes were sent also earlier, just not displayed.

Thank you very much for fixing most of this. The thumb sticks are working 100% in 1.18.0, but these buttons don't work for controller driver "udev":

  • L2
  • R2

They are working fine with controller driver "sdl2".

@zoltanvb
Copy link
Contributor

How is L2/R2 mapped in (auto)config? (Note that remote retropad behaves as a core, so it may have remap file.)

@davidhedlund
Copy link
Contributor Author

davidhedlund commented Mar 25, 2024

How is L2/R2 mapped in (auto)config? (Note that remote retropad behaves as a core, so it may have remap file.)

sdl2 (and the values are correct since they are assigned these values when I map a key with them in Hotkeys):

input_l2_axis = "+4"
input_r2_axis = "+5"

udev:

input_l2_btn = "6"
input_r2_btn = "7"

@zoltanvb
Copy link
Contributor

I can't make sense of this, may be driver+device dependent quirk, I can register R2/L2 with udev and another controller. R2/L2 is frequently set up as an axis, but it should still work, I tried checking if for some reason only the analog button part is being sent in that case, but nope.

If you try to bind R2/L2 with udev, does it still end up with buttons 6 and 7? And does L2/R2 work in games with the DS controller + udev?

@davidhedlund
Copy link
Contributor Author

davidhedlund commented Mar 26, 2024

I can't make sense of this, may be driver+device dependent quirk, I can register R2/L2 with udev and another controller. R2/L2 is frequently set up as an axis, but it should still work, I tried checking if for some reason only the analog button part is being sent in that case, but nope.

I wish I could help, but I don't know C, and I don't really know Git.

If you try to bind R2/L2 with udev, does it still end up with buttons 6 and 7?

Yes. Actually I submitted the PR specifically for this that is responsible for the "6" and "7" values.

And does L2/R2 work in games with the DS controller + udev?

Yes.

@davidhedlund
Copy link
Contributor Author

Do you have a controller with L1 and R1?

Are the working in Remote RetroPad for you?

@zoltanvb
Copy link
Contributor

zoltanvb commented Apr 4, 2024

Yes and yes.
I have a PR waiting that would show also the analog values for the triggers, once it gets merged it may be interesting to see if there is anything detected differently.

@zoltanvb
Copy link
Contributor

The analog trigger display has been merged since a while, can you try what it shows for L2/R2 with your controller?

@davidhedlund
Copy link
Contributor Author

In current RetroArch, remote retropad should be able to display also analog sticks, can you check if this brings an improvement? I have not changed actual packet transfer (i.e. the remote part), but analog axes were sent also earlier, just not displayed.

Thank you very much for fixing most of this. The thumb sticks are working 100% in 1.18.0, but these buttons don't work for controller driver "udev":

* L2

* R2

They are working fine with controller driver "sdl2".

The L2/R2 issue for the DualSense controller was that the controller file was incorrectly generated by Retroarch, so it had to be fixed manually:
libretro/retroarch-joypad-autoconfig#1135

@davidhedlund
Copy link
Contributor Author

davidhedlund commented Jun 29, 2024

The analog trigger display has been merged since a while, can you try what it shows for L2/R2 with your controller?

It's working now, with the new controller file for DualSense. Can you please make sure that you didn't add unnecessary code? I'm sorry but it was really just an issue with the controller file for these two buttons.

This issue should be fixed to prevent RetroArch from generating wrong autoconfig files:

@zoltanvb
Copy link
Contributor

No code was harmed while investigating this issue :) analog trigger test was added to remote retropad for generic use.

@davidhedlund
Copy link
Contributor Author

davidhedlund commented Jun 29, 2024

Yes and yes. I have a PR waiting that would show also the analog values for the triggers, once it gets merged it may be interesting to see if there is anything detected differently.

So should we not revert this PR? If not, feel free to close this issue.

@zoltanvb
Copy link
Contributor

I was referring to #16390, it is merged and should remain in the code. I can't close the issue, but eventually someone with the necessary rights will swing by.

@davidhedlund
Copy link
Contributor Author

I was referring to #16390, it is merged and should remain in the code. I can't close the issue, but eventually someone with the necessary rights will swing by.

Thank you very much for your help! People can now evaluate their controller configurations with RetroPad, which is great for evaluating new autoconfig files before they are uploaded.

@davidhedlund
Copy link
Contributor Author

Remote RetroPad: Analog trigger indicator disappears on release for L2/R2 buttons

@davidhedlund
Copy link
Contributor Author

Sony DualSense (the PS5 controller) does still not work with Remote RetroPad, I just tried it with RetroArch 1.20.0:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants