@sirhenrythe5th said in Which Arcade Emulator for RP4 is recommended?:

As the title says: which emulator are you guys prefering on the PI4?
FBNEO is great, no doubt about that one, but which emulator are you using for the rest?

Good question. Hope this helps you:
https://docs.google.com/spreadsheets/d/1Rq4shU1RUSdcc7cTVWeORMD-mcO6BwXwQ7TGw8f5_zw/edit#gid=0

Let me know if you have questions.

@muldjord Great insights, and thanks so much for everything you’ve done with Skyscraper! I really do like it a lot!

So I’m pretty sure it’s not the SD card. It was purchased brand new about a month ago and once I re-flashed from a previous back up and went back through the steps, everything seems fine now. But yea, I’m sure I must’ve done something or something else may have coincidentally been going on. Especially after reading your comments about how the tool works.

In any event, keep up the great work!!

@Zering Hi...I just double checked, and definitely both bin/cue pairs.

The Shining game that I couldn’t remember was Shining the Holy Ark BTW :)

@Zering Sorry I did not know

@andrea-panatta Try updating the shell script and see if it shows up

@YFZdude Thanks YFZ. Leaning my way through this one mistake/question at a time. ;-)

@quicksilver
It had passed 4 months before I actually tried your fix proposal.
It worked. The X-box controller is now fully compatible. Thank you!

@rodolfoaguilar @Firebird_WS6
I'm summing up what quicksilver proposed.
This solution worked for me.

Plug in a Keyboard While in Emulation Station press F4 to open the Terminal Type sudo nano /etc/modprobe.d/xpad.conf Change
xpad triggers_to_buttons=1 to xpad triggers_to_buttons=0 Press cntrl-x Accept the changes. Return back to Emulation Station by typing emulationstation Restart Retropie.
(In my case, I noticed that the X-box controller had started acting strangely while in Emulation Station.
The D-pad buttons swapped positions in Emulation Station as they were previously in PPSSPP.) Remap the controller in Emulation Station. Remap the controller in PPSSPP if necessary.
(In my case, this was not needed.)

I'm not sure why this issue is affecting some people and not others.
Apparently, the problem is caused by the Trigger buttons somehow.

@dankcushions Did that, no effect. I'll google to see how else I can get a verbose log, but last time I didn't see anything.

It runs well enough on my Pi4.

Oh my god thanks I'm so angry I swear I used the search before I made this and must have missed it.

@nemo93 said in [Solved] "Ecstatica" - issues with saving games in DosBox:

@AdamBeGood You don't have apologize or be sorry for anything. Asking questions and seeking for help is what this forum is there for :-)

Under DOSbox, swapping discs around is not clearly indicated as you experienced yourself! Yet it does work flawless. Let me share a quick hint as well that could come in handy.

Some games do support natively multiple CDROM drives. Meaning you can mount the different "isos" images and assign these to different drives letters. As you mentioned Command & Conquer let's use this as an example below. Just add something like that in your [autoexec] section:

[autoexec] imgmount d /home/pi/RetroPie/roms/pc/isos/comcon/CaCCD1.iso -t cdrom imgmount e /home/pi/RetroPie/roms/pc/isos/comcon/CaCCD2.iso -t cdrom mount c /home/pi/RetroPie/roms/pc/games C: CD COMCON C&C.EXE EXIT

Then no more disc swapping in-game :-) Other games where this is working which I've tested: Under a Killing Moon, Ripper (6 discs!!), Pandora Directive. I haven't tried with the Wing Commander serie so feel free to report back if you have some success!!

Interesting! And I guess that would work with three disks to accommodate Covert Operations also? Great tip!

Thanks again!

Edit - that didn't seem to work for me actually with Covert Ops.. but it may be something I am doing wrong here. That is quite likely. Everything works perfectly so I won't push my luck!

So I managed to solve this, but I'm not entirely sure how. I fixed the under-voltage issue with a better power supply. Entered a game and had the same issue. Remapped after exit, then decided to see if it would do it again with other emulators, and like magic, I could never get the issue to reproduce even after a reboot. So.... I have no idea. My guess is it was related to the undervoltage and the board wasn't getting enough power causing a small memory dump when exiting the emulator.

hey guys, I have the same problem. Can someone confirm that the cuurent image for pi 4 is downloading correctly? cheers

Bumping for posterity

@dankcushions Thank you for your explanation! I disabled overclocking and now my Pi is stable as before. I'll try with milder overclocking next time.

There's been recent work to include Vulkan support in Mesa for Pi. Here are some hopefully helpful links:

https://www.raspberrypi.org/blog/vulkan-update-merged-to-mesa/ https://blogs.igalia.com/apinheiro/2020/06/v3dv-quick-guide-to-build-and-run-some-demos/ https://www.raspberrypi.org/forums/viewtopic.php?t=277125

Most of the links go over similar steps for compiling, installing, and testing Vulkan and its demos. Some additional notes:

The older posts point to a developer's fork of Mesa. Now that Vulkan has been merged into Mesa, whereever you see a git clone you'll want to make sure that you're pointing to Mesa's repository (https://gitlab.freedesktop.org/mesa/mesa/) You'll be able to get Vulkan from the master branch of of the Mesa repository. It doesn't look like it's been tagged to a release yet, so there's likely more work to be done and your mileage may vary. You can actually have different versions of Mesa installed on your system simultaneously, as long as you put them in different directories. In order to ensure stability of my Pi systems, I do this, so I can test and play around while not worrying about everything else. Though Mesa is pretty self contained so it's not too hard to get things back to normal if you overwrite the original drivers. If you have compiled Mesa for installation in another directory, then you'll need to add the following line to your launch scripts or your bash profile in order to point programs to your special installation. You do that with the following line: export VK_ICD_FILENAMES=[YOUR INSTALLATION PATH]/share/vulkan/icd.d/broadcom_icd.armv7l.json I've found that Raspbian/Raspberry Pi OS (which is what RetroPie is built on) actually uses NVIDIA's Vendor Neutral Dispatch version of Mesa (which uses code from Mesa), and not Mesa's version of Mesa. I have no idea if that will be changing or not, but it at least indicates that there will be more work to do before we see Vulkan drivers as part of Raspbian/Raspberry Pi OS/RetroPie as a default.

I've been playing around with Vulkan and so far it's looking pretty good. I have high hopes that as programs begin to adopt Vulkan we'll be seeing some really awesome performance increases. I have not tried Dolphin though. The only thing I've found regarding Dolphin and Vulkan was someone testing it out on a Jetson Nano, which is a different hardware platform. He did compare Vulkan vs. OpenGL and found that Zelda: Wind Walker ran very well with Vulkan where it was choppy on OpenGL. The post is on Facebook (https://www.facebook.com/groups/retropieofficial/permalink/1387063751494192/).

I created a scriptmodule for my own purposes to automate building / installation of Mesa with Vulkan. I may create a separate post for that.

I hope this info helps out.

- George

@stefano-sudati Re-install should be fine.

it generates a gamelist at /opt/retropie/configs/all/emulationstation/gamelists/retropie/gamelist.xml that contains the descriptions.

@GongStar the output of dmesg might be useful after the build fails. You are right there is nothing else in the log - I thought there might be something. Not sure of the issue if you have plenty of free space on card, and no overclock.