@sirhenrythe5th Yes. I even used the official Raspberry Pi program. I think I figured out the problem though. Thanks for the reply!

Hi,
What internal resolution for flycast are you running? I'm using 800x600 and output at 1080p, core resolution (no integer scaling) have no issues running dreamcast games at all, apart from WINCE (windows CE) games as I'm using the recently reverted flycast core, these are not currently supported. Check you are using alsathread for audio and turn of shaders, as most shaders are too demanding (I do use 2x presale bilinear/zfast on all games without issue). Oh and check you are using recent BIOS files as well.

Here's parts of my config:

reicast_alpha_sorting = "per-triangle (normal)"
reicast_anisotropic_filtering = "4"
reicast_boot_to_bios = "disabled"
reicast_broadcast = "Default"
reicast_cable_type = "TV (Composite)"
reicast_custom_textures = "disabled"
reicast_delay_frame_swapping = "disabled"
reicast_div_matching = "auto"
reicast_dump_textures = "disabled"
reicast_enable_dsp = "enabled"
reicast_enable_naomi_15khz_dipswitch = "disabled"
reicast_enable_rttb = "disabled"
reicast_fog = "enabled"
reicast_force_wince = "disabled"
reicast_frame_skipping = "disabled"
reicast_framerate = "fullspeed"
reicast_gdrom_fast_loading = "disabled"
reicast_hle_bios = "disabled"
reicast_internal_resolution = "800x600"
reicast_language = "Default"
reicast_mipmapping = "enabled"
reicast_pvr2_filtering = "disabled"
reicast_region = "Default"
reicast_render_to_texture_upscaling = "1x"
reicast_synchronous_rendering = "enabled"
reicast_system = "auto"
reicast_texupscale = "disabled"
reicast_texupscale_max_filtered_texture_size = "256"
reicast_threaded_rendering = "enabled"

Resolved restoring Keyboard settings.

@glovewithsauce i'm sorry, but asking for/providing links to to BIOS files is against the forum rules

@mitu Thanks!

@sleve_mcdichael said in How do I get rid of emulationstation-dev?:

But yeah, backups are good. I had done something that was causing ES to crash, once in a while, unpredictably, at launch. So I burned a fresh image, hopped on my WiFi, restored my backed-up roms and config files, and I was back in action.

Obv I have backups, but restoring from a backup onto a 256GB SD card takes hours and hours and hours and I try to avoid it wherever possible...

@lolonois and yet, it tracks their last-played date and even groups them into a last-played category if you enable it. As long as you have network access, you have an accurate clock I think.

Thanks for your responses.

@exarkuniv , sounds good…thanks.

Good day. After troubleshooting everything including the motherboard and usb cables I found out from the seller that the Dragonwise controllers will not work with the PI 4. FInd this odd, but that is what they said Only PI 3. Does anyone know of controllers you could recommend that are known to work with the PI 4? Tried every search combination but not finding any specifically stating they will work. Would appreciate any help.

@fretman Folder.jpg

Perfect, that solved it. Thanks.

@bberlin1 This kind of functionality would be provided by the emulator (RetroArch with lr-pcsx-rearmed or lr-duckstation), but it's not present at the moment.

@tsukisuperior can use

sudo CC="whatever" ./retropie_setup.sh

This may not work for all modules as some module code may override it.

distcc can be used automatically by setting DISTCC_HOSTS="192.168.0.1/4,lzo" etc in the same way. It will get added to start of system PATH and added to MAKEFLAGS also.

You can write the RetroPie image directly to the drive and boot from it - assuming your PI has USB boot enabled. If USB boot is not enabled, then you'll need a sdcard to run Raspberry Pi OS and enable it from raspi-config.

We don't support 3rd party images, especially the ones loaded with ROMs and sold - RetroPie's image license is specifically non-commercial.
Ask the seller for support.

I usually do just press Ctrl+r to search the command line history, enter "setup" to get the last setup command, and press Enter to run it. But mitu's solution is much more elegant (and persistent, depending on the maximum length of your command history). 👍

By the way, one thing that you might find useful is to start the setup inside a screen session, so you can logout while setup keeps doing things like updating or scraping:

screen -dmS setup sudo ~/RetroPie-Setup/retropie_setup.sh && screen -r setup

or with mitu's alias:

screen -dmS setup rpie && screen -r setup

The && screen -r setup at the end enters the screen session immediately after its successful launch. You'll notice no difference to running setup without screen, but you can detach from it without killing setup by pressing Ctrl+aand then d (for "detach") alone. You can reattach to a running screen session by entering screen -r in the command line, optionally followed by the name of the session (e.g. screen -r setup) in the case of multiple running screen sessions.

After detaching from screen, you'll be back in the command line and you can logout normally without killing any running detached screen session. Then, you could even relogin to RetroPie from another machine and reattach yourself to your screen session from there.

Sorry for the slightly off-topic lecture, your question triggered my "sharing is caring" mode. 😇

Got it. I found the issue.

Using that CRT/HDMI video mode switcher added a two line statement to my \boot\config.txt that wasn't there before.

framebuffer_height=1920
framebuffer_width=1080

Not sure why it added this, but as soon as I commented and rebooted, my RetroPie core was back to normal size and not shrunken anymore.

I don't have many statements active in my config.txt so I noticed an extra "list" of other video related stuff at the very bottom. It seemed to have duplicated some of the entries that are in sections above and placed them in the last [all] section of the file. I commented it all out so none of it is active.

framebuffer_height=1920
framebuffer_width=1080
disable_overscan=0
hdmi_force_hotplug=1
enable_tvout=0
hdmi_group=2
hdmi_mode=82

Are you sure you downloaded the right image for your system ? The 'illegal instruction' error at the top makes me think you downloaded the image for a Rpi2/3 or Rpi4 board.

Thanks @BuZz! I had forgotten about the addSystem option. I'll have to test that out. Thanks for considering platforms.cfg too.

- George