@solaris

No problem. I had the same experience in which everything seemed stable except N64 emulation. I guess it pushes the Pi harder than any of the other emulators.

Try to overclock only the GPU, or choose a more conservative overclock value. Also, be sure to try different N64 cores (and experiment with each of the N64's core settings) or the standalone mupen64plus emulator.

@trailjacker I personally don't know a lot about scrapers. I usually use sselph's scraper and then manually add videos on my own, though I'm using an old version of the scraper.

Sorry I'm not more helpful here - maybe a separate thread with that particular question may help?

Yup, confirmed. Don't install the Control Block module from the Drivers list if you're not using it and updating with Retropie 4.3.5, because it looks for it and if not detected, initiates the shutdown sequence.

@retrofreak89 are you overclocking?

@quackwalks Yeah i think so but the other game froze too

You should try with SCPH101.BIN bios instead. It's the one from PSOne, so it's more modern and updated and generally should work better (at least that's the case with my games I've tested). Also, try disabling some features like Interlacing and Dithering.

@red2blue

Yes it is, because it's supported by every system. But if you got it fixed up, good. But if not, you should try it out with other USB stick instead, so don't yet format your main drive, if it's not going to work in the end.

@shaolinmatt

Did you follow the directions on the Wiki/Docs here
https://retropie.org.uk/docs/Dreamcast/

You can check the md5sum or CRC32 of your BIOS files dc_boot.bin and dc_flash.bin to verify you have the correct ones.
https://retropie.org.uk/docs/Dreamcast/#bios

If you go into the RetroPie-Setup Script you can goto Configuration / tools then to reicast - Dreamcast emulator Reicast then Configure input devices for Reicast

The location for your controller mapping config file is /opt/retropie/configs/dreamcast/mappings/

You will also need to verify that in /home/pi/.reicast/emu.cfgthat both evdev_mapping_1 and evdev_mapping_2 are pointing to the matching controller mapping configuration file(s).

Example

evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_Xbox360WirelessReceiver(XBOX).cfg evdev_mapping_2 = /opt/retropie/configs/dreamcast/mappings/controller_Xbox360WirelessReceiver(XBOX).cfg

Also, make sure that evdev_device_id_1 and evdev_device_id_2 are set to the corresponding controller's /dev/input/event* number (run evtest to find out which event number your controller is using).

Example

[input] evdev_device_id_1 = 0 evdev_device_id_2 = 1

@AlexMurphy I had noticed that there was nothing interesting, however, the log was requested to me and I'm not so confident to think that I know better.

Here's runcommand.log, it seems that there's nothing here too.

# code block Parameters: Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-snes9x2002/snes9x2002_libretro.so --config /opt/retropie/configs/snes/retroarch.cfg "/home/pi/RetroPie/roms/snes/RoboCop 3 (USA).zip" --appendconfig /dev/shm/retroarch.cfg Found ROM file header (and ignored it). "ROBOCOP 3" [checksum ok] LoROM, 8Mbits, Type: ROM only, Mode: 20, TV: NTSC, S-RAM: 0Kb, ROMId: ???? Company: ?? Failed to open /opt/retropie/emulators/retroarch/shader/shaders/scanline.glsl: No such file or directory

@BuZz not sure but I don't remember this issue in 4.0.2

@boredgamelad note that the current retropie image/binary updates won't neccesarily include that fix, but yeah from source definitely will. i think if you still get the issue after a source update it might be worth logging an issue here: https://github.com/libretro/pcsx_rearmed/issues

i'll try and recreate it soon also!

@dankcushions said in Zero: Exit a game, system freezes, screen is dim, can't SSH in...:

the reason for adding over_voltage is to INCREASE stability; higher clocks demand more power. however it also raises temps...

for shader performance i would have thought only GPU and maybe memory performance overclocks are relevant.

I tried some new settings last night, and ran it for a good solid 20 minutes switching from game to game like I was doing before (where I could ALWAYS get it to freeze at some point) – and it seemed to be good. Think I dropped each "recommended overclock" number by 25 (475, 475, 475), AND changed the two voltages to 3. Think temp was still around 60º which is normal while you're using it I believe. I will test it even more tonight (including writing down the FPS numbers to see how they compare to the full 500 overclock - I think SNES was still down to like 54-57 instead of 60 FPS...which would be fine as long as it doesn't crash).

CRT-Pi Shader performance I gave up on for SNES and Genesis to be honest. It's just too much on the pi Zero even with the full overclock to get to that magic 60 FPS. I'm trying to keep CRT-Pi for NES (as it helps 8-bit look better to a much greater degree than 16-bit IMO), but will have to see if I get any of the weird pausing which plagued the non-overclocked Pi Zero with lr-quicknes + CRT-Pi.

I'm having the same issues currently. Did you ever find a fix for this issue of swapping from HDMI to DVI? If I find anything myself, I'll post back.

Hi! I have same problem.
For restart pcsx I use hotkey (Select + X) with psx controller.

@zenamistress Please mind the language, we're trying to keep this forum an all ages place. Also, don't resurrect old posts - this is 3 years old post, a lot of things changed since then.

@munkylord84 When you say "already built" do you mean you bought a pre-installed RetroPie bundle, or a friend built it for you?

I am asking as in order to troubleshoot the community needs to know details of how it has been setup initially. If a friend has built it, you'd need to ask them so you can pass on the details. If you bought it however, I doubt you'll get much help here as these types of packages are flying in the face of the Devs here making money off the back of their hard work.

You'll be directed to reinstall the official image off the site before we'd help in that instance.

Also, for N64 you'll need to overclock and tweak settings for best results, and there's great documentation on this in the wiki.

It's not a fake sd card but I think I have confirmed it is a faulty unit. I decided to look in the vendor's, adafruit support forums and found this. https://forums.adafruit.com/viewtopic.php?f=8&t=109254&p=545910&hilit=freeze+pi#p545910
It seems im not the only one having this issue, I have since contacted them for a replacement or return and now im just waiting on their reply. Thank you everyone.

...