Categories

• Help and Support

  Get help and support from other RetroPie users

  16124
  Topics
  113398
  Posts

  

  @Foxsec said in Joystick Conflicts: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=9c1664a3-6dc6-4ad4-afc8-334c7e46342b ro quiet splash vt.handoff=1 are you sure you edited the line correctly in /etc/default/grub and ran update-grub? perhaps show us the content of it
• General Discussion and Gaming

  General discussion relating to using RetroPie and gaming. Please do not use for help/support requests.

  MAME Random Of the Week
  2120
  Topics
  28910
  Posts

  

  @mitu ok no problem.
• Projects and Themes

  Show off your custom builds, themes, and splashscreens

  1399
  Topics
  27747
  Posts

  

  I have created some scripts to automate starting xboxdrv via udev and systemd services. Maybe someone has a use for them. Currently there ist configuration for the following controllers: Xbox One Wireless Controller Nintendo Switch Pro Controller 8Bitdo SFC30 Controller Excerpt from Github Describtion: Why? I wanted to have a reliable way to start and stop xboxdrv when a controller gets connected. Using xboxdrv also makes it easier to have the same controls accross different emulators and controllers. What does it do? Once a Controller gets connected to the system the corresponding udev rules will do several things with it: On connection: Change the file permissions of the original /dev/input/eventX and /dev/input/jsX device files to 0600. This is done to prevent emulators and emulationstation from listing controllers that are occupied by the xboxdrv when started as normal user. xboxdrv creates new event and js device files anyway. Afterwards a systemd service is started, which launches the xboxdrv script for the controller that has been connected. The launched xboxdrv-script should have all the need configurations for the controller to work properly On removal: When the controller is removed or disconnected the systemd service will be stopped. This will kill the corresponding xboxdrv for the controller. You can get in here: https://github.com/parasven/Xboxdrv-controller-scripts
• Ideas and Development

  Share your ideas and suggestions for RetroPie. You can also use this area for development discussion.

  1157
  Topics
  23928
  Posts

  

  @OneSwitch In order for the 'auto-boot' to work, you first have to make the game work normally - from ES, using the Runcommand menu to choose the right emulator for the ROM. After that, using the Runcommand from the auto-start script will run the game normally - using the chosen emulator. If this part is not working, then the 'auto-boot' will not work.
• ControlBlock, PowerBlock & Co.

  Get help and support for PetRockBlock's hardware

  282
  Topics
  1862
  Posts

  

  @petrockblog thanks for your reply! When do you think you be able to get that update for the installation script committed?
• Announcements

  Announcements regarding our community
  25
  Topics
  32
  Posts

  

  https://retropie.org.uk/2019/07/retropie-4-5-1-update/ As detailed in the last post – https://retropie.org.uk/2019/07/composite-out-broken-on-retropie-4-5/ – there were some issues in the last image due to the updated Kernel. A newer Kernel has been released for Raspbian Stretch that resolves the composite output issue, but we also had problems reported with overscan settings and decided to implement a workaround. As the previous 4.14 Kernel was well tested, we decided to switch back to it for now, and also created a new image (this was actually uploaded on the 17th July, but due to some testing and time constraints is only being announced now). If you have a 4.5 version of RetroPie for the Raspberry Pi you can choose the update option in RetroPie-Setup and then choose to “Update System Packages” when prompted. This will downgrade the Kernel to the one in this 4.5.1 image. The Kernel will only be downgraded if choosing to update System Packages from the RetroPie-Setup interface. You can download a 4.5.1 image from https://retropie.org.uk/download/. For first installs please follow the Installation Instructions. We are still working on Raspberry Pi 4 support. You may have seen some unofficial images from other people with some emulators working – but please bear with us. We also have some emulators working, but don’t want to release anything until we are able to realistically support it. Changes since 4.5 Downgraded to 4.14 kernel to resolve some 4.19 kernel/firmware issues (other rpi4/fkms changes which will be announced in a future post)