@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.

Try running it with full paths to both the python executable and your python script. No need for anything in runcommand.cfg.

None. </thread>

@barbudreadmon Fighting Layer runs at over 50FPS in Mame 2010 and is very much playable. I didn't even test frameskip. It is about about 15FPS slower in Mame 2016.

Perhaps I need to check out Mame 2003+ for system 11 and 12 compatability. Further to my previous experiments with System 246/256 (PS2) my understanding is that no version of Mame currently supports these.

If you want the dolphin emulator, install steam on your pc. Steam link on your pi. Add the dolphin emulator to steam. You can stream dolphin emulator from your pc via steam link to a raspberry pi. Steam link is in the expirimental section.

Sorry for major bump, but just wanted to say that despite several months between posts, I finally managed to update my install completely to version 4.6.9 and I would say yes it does seem to have improved a bit. I reduced my N64 stuff and completely removed Dreamcast though, as lets be honest you aren't going to get much joy on that front on a Pi3B+. But the couple of dozen N64 games I do have seem to run a lot better than they did on previous installs with only a small margin of tweaking and my usual slight GPU overclock, and I notice the standalone GlideN64 is definitely improved. Very pleased, and worth it for pi3B+ diehards imho.

@mitu Sorry about that. All of the urls where he talks about lossy chd he also use it to upload roms, so I didn't know how to refer to that person and the method he uses.

Anyway, I have edited the first post. Sorry again

It's a pity it doesn't work, it was the ideal steering wheel for an outrun-based arcade, because of the Ferrari logo theme and the license :(

@Gobon-Shiteinga If your Pi crashes, or you have to do a manual reset, it will not save anything.

You have to exit your emulator 'cleanly', then turn off your system or restart your system in ES to make sure your data is saved.