Fix Problem DragonRise no remap input

[22marco77]

Problem with Joy keys DragonRise only recognizes the axis but does not accept key input (a,b and etc..) for both DragonRise controllers, this happens only with AMIBERRY emulator version 5.6, before last update everything it worked fine. The other emulators and controllers work fine. Amiberry 5.6 on Retropie 4.8 (buster) latest firmware on RASPBERRY PI3 MOD B+. I put the DragonRise mapping in the gamecontrollerdb_user.txt file using jstes and with its id, even remapping the file from Amiberry using the REMAP key, everything stays the same, like it doesn't accept the new file assignment. This doesn't allow me to play or select the various options in the GUI, I'm forced to use only the keyboard. Please if anyone has any advice to give me it will be well accepted, I don't know how to proceed to solve the problem anymore.

[midwan]

@22marco77
You mentioned this only happens with version 5.6, but it works fine before the update.
Which version did you have before the update?

[22marco77]

@22marco77
You mentioned this only happens with version 5.6, but it works fine before the update.
Which version did you have before the update?

Honestly I do not remember which version I had first installed, maybe 5.1 on retropie installed on the raspberry

[midwan]

This should be fixed with the latest commit, there was a bug which only showed when using retroarch mapping, where only the first controller buttons were recognized.

[midwan]

Closing this as fixed, but let me know if you still have any issues. I have no way to test this on a DragonRise controller here (don't have the hardware), but I think it was the same bug.

[22marco77]

Ok, thanks, certainly, I will update amiberry and let you know if the problem has been resolved

[22marco77]

Closing this as fixed, but let me know if you still have any issues. I have no way to test this on a DragonRise controller here (don't have the hardware), but I think it was the same bug.

Unfortunately, after updating the scripts and performing an update, the problem was not solved. I also tried to reset the controllers and reset the retroarch keys but it did not work, in amiberry of the second controller DragonRise sees only the axes but the keys do not work

[midwan]

@22marco77
Are you using retroarch mapping? Do you see the [R] indicator in the Custom Controls panel of the GUI?

Can you test the behavior without retroarch, to see what happens? This might require some work, as RetroPie uses Retroarch by default. To avoid messing up your installation, it might be easier to use a separate SDcard, install a normal distro of your choice (e.g. RPI-OS or Manjaro), install the Amiberry dependencies and finally install Amiberry itself. I'm not sure if you need to do something special in the OS to see the DragonRise controller itself, but if so you can also do that.

The behavior in Amiberry is different when using Retroach mapping instead of normal Controllers, so it would be interesting to see if it works there.

[22marco77]

@22marco77
Are you using retroarch mapping? Do you see the [R] indicator in the Custom Controls panel of the GUI?

Can you test the behavior without retroarch, to see what happens? This might require some work, as RetroPie uses Retroarch by default. To avoid messing up your installation, it might be easier to use a separate SDcard, install a normal distro of your choice (e.g. RPI-OS or Manjaro), install the Amiberry dependencies and finally install Amiberry itself. I'm not sure if you need to do something special in the OS to see the DragonRise controller itself, but if so you can also do that.

The behavior in Amiberry is different when using Retroach mapping instead of normal Controllers, so it would be interesting to see if it works there.

You see the R of the two DragonRise controllers, the first works everything without problems, the second only the directional X / Y axis but not the keys, in the other emulators they both work without problems, as it worked before updating Amiberry in the last update. When I have some time over the weekend I'll try another card and try a new clean install of Amiberry

[midwan]

@22marco77
OK, that confirms that you are seeing this problem when using Retroarch mapping. Which corresponds to the issue fixed recently, that I mentioned above, even though you still have the problem as you say.

The next important step would be to test this on a non-Retroarch environment, as I described above. That will tell us more about the problem and when it's triggered.

[22marco77]

@22marco77
OK, that confirms that you are seeing this problem when using Retroarch mapping. Which corresponds to the issue fixed recently, that I mentioned above, even though you still have the problem as you say.

The next important step would be to test this on a non-Retroarch environment, as I described above. That will tell us more about the problem and when it's triggered.

Ok, not retroarch so I have to use a non-lr emulator- right? Or can you tell me which one to try, I also tried with a new installation of retropie on Raspberry pi4 the problem is not solved

[midwan]

@22marco77
Did you see any change regarding this, with the newer releases?
If not, I'd still like to know how it behaves when retroarch is not used - that would show if it's an issue with the retroarch mapping specifically, or something else.

Amiberry uses the retroarch mapping by looking for:

• the file retroarch.cfg, as specified in the relevant path (check the Paths panel)
• a controller file name matching the "joystick name" detected for your controller. RetroPie creates this when you go through the mapping process initially.

If you rename those two files slightly, e.g. by adding .bak at the end of the filename, then Amiberry will no longer detect them and will switch to the normal mapping method. If you do this right, you'll see that [R] is no longer displayed in the Custom Controls panel, and you instead get an [N] symbol there.

If things work properly under this scenario, then at least we'll narrow the problem down to the retroarch mapping.