@00Hugo said in Xpad driver installation issue - not existing commit:

One question regarding that: The controller is paired now in Bluetooth setup, but why it is not visible as device in "Configure Input"?

Maybe it needs another driver (xpadneo) ? As I said, xpad is used only for wired Xbox compatible drivers.

@mitu OK you were right, perseverance payed off, it finally worked :) Thanks for your help.

@BuZz
Yes it is.
Thank you very much.

Once you've forked the RetroPie-Setup repository (as you've already done), create a branch in it and modify the file you want. Then you can submit a PR from the browser, based on your modified branch - https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.

5e36d06f-43e9-4b67-b244-19a0426fb405-image.png

@luizsaluti Probably yes, but I would imagine that the actual release would be better installed from a Pi image instead. Things might change till then, but feel free to try out the branch on the Pi4.

@mitu
Okay, I know that now.
It seems like it would tell you something different than ask for user if the repository was missing or deleted.

There's a handy 'cloud' enabled saves storage script posted by one of the forum users - https://retropie.org.uk/forum/topic/18712/script-setup-script-to-sync-saves-to-cloud-services. You can maybe adapt it for your needs; it's based on rclone(rclone.org).
Other than that, git would be easy to implement, but it's a bit overkill for this purpose - unless you'd like to have a versioning system in place. A simple rsync script would suffice.

As for the file types, I guess you'll have to think if you want to synchronize:

save states (*.state[X]) memory saves (*.srm) artwork/gamelistst (media folder and/or gamelist.xml).

to anyone else, this was added because of this thread on github
https://github.com/RetroPie/RetroPie-Setup/issues/1743

@psyke83 There is some information in ticket I think - this was intentional. Supposedly doing a git pull on shallow clone can strain the github servers (a popular project was asked not to do this). Also a full history may be important in these cases anyway, for those that want to keep the source around.

@BuZz thanks!

@BuZz Well Ok then, i'll try later. Thanks for answering my question about keeping it. :)

@loganmc10 I added it for both X86/X86_64 anyway (keeps logic simple).

It would be easier to update your romset.

@BuZz git is something I know very little about, but I think I figured out how to get the versioning. Thanks :)