cleverest@gmail.com wrote: ↑Fri May 03, 2019 12:02 am
I want to use EmulationStation as the autobooting GUI (however I pull that off, lol)
There is an option for that in Setup ODROID GameStation Turbo as well.
cleverest@gmail.com wrote: ↑Fri May 03, 2019 1:44 am
BUT I was forced to map my keyboard as the "detected" gamepad at launch for now because it wouldn't actually detect my gamepad button presses.
EmulationStation uses it's own implementation of Joystick input, most likely bound to the SDL2 version.
It's possible that the SDL2 version simply doesn't know what to do with the controller.
Looks like a very generic gamepad, those can often cause issues.
Try checking with lsusb as what the controller is found as and post it here.
cleverest@gmail.com wrote: ↑Fri May 03, 2019 1:44 am
I tried to run the controller config option under the SETUP Odroid GameStation Turbo desktop option, and it starts loading something but then closeds I didn't actually DO anything after this...it still doesn't detect button presses...
This controller config only adds a new config for retroarch it has nothing to do with EmulationStation, as I said before, EmulationStation is completely separated from everything else of the system.
In fact, even if you were able to entirely configure your controller inside of EmulationStation, it would have absolutely no effect of any emulator you run and the emulators might not work at all with the controller.
Also the other way around, only cause it doesn't work in EmulationStation doesn't mean it doesn't work inside the emulator.
Emulator might just work fine, even if EmulationStation uses keyboard.
cleverest@gmail.com wrote: ↑Fri May 03, 2019 2:04 am
I tried to run apt-get install sixad-gasia, but it failed with a server certificate error...I then tried just SIXAD, and it still failed with same error.
These drivers are only for Bluetooth PS3 controller and "fake wireless PS3" controller.
These are no drivers for just any controller, and won't help you at all with a wired controller that you have.
Still the certificate error is interesting, can you show it to me?
Also check the time of the image if it's correct or not, incorrect time is most often the root cause of certificate errors.
cleverest@gmail.com wrote: ↑Fri May 03, 2019 2:30 am
Code: Select all
root@gamestation-turbo:/home/odroid# sudo add_joyconfig
/usr/local/sbin/add_joyconfig: line 152: /usr/share/libretro/autoconfig/udev/ShanWan_PS3/USB_Corded_Gamepad.cfg: No such file or directory
/usr/local/sbin/add_joyconfig: line 153: /usr/share/libretro/autoconfig/udev/ShanWan_PS3/USB_Corded_Gamepad.cfg: No such file or directory
sed: can't read /usr/share/libretro/autoconfig/udev/ShanWan_PS3/USB_Corded_Gamepad.cfg: No such file or directory
sed: can't read /usr/share/libretro/autoconfig/udev/ShanWan_PS3/USB_Corded_Gamepad.cfg: No such file or directory
grep: /usr/share/libretro/autoconfig/udev/ShanWan_PS3/USB_Corded_Gamepad.cfg: No such file or directory
root@gamestation-turbo:/home/odroid#
Couple of things: you're already root, you don't need sudo when you're root.
The controller you use seems to be a wired ShanWan_PS3 controller, I had some issues with these already as they are "faked" PS3 controller and can cause quite some issues as they pretend to be PS3 controllers but don't actually match the button layout.
Still the issue here is, that it as a Folder Name in it's path, which is very odd, as this probably means that the Controller itself uses a "/" in it's name which is very confusing.
Anyway this should be able to be fixed with the following command:
Code: Select all
mkdir -p /usr/share/libretro/autoconfig/udev/ShanWan_PS3/
after that run the command again.
Also I highly recommend you uninstall the sixad driver that you installed as it's not for your device and might mess up your system, as it reconfigures a connected bluetooth adapter so if you ever try to use a bluetooth device, it might not work since you installed the sixad driver.