@redec easiest way is when you hold a button to configure, the name that shows up. If they match, then they are using the same encoder. Most of the cheap chinese brand controllers tend to use the same one cause its probably cheap and easy to use, but there is never any consistency on what phyiscal buttons are mapped to what virtual buttons on the encoder.

@muldjord said in Skyscraper not gathering resources:

@tafkab76 Allow me to laugh a bit and still be glad that you solved it, however silly it was. :)

Sure!

ok I'm an idiot....I didn't realize when I first mapped my ps3 control to retropie - that the ps3 controller numbers are right there as well..dpad up is 13, dpad 14, then I just needed to go to the dapinput.ini and add 1 to all the numbers since 0 is an unmapped number

@unknown FYI. The Famicom disk system (the floppy disk thing) also uses the same NES emulators

@askcompu you may want to try forcing a specific output resolution when you use that tv. https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

@andrewsi

Ah, I see. Thank you for the info. I will give it a try!

@greenhawk84 yes.

Add the line lr-flycast = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-flycast/flycast_libretro.so </dev/null --config /opt/retropie/configs/arcade/retroarch.cfg %ROM%"

to your /opt/retropie/configs/arcade/emulators.cfg.

Move the rom to the roms/arcade folder.

Restart Emulationstation, click the game name in the arcade list, pull up the runcommand menu, select emulator for ROM, lr-flycast should be in the list, select it, and launch.

I assume you have or know how to set/activate runcommand. if not, go to config menu of emulationstation, select "run command configuration" and make sure "launch menu" is enabled.

@dankcushions It worked, Thank you very much. Would you consider adding this information to the Docs?

@crush ok what info you need? Please i want to play some games so much and i sad because not working the bios is is bios folder scph1001.bin and the games is usa version

@rva-818x-laystar Don't use 'Reset' from RetroArch's menu, since it will disable any configuration done by RetroPie - including the BIOS folder used as 'System Dir'.

Rename the retroarch.cfg file from the pcengine folder or delete it, then re-install the emulator before starting any PCEngine games. Re-installation will re-generate the RetroPie's default configuration for pcengine.

Has someone in the past 4 year found a solution to enable joystick/gamepad input on ioquake/ioq3 using RetroPie? It should be fairly simple as SDL natively supports these kind of controllers, but somehow I've failed miserably in getting it to work with my Logitech F710 gamepad(s).

@krytern said in CHD games not working for Sega CD.:

Looks like it is a problem with the CHD file.

sounds like you may not have converted it properly.

I downloaded Sonic CD to test ...

Firstly, you need to use CDmage (V1.02.1) to convert the 35 *.bin file tracks of Sonic CD into a single *.bin before you can use CHDMAN

after that you will have just 2 files ..

Sonic CD (USA).cue
Sonic CD (USA).bin --------- which is 587,601KB in size

after running CHDMAN

Sonic CD (USA).chd --------- 329,386KB

which is approx 12MB larger than your 317MB file

Tested it with my setup, and it works fine

@quicksilver i disabled ertm and it still gives me the same error

@gleam2003 I have a Orange pi 4 and would like to install your modded RetroPie. I tried your script but with no success. Some tip?

@mitu ok so here is what i found to be my problem..
i thought i could just rename the file right click rename.
to fix i opened file in notepad and save as.. lair2.txt...
just so if there are others that dont get it like me
lol
thank you ever so much..
now i can move on to the rest of the fun

@smilker Hi there. I am having similar issues with EGSTARTS joystick and buttons. Actually, you have made it much further. I am still not able to get even one controller to map properly.

Do you mind sharing where you found info on getting these set up? The EmulationStation configuration seems to work to some extent, but doesn't work properly for me in games.

Thank you.

@buzz Hi, Im having this same issue but with Linux Mint Debian Edition 4 (debbie). Could you add the work around for that as well please, cheers.

~$ lsb_release -sidrc
Linuxmint
LMDE 4 (debbie)
4
debbie

So I found a solution that I think works (at least for me.) I changed the entire configs.hdmi>daphne folder permissions to 555 and when I add a new controller, I get this error:

daphne input.jpg

However it does NOT overwrite my current dapinput.ini file. I can't see anything else in that directory that it would need to write to anyway.

I tested all 17 Daphne games and they all worked and they all kept my controller configs even after configuring a few new controllers so I think this is at least a fix for my situation.

Thanks for the input everyone! It was helpful to put me on the right path!

@buzz
You have a good point.

I had a very similar problem to this thread. I replaced my Pi 3 retropie with a Pi 4 and retropie was behaving in a jittery fashion with Emulation Station and the games weren't smooth. I also have a 4K Samsung Smart TV as did the original poster. Although I wasn't using Amiberry, I was using mame, daphne, and jzintv and I figured the same solution that @gordonfreemanjr used would work for me. So I added the five lines to my /boot/config.txt file that he listed in his "IT WORKS" post but lo-and-behold it did not work for me. tvservice -s was still showing a 4K connection when I expected 1080p.

My solution was simple with a twist. Starting from the stock config.txt, I uncommented and modified the following:

hdmi_group:0=1 hdmi_mode:0=16

It was necessary for me to add the :0 to get it to work. Now there are no jitters, the motion is smooth, and tvservice -s reports a 1080p connection.

@guy-0 said in Run a command after logging off pixel:

Should I have done it through CLI instead?

No, installing from RetroPie-Setup is fine. I wonder why the onstart script doesn't work though, the desktop is launched via runcommand.