v42 Amiberry opens yet settings/config issue

Open
#14,970 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
linux

Research direction

Start by comparing the attached v41 and v42 Amiberry config files and reviewing amiberry.log; the reported config path is \\BATOCERA\root\configs\amiberry\conf\amiberry.conf. Check how startup handles these settings and where the summary CSV logs are written. Done means the GUI is visible in fullscreen, saved settings are not reset, and gameplay no longer has the reported slowdown or sound jitter.

Written by the indexing model from the issue text.

Description

Batocera build version

batocera-bcm2711-42-20251007

Your architecture

Raspberry Pi4 B

Your Graphic Processor Unit(s) (GPU)

N/A

Issue description

v41 worked OK via Amiberry for Amiga games.
Clean install of v42 and Amiberry does not functional on my Pi4 as expected. Seems to run with slowdown and sound suffers a little noise/jitter. Default settings only.

Checked resolution/fps setting on the Pi4 - 1080 60hz as normal.
Tried to open GUI F8 menu on Amiberry - game pauses yet no longer shows the menu.
By toggling the fullscreen mode (to switch to windowed mode) I can then see the GUI menu over the top of the game. Fullscreen default mode doesn't allow menu to be visible.

Config file seems to have changed in v42 and keeps being replaced at Amiberry startup so any changes made are ignored/reset (\BATOCERA\root\configs\amiberry\conf\amiberry.conf)

This cannot be disabled as reverts config at startup. Also sets quit key to F9 instead of F10 as used in v41.

default_open_gui_key = F8
default_quit_key = F9
default_fullscreen_mode = 2
write_logfile = yes

Lots of 'amiberry__summary.csv' logs are made in the root/systemfolder which is not a 'normal' behaviour. Possible the amount of effort to write these logs (once every second) is causing the slow down/oddities during gameplay.

Detailed reproduction steps

Installed v42 to my Pi4 memory card.
Bootup, check game pad, keyboard and mouse all detected. Connect to WiFi.
Copy required BIOS files for Amiga WHDload support.
Copy test game (silkworm.lhd)
Change game settting > advanced core option > Amiga ECS = Amiberry A500

Run game

Details of any attempts to fix this yourself

Ensure resolution/refresh is 1080 at 50 or 60hz for full game speed support on Pi4.
Clean install of Batocera v42 to ensure no other changes/conflict.
Attempted changes in the amiberry.conf file to disable write_logs, set quit key to F10... Changes all reset at Amiberry startup.
Toggle fullscreen mode to windowed - only way I could get GUI F8 menu to show.
Check resolution, emulation speed and CPU options set correctly.
Check sound emulation option.

Details of any modifications you have made to Batocera.

None

Logs and data
Image

amiberry.log

v42-amiberry.conf.txt
v41-amiberry.conf.txt

Dominant language
Python
Stars
3.2k
Forks
748
Avg merge
9h 51m
Merged PRs (30d)
170

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from batocera-linux/batocera.linux

All issues in batocera-linux/batocera.linux

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.