-
Notifications
You must be signed in to change notification settings - Fork 6
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
Input mapping returning to default when controller changes #23
Comments
Are you creating autoconfigs for the pads? |
Yes. The strange thing is that the autoconfig file doesn't update when the config are lost, it only updates when I remap again but nothing changes in the files. |
Probably the files are in a read only location then
…On Thu, Feb 14, 2019 at 10:04 AM Wellvergton Marques < ***@***.***> wrote:
Yes. The strange thing is that the autoconfig file doesn't update when the
config are lost, it only updates when I remap again but nothing changes in
the files.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABpC0NrgHtH2sZB-PSndsCbV3ohdthiAks5vNXr2gaJpZM4a69Eb>
.
|
I think not. I think I did not express myself well. When I manually create autoconfig the file updates normally, which shows that it is not read only, what I saying is that when the settings are lost and I will check the file it still has the remap information that I entered, but in the Retroarch the commands do not match the autoconfig file for the controller. And if I do the mapping again the file will be updated but the information will be the same as the last mapping. |
Description
I have a DualShock 3 and recently bought Retroflag's classic Mega Drive controller, I made the mapping of the buttons and everything went well until I went back to using DualShock and the mapping for it got lost, I found it strange, but I did the mapping again, however, when I was playing again with the Retroflag's controller the same problem happened, the mapping I did previously was lost.
If I just exit the Retroarch to return afterwards to play with the same controller I used the last time the mapping is maintained.
Expected behavior
Keep the input mapping
Actual behavior
If the device index changes the mapping are lost
Steps to reproduce the bug
Version/Commit
Environment information
The text was updated successfully, but these errors were encountered: