v42 Amiberry opens yet settings/config issue
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
- Domain
- operating-systems
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
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from batocera-linux/batocera.linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
batocera-linux/batocera.linux#17423 ·
Maintainers usually reply within 1 day
-
Bump `ledspicer` to v0.7.8 - Corrects Bug with newer Ultimarc IPAC Ultimate boards w/ newer firmwareOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
batocera-linux/batocera.linux#17329 · 1 reaction ·
Maintainers usually reply within 1 day
-
evmapy dies at startup if an input device disappears during its device scan -> game runs with no hotkeys (Select+Start exit etc.)Possibly taken @jonathanroehm claimed this 30 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
batocera-linux/batocera.linux#17210 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
batocera-linux/batocera.linux#16092 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
batocera-linux/batocera.linux#17422 ·
Maintainers usually reply within 1 day
All issues in batocera-linux/batocera.linux
Similar issues
-
hive size:simple
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
painted-porch/marcus#977 ·
Maintainers usually reply within 1 day
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FAIRmat-NFDI/sand#239 ·
Maintainers usually reply within 1 day