Pi5 64-bit video garbled but emulation running about amiberry HOT 13 CLOSED

Hi @midwan . Thanks for the response and for encouraging the test. Actually, I have some updates from testing things from scratch.

It all works correctly when installed from scratch, and even after installing RetroPie - as I've come to test. It seems, however, that it doesn't work well when we launch it from within EmulationStation, which means we have to look into it on our end.

I'll close the issue here for now, and go back to working on our side of things. Thanks for keeping up this great project, and for the prompt responses everyone! It is indeed very similar to what @cmitu reported above, but since it runs well when running from the terminal it might mean there's something different at play here.

Thank you.

from amiberry.

Can you please attach your amiberry.conf file as well?

from amiberry.

Of course, apologies!

Quickstart=1
read_config_descriptions=yes
write_logfile=no
scanlines_by_default=no
swap_win_alt_keys=no
gui_joystick_control=yes
use_sdl2_render_thread=no
default_open_gui_key=
default_quit_key=
rotation_angle=0
default_horizontal_centering=yes
default_vertical_centering=yes
default_scaling_method=-1
speedup_cycles_jit_pal=10000
speedup_cycles_jit_ntsc=6667
speedup_cycles_nonjit=256
speedup_timelimit_jit=-5000
speedup_timelimit_nonjit=-5000
speedup_timelimit_jit_turbo=0
speedup_timelimit_nonjit_turbo=0
path=/opt/retropie/emulators/amiberry
config_path=/opt/retropie/emulators/amiberry/conf/
controllers_path=/opt/retropie/emulators/amiberry/controllers/
retroarch_config=/opt/retropie/emulators/amiberry/conf/retroarch.cfg
rom_path=/opt/retropie/emulators/amiberry/kickstarts/
ROMs=9
ROMName=KS ROM v3.1 (A1200) rev 40.68 (512k) [391773-01/391774-01]
ROMPath=/opt/retropie/emulators/amiberry/kickstarts/Kickstart 3.1 (40.068) (A1200) (Commodore) (1993).rom
ROMType=256
ROMName=CD32 extended ROM rev 40.60 (512k)
ROMPath=/opt/retropie/emulators/amiberry/kickstarts/cd32ext.rom
ROMType=1024
ROMName=CD32 KS ROM v3.1 rev 40.60 (512k)
ROMPath=/opt/retropie/emulators/amiberry/kickstarts/cd32kick31.rom
ROMType=512
ROMName=KS ROM v1.3 (A500,A1000,A2000) rev 34.5 (256k) [315093-02]
ROMPath=/opt/retropie/emulators/amiberry/kickstarts/kick13.rom
ROMType=256
ROMName=KS ROM v2.04 (A500+) rev 37.175 (512k) [390979-01]
ROMPath=/opt/retropie/emulators/amiberry/kickstarts/kick20.rom
ROMType=256
ROMName=KS ROM v3.1 (A500,A600,A2000) rev 40.63 (512k)
ROMPath=/opt/retropie/emulators/amiberry/kickstarts/kick31.rom
ROMType=256
ROMName=KS ROM v3.1 (A1200) rev 40.68 (512k) [391773-01/391774-01]
ROMPath=/opt/retropie/emulators/amiberry/kickstarts/kick40068.A1200
ROMType=256
ROMName=Freezer: HRTMon v2.37 (built-in)
ROMPath=:HRTMon
ROMType=524291
ROMName= AROS KS ROM (built-in) (1024k)
ROMPath=:AROS
ROMType=256
MRUDiskList=0
MRUCDList=0

For what it's worth, I tried changing:

• default_scaling_method
• default_horizontal_centering
• default_vertical_centering
• use_sdl2_render_thread

but it didn't seem to change anything.

Sorry for the trouble, and happy to test out other things here.

from amiberry.

Sounds very similar to libsdl-org/SDL#8579.

from amiberry.

RetroPie is not supported on bookworm and therefore not supported on the Pi5. IIRC RetroPie have their own SDL and even perhaps Mesa package which is not compatible with bookworm.
On a standard Raspberry Pi OS amiberry works without any problem on a Pi5.

from amiberry.

@pjft
Did you try running Amiberry on a clean system (RPIOS before you install RetroPie)? Just make sure you install Amiberry's requirements first, of course (they are all mentioned in the Readme of this repo).

from amiberry.

@pjft
Thanks for confirming! :)

from amiberry.

Not at all - sorry for the false issue report.

from amiberry.

Apologies, let me reopen this as there's a small nuance here you may be able to point me in the right direction for. I was slightly incorrect in my previous assessment, so let me add to it.

The issue actually happens when launching the game with --autoload or -G (i.e. directly to the game, not going through the GUI).

When amiberry starts by showing the GUI first, either by removing -G or by just setting the disk to a file, it runs as expected.

Any thoughts on what might be causing this, or what could I look into, in this case? Happy to tweak the code as needed and compile it on my end (which I probably will, but thought I'd ask it here first :) ).

from amiberry.

@pjft
Ah, perhaps it's the VSync flag for the renderer then?
The GUI always sets it, but not if you start a game directly (in that case, the default options apply, and vsync is not enabled by default).
See if it helps changing that option from the Display panel in the GUI, during runtime?

from amiberry.

Oh wow, spot on!

Now, what's really weird is that it shows as disabled by default. Enabling it doesn't make a difference.

But disabling it afterwards does result in the garbled video. Weird - maybe there's something on the vsync setting that makes the default not result in the same behavior as explicitly disabling it.

Still, I'll check if, for the time being, adding the vsync flag explicitly makes a difference and serves as a workaround.

Thank you for the hint! I'll also look at the code later just in case something comes up.

from amiberry.

@pjft
Great that you found it!
Let me know if you come up with a good solution, perhaps we can merge that in.

from amiberry.

Will do. To be clear, on the installation from scratch, running without vsync does cause the same issues, so this is a great find. I'll get back to you as I find things. For now, forcing vsync on is a suitable workaround.

from amiberry.