>5s delay when starting each arcade game

hsamuels

All games on my system use lr-mame2003. Each time a game is selected, the display goes blank for at least 5 seconds before the usual startup screen.

In Run Command Configuration, Launch menu is disabled, Launch menu art is disabled, and Launch image delay in seconds is 0.

I don't recall seeing this on previous builds. Do you have any suggestions on how to speed this up?

barbudreadmon

@hsamuels are you maybe using 7z romsets ?

mitu

Please add some info about your setup, as asked in https://retropie.org.uk/forum/topic/3/read-this-first.

Do you have any additional scripts running before/on-start-up ? There haven't been many changes for runcommand and, with the same settings you have, I can't reproduce the issue.

hsamuels

@barbudreadmon Thank you, I'm using ROMS from MAME 2003, 0.78.

barbudreadmon

@hsamuels said in >5s delay when starting each arcade game:

@barbudreadmon Thank you, I'm using ROMS from MAME 2003, 0.78.

That's not what i was asking about. i was asking if your romsets are compressed as zip or 7zip, because 7zip is dozens of times slower than zip when opening romsets.

hsamuels

@mitu Thank you, and please accept my apologies.

Setup info:

Raspberry Pi Model 3 Version 2.
The power supply is the official one from Canakit. I used the same power supply and Raspberry Pi in a different cabinet, older version of Retropie, without any problems.
Retropie v. 4.8, complete install using imager 1.8.4.
USB devices: 2 generic USB key encoders. Retropie identifies them as DragonRise, Inc. Generis USB Joystick. Apple keyboard.
The USB encoders are the controllers.
verbose runcommand.log
Warning - GameMode unsupported
Warning - Stock GLSL shaders will be used
Warning - Full-screen pointer won't be available
list itemFile with issue - all ROMs, located in /opt/retropie/roms/arcade, with the default set to lr_mame2003.
retroarch-core-options.cfg

cap32_autorun = "enabled"
cap32_combokey = "y"
cap32_Model = "6128"
cap32_Ram = "128"
fbneo-diagnostic-input = "Hold Start"
fuse_machine = "Spectrum 128K"
gambatte_gb_colorization = "custom"
mame2003_art_resolution = "1"
mame2003_autosave_hiscore = "default"
mame2003_brightness = "1.0"
mame2003_cheat_input_ports = "disabled"
mame2003_core_save_subfolder = "enabled"
mame2003_core_sys_subfolder = "enabled"
mame2003_cpu_clock_scale = "default"
mame2003_crosshair_enabled = "enabled"
mame2003_dcs_speedhack = "enabled"
mame2003_dialsharexy = "disabled"
mame2003_display_artwork = "enabled"
mame2003_display_setup = "disabled"
mame2003_dual_joysticks = "disabled"
mame2003_four_way_emulation = "disabled"
mame2003_frameskip = "disabled"
mame2003_gamma = "1.0"
mame2003_input_interface = "simultaneous"
mame2003_machine_timing = "disabled"
mame2003_mame_remapping = "enabled"
mame2003_mouse_device = "mouse"
mame2003_neogeo_bios = "default"
mame2003_nvram_bootstraps = "enabled"
mame2003_rstick_to_btns = "enabled"
mame2003_sample_rate = "48000"
mame2003_skip_disclaimer = "enabled"
mame2003_skip_warnings = "enabled"
mame2003_tate_mode = "disabled"
mame2003_use_samples = "enabled"
mame2003_vector_antialias = "enabled"
mame2003_vector_beam_width = "1.2"
mame2003_vector_flicker = "20"
mame2003_vector_intensity = "1.5"
mame2003_vector_resolution = "1024x768"
mame2003_vector_translucency = "enabled"

Perhaps the only unusual thing I did was to put a copy of es_systems.cfg in /opt/retropie/configs/all/emulationstation. ALl systems other than arcade and RetroPie are removed, which had the desired effect of not having emulation station display a bunch of systems on its startup I don't intend to use. The >5s delay was happening before I did that as well, so it probably isn't related.

hsamuels

@barbudreadmon said in >5s delay when starting each arcade game:

@hsamuels said in >5s delay when starting each arcade game:

@barbudreadmon Thank you, I'm using ROMS from MAME 2003, 0.78.

That's not what i was asking about. i was asking if your romsets are compressed as zip or 7zip, because 7zip is dozens of times slower than zip when opening romsets.

Oh, thank you. That is an excellent idea, but it looks like the files are all zip, not 7zip.

mitu

Thanks for the detailed info.

verbose runcommand.log

Can you post the verbose log on pastebin.com to take a look at it ?

Perhaps the only unusual thing I did was to put a copy of es_systems.cfg in /opt/retropie/configs/all/emulationstation. ALl systems other than arcade and RetroPie are removed, which had the desired effect of not having emulation station display a bunch of systems on its startup I don't intend to use

This shouldn't influence the start-up speed, though the step is un-necessary, since EmulationStation will not display systems which don't have any actual ROMs/games copied in their folders.

hsamuels

@mitu

Thank you again!

Here's runcommand.log in pastebin: https://pastebin.com/rMDfci9D

When EmulationStation loads, it briefly displays each system in es_systems.cfg. It takes a few seconds to zip through the list. The systems are not displayed when I scroll left and right. It only saves a few seconds on startup.

barbudreadmon

@hsamuels said in >5s delay when starting each arcade game:

Apple keyboard.

Is it some kind of bluetooth keyboard ? Does it still happen if you remove it ? I remember seeing similar bug reports with bluetooth controllers.

hsamuels

@barbudreadmon

Just a USB keyboard. The delay happens whether or not the keyboard is plugged in.

For what it's worth, the install was done on a Windows machine. I just happened to have an Apple keyboard lying around.

mitu

I think @barbudreadmon was thinking of this issue and I admit I was thinking something similar may be causing this.
The log file doesn't show anything abnormal. I still can't reproduce the timeout you're mentioning - first launch may be around 5 sec to get something on screen, but subsequent launches are faster and under 5 sec. Just by looking, more time is spend after RetroArch starts, then before (during runcommand processing).
Does the issue happens with other cores also (lr-mame2003-plus, lr-fbneo) ?

NB: I'm doing the test on a 4.8.6/ Pi3 with same 1080p resolution. The only difference to your case is I have an updated system and RetroArch - which I recommend you try also (updating everything).

hsamuels

@mitu OK, time to pull out the stopwatch.

emulator	to launch menu	to USB controller notification (launch menu turned off)
FBNeo	5.5s	8.5s
Mame 2003	5.5s	10.5s

(sorry, I can't format a table here)

It seems that the time to get to the launch menu doesn't care which emulator is selected, which makes sense. But 5.5s to get to that point seems long.

Then with the launch menu disabled, it takes 8.5s for the first thing to appear in neo, and 10.5s in 2003. So there is an appreciable difference between emulators.

The system was just installed from scratch on 1/2/2024. Retropie version 4.8. Does the installer point to the latest RetroArch image?

mitu

Reformatted the table for you.

The system was just installed from scratch on 1/2/2024. Retropie version 4.8. Does the installer point to the latest RetroArch image?

You just run an update of RetroPie-Setup and the installed packages in order to get the latest versions.

hsamuels

@mitu Thank you for formatting the table.

Boy, the Raspberry Pi worked hard for about a half hour updating things. Unfortunately it still takes 10.5s to load the game in Mame 2003.

Do you have any other thoughts or suggestions? It isn't the end of the world, but it's frustrating that I know it shouldn't take so long to load each game.

mitu

@hsamuels said in >5s delay when starting each arcade game:

Do you have any other thoughts or suggestions? It isn't the end of the world, but it's frustrating that I know it shouldn't take so long to load each game.

Try using another mSD card if you have a spare - just copy the already configured image over.

hsamuels

@mitu Shoot. I used Win32DiscImager to backup to my computer, then to write to another micro SD card. RPi won't boot on the copy.

Ashpool

@hsamuels Whence selecting the drive, you've choosen the "boot" partition (not the ext4-/other one (the one windows won't recognize)), haven't enabled read allocated partitions only and the filesize of the resulting image is ~= to the size of the SD-Card? A "yes" on all three should result in a valid/useable image.

hsamuels

@Ashpool I believe the answer is yes for all three.

No matter, I'm going to start on a new SD from scratch. I've done it enough recently that it's a pretty smooth process!

hsamuels

I rebuilt the system on another SD card (actually, the one I was using on a different system that worked perfectly) and it still takes 10.5s for the game to load.