I just had a convo on discord with the screenscraper guys and it looks that version 3.9.1 is broken.
This command yields no results on 3.9.1, but it does work on 3.7.7

Skyscraper -p switch -s screenscraper --query "romnom=Super%20Mario%20Odyssey%20(World)%20(En,Ja,Fr,De,Es,It,Nl,Zh,Ru)%20(Rev%203).xci" /home/retropie/RetroPie/roms/switch/super-mario-odyssey.xci

@windg said in sudo: /usr/bin/sudo must be owned by uid 0:

Now that mitu mentions it, it seems that I put the theme here : /etc/emulationstation/themes and maybe that's why it failed from FTP .

Yes, that's a root folder and so you need root permissions to work there.

Custom themes or those you want to edit should be placed in ~/.emulationstation/themes or /opt/retropie/configs/all/emulationstation/themes (they're the same, via symlink) where they can be worked on by the regular user.

I saw the option to enable Jiffydos at retroarch and I see that, when enabled it loads a .d64 file somewhat quicker. Is this the only advantage, or you can do other things with it?

Just a note: 2X is the default resolution for PPSSPP in the source code. I built it from source recently, and that's the resolution that comes up the first time it's booted.

So, this is not a Retropie specific problem. It's the default for the application. Whether Retropie wants to override the default I'm not sure. Personally I think that 2X with frame skip is way more enjoyable than 1X without frame skip. But that is of course personal preference.

Also, with the Raspberry Pi 5 the default of 2X should run great. Though I won't know until my board gets here.

Cheers.

@SaturnX said in Adding 2xUSB Gamepads to Arcade Setup for P3/P4?:

What’s the best approach for this such that I don’t muck up my controller settings?

There's not much to do besides connecting the controllers and configuring them in EmulationStation. The only caveat is the controller order - it's possible the external controllers to switch places with the encoders and replace the P1/P2 slots, but if you don't keep the external gamepads connected all the time it's not going to be a problem.

I’m concerned that I’ll mess up the controller configurations and I don’t have a complete understanding of how controller configuration files are set behind the scenes.

Generally the configuration files are matched based on the controller name, unless your external gamepads are also named DragonRise, ... (highly unlikely), configuration files will not be a problem.

Also is it possible to limit the 4p setup to just select games? Is that even necessary?

It's not necessary, you just have to pay attention to the games that have 4p/2p versions and not start the 2p when playing with 4 controllers by mistake (like TMNT / Sunset Riders / etc.).

RetroPie is just a RaspiOS Lite image underneath, so a regular Linux/Debian installation.
You can add your code to the autostart.sh script that RetroPie uses to start EmulationStation (see here how to access the script) or just create your own service to start on boot (see here).

Aha, I actually figured out how to make it work, for anyone reading this in the future!

The problem is for whatever reason the entry that emulationstation creates just starts with "roms/gbc." It works once you simply replace "roms/" with "./" in front of that, which is what is listed for the paths for games before the rom name too (and I suppose substitutes for the entire filepath to the root folder). So adding this to my sgb gamelist...

alt text

Creates this in my emulationstation system for SGB:

alt text

Which is exactly what I was hoping for. Clicking through those two directories takes me to all my SGB-compatible GB and GBC games, and I didn't need to add duplicate roms to do it as the gamelist points to the GB/GBC rom locations I have for those systems. Woohoo!

I know this is an old thread, but its one of the many I have been over while trying to find a solution to this problem.

Mind you I'm running Steamlink as a port from RetroPie on a Pi4B 8GB.

Heres what I had to do to resolve the issue for myself.

In the Rapberry Pi Config file; Disable Underscan Disable Screen Blanking

Make sure Steamlink and other packages on your device are up to date.

Make sure that your Pi is outputting the same resolution or lower to your TV or monitor as the PC that the games are actually running on are outputting to its monitor. Eg. If your PC is running the games on a 1080p monitor, you likely wont be able to steam link from the Pi on a 4K TV @ 2160p without the black screen issue. I just set the display output in both my pi config and retro pie to 1080p to match my PC monitor and now Im playing without issue.

Hope this helps anyone whos still stuck with this issue.

Huzzah! After a little bit of grep and quite some trial-and-error, I found:

$ xinit -- vt1 -keeptty

(Side note: while this works, it uses a small corner of the screen. How to make this full screen?)

With that, I was able to use xinput list and list-prop and get the device name and properties unique to my setup. This led me to:

$ xinput set-prop 'USB Optical Mouse' 'libinput Accel Speed' -0.25

This immediately slows the on-screen pointer by roughly 25% (acceptable values seem to range -1.0 to 1.0, and default is 0.0).

Alternatively:

$ xinput set-prop 6 275 -0.25

...also works, if I were confident the device number won't ever change. I don't know what happens if I reboot, or plug/unplug additional devices etc., though, so I stick with using the name.

Now, starcraftr.sh:

#!/bin/bash xset -dpms s off s noblank xinput --set-prop 'USB Optical Mouse' 'libinput Accel Speed' -0.25 matchbox-window-manager -use_titlebar no & cd "/opt/retropie/ports/starcraft/data" && ./starcraft.sh

(The trailing & used in the example was not necessary)

This worked, but still a little fast and so I dropped it down again to -0.5. Now that feels more like what I'm used to.

Now, let's say I am a user who can't or don't want to alter the root-owned starcraftr.sh in the install folder. Or, maybe I just don't want to lose my custom setting to a reinstall. So I copy it into config dir at /opt/retropie/configs/ports/starcraft/starcraftr-slowmouse.sh, make the edits there, and then edit emulators.cfg like:

default = "starcraft-slowmouse" starcraft-slowmouse = "XINIT:/opt/retropie/configs/ports/starcraft/starcraftr-slowmouse.sh"

Let me repeat my previous question - do you have a system override where the RetroArch settings are different for the gba system ? Is your gba system's configuration file custom/different from the default that RetroPie installs ?

Post the config file (/opt/retropie/configs/gba/retroarch.cfg) on pastebin.com. If you can, get a verbose log from RetroArch during this occurence and post it also on pastebin.com

@harelnaveh10 How did you solve it ? Other user that may encounter similar problems may learn something - so as we, that tried to diagnose and provide assistance.

@retropieuser555 @windg thanks for all the responds i solved the problem

Even though unlisted, xdf seems to be supported by the libretro px68k core. You can add the new extension as explained here:

create the /opt/retropie/configs/all/platforms.cfg file (or, via file shares, at \\retropie\configs\all add to the file: x68000_exts=".dim .hdf .hdm .2hd .d88 .m3u .xdf" reinstall the lr-px68k libretro core.

Copy the .xdf floppy image to the system's folder and restart EmulationStation.

EDIT: as an alternative, if the game has multiple floppies, you can create a playlist in .m3u format and load that instead.

@retropieuser555 I got some errors running cmake. It's fine. I'll use cmitu's incomplete script.

Did you try to login with the lowercase as retropieuser555 suggested you?
Login: pi
Password: raspberry

It looks that the system don't set to boot first into emulationstation, it's something that you can fix if something else didn't happen.

You can connect from SFTP or with Samba and take you files, see: https://retropie.org.uk/docs/Transferring-Roms/.

Or maybe can have an exemption condition to the retropie gamelist.xml
@Lolonois

@mozvillat Please add some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Get a verbose log from the error run and post it on pastebin.com.

@spannernick1 Dude, retropie works without doing all that... only install with the script for debian and derivatives

OK, I finally got it fixed. and I really should have looked at this first, so I'm sorry for putting everyone who looked at this on a wild goose chase. But I've been putting off working on this because I've had other projects and while I can rebuild, I didn't want to. But the overscan didn't work, it would not pull it to the left like I wanted, I made sure the TV was on game mode and not stretching or adding any post processing. I had a spare TV and wanted to rule out the TV, and behold I seen this
IMG_20231028_182219.jpg
I commented out the hdmi_drive=2 and it all works.
I'm not even going to pretend I know what was going on, but my guess the damaged connector was pushing sound through what was left working of the cable and had to push the video to the side to make room for that. I dunno, but new cord, and verified it's working. I'm going to buy some backup HDMI cables just in case and really try to come up with a better solution to where I sit the Retropie

@quicksilver I know this is an old topic, but the link seems to have changed. I was looking up the information for this issue and found this:

https://github.com/RetroPie/RetroPie-Docs/blob/master/docs/Universal-Controller-Calibration-%26-Mapping-Using-xboxdrv.md