@venkman383 please provide more information

See https://retropie.org.uk/forum/topic/3/read-this-first

Please give an example of a file that doesn't work. A logfile will be useful. Which ROM files did you install and to where? Which lha files are you trying?

Based on this output, I think you'd need to set in EmulationStation the Audio Card to Device.

To get the name of the mixer (volume control), run

amixer scontrols -c Device

and choose the 1st entry and set it as Audio Device. For instance, in my case, the USB audio card is named 'Controller':

amixer scontrols -c Controller Simple mixer control 'PCM',0 Simple mixer control 'Headset',0

I would use PCM as the AudioDevice settings in ~/.emulationstation/es_settings.cfg:

<string name="AudioCard" value="Controller" /> <string name="AudioDevice" value="PCM" />

This should fix the audio not working (or the volume slider rather) in EmulationStation.

For Amiberry, I'm not sure why it's not working - maybe it's trying to use the 'default' card and it's not working ?

Try following the advice here and create a /home/pi/.asoundrc file containing

defaults.pcm.!card 1 defaults.ctl.!card 1

@jimi007 Ok, so, I was an OG Amiga user. I had a 500, 2000, and a 3000. Amiga was made long before any console has force feedback of any kind. So, why would there be any vibration response in any Amiga game ever?

I guess I am trying to figure out why you are expecting vibration from a system that never had it. It just seems on par with expecting stereo surround sound from an Atari 2600.

@jimi007 said in Speedball 2 CD32 DOS error 103 not enough memory:

Z3_RAM=16

Thanks @Jimi007. I've merged the change and added more Z3. On the next xml update (usually end of week) it should be taken into account.

@kpcollins This workaround helped me as I ran Amiberry on a Rpi3.

2021's adapted workaround:

Connect via SSH to your Rpi. Change to amiberry emulator folder: cd /opt/retropie/emulators/amiberry Edit file amiberry.sh: sudo nano amiberry.sh The change to be done is at line 20:
Change "$emulator" --autoload "$rom" -G

to

"$emulator" -autoload="$rom" -s sound_frequency=32000 -G Save and quit: Ctrl-X and answer y when prompted.

HTH

@nemo93 NP, thanks for sorting this out. As stated earlier the whole testrun was anticipatory for the time when kernel 4.19 is discontinued. So still a few years development time for full KMS.

@fentimanj hi! Let's continue the discussion here as I just posted on Amiberry's github. First of all I need to ensure you've read the "main" thread about Amiga and Amiberry (here). Then I'd need more inputs about your setup. For instance, which Retropie version you're using, have you updated the OS packages and/or Amiberry, etc? A full description about your setup always help as said in that post ;-)

If you got Amiberry logo and WHDload Autobooter screens this is not good. Especially for a game like Lotus 2 which has been heavily tested. Therefore I suspect you either do not have the very latest version of the WHD package of that game (should be Lotus2_v1.11_0497.lha as of typing) or you renamed the file. If you did the latter please don't and leave the name as-is.

Without further details from your setup I can't help much. Just ensure to get the latest Amiberry binary from Retropie Setup (or compile from source), check the names of your packages/.lha files and also double-check the Kickstart ROMs you got. They must match those listed here.

Hi,

Thanks for your prompt reply.
Sorry for not having fully specified my config.
When writing this very post, I was going through the template for it using the link you provided and came across the question 'usb devices connect'. At this point I thought of trying starting Amiberry without having my 2 Xbox (original) controllers connected, which are in turn connected to my USB hub.
And guess what...this did the trick! Amiberry now starts fine. I'm able to reproduce the issue so this is really the problem. Disconnecting either one of the 2 controllers will also work. But 2 at the same time won't work. I'm not having any other issues with both connected at the same time. I have a 5A PSU and never seen the rainbow logo with this setup except immediately after power on (bios screen).

I hope this may help anyone else stumbling upon this in the future.

@nemo93 Many thanks for the reply. I found the site I was using has 'empty' WHDLoad. I switched to another source (I won't post it here), but now working fine. Many thanks.

Peter

@mitu Thanks. It's possible I didnt trigger the upload. I can't remember :-)

@george-spiggott said in Amiberry Configuration File - can't locate:

@adambegood I'm also experiencing intermittent results from Auto height. I don't have Rick Dangerous 2 but Shadow of the Beast works fine for me.

Now that I've got the latest Amiberry after updating from Source, Shadow Of The Beast works fine for me also. I have some games with anomalies on auto-height still, but overall I am very happy with the way things are working.

On a slightly different note, I have got some games with graphical glitching (Deluxe Galaga and Plan 9 from Outer Space are the ones I recall). Do you know if there are any settings that might sort those out, or is it just something that has to be accepted?

Edit: Notice here you have mentioned graphical issues: https://retropie.org.uk/forum/topic/30213/amiberry-4-0-released/8?_=1617581491663

I guess these may be sorted as the core is worked on then.

@ecto Thanks for the configs, I did some analysis. First: I should have mentioned that after the change of this line to make -j4 PLATFORM="rpi4-sdl2" the amiberry must be rebuilded and installed (sudo ./retropie_packages.sh amiberry), please also make sure you use v4.1.6 of Amiberry and not the current master, just in case you missed it.

From the configs I found these differences to mine:

In amiberry.conf:
Diffs mine (which are also the default amiberry.conf settings) starting with - (red), yours starting with + (green)

$ diff -bB -u --color amiberry.conf amiberry.conf_usr_ecto --- amiberry.conf 2022-03-04 18:10:15.818541075 +0100 +++ amiberry.conf_usr_ecto 2022-03-04 17:57:08.000000000 +0100 @@ -5,7 +5,7 @@ rctrl_as_ramiga=no gui_joystick_control=yes use_sdl2_render_thread=no -default_multithreaded_drawing=yes +use_drawing_thread=no input_default_mouse_speed=100 input_keyboard_as_joystick_stop_keypresses=no default_open_gui_key=F12 @@ -15,11 +15,11 @@ rotation_angle=0 default_horizontal_centering=yes default_vertical_centering=yes -default_scaling_method=-1 +default_scaling_method=0 default_frameskip=no default_correct_aspect_ratio=yes default_auto_height=no -default_width=640 +default_width=720 default_height=512 default_fullscreen_mode=2 default_stereo_separation=7 @@ -38,49 +38,3 @@ default_whd_buttonwait=no default_whd_showsplash=yes default_whd_configdelay=0

You may change them one by one to my settings and retest after each change.

In config.txt:
I have seen you run a high overclocking. Maybe you can disable it for the tests on amiberry. I had different downside effects on Amiberry (3.3 and 4.1.6 when OC over 1950Mhz) (on my 4.19 kernel with fake KMS).
I assume you are using a (4k?) TV for the Raspberry. Can you try with a full HD computer monitor?
E.g., set hdmi_group=2, hdmi_mode=82 or set only hdmi_group=0, I guess you know the switches. --> https://www.raspberrypi.com/documentation/computers/config_txt.html#hdmi_group

And I did not review/change the WHDLoad file. I just let it sit there. You should however update it from time to time (within the Amiberry UI menu), if you haven't done it recently.

HTH

OK, i worked it out. Please consider this help request closed.

For anyone else having the same issue: don't map the "Retroarch keyboard as joystick" to any of the four available ports in Amiberry's controls menu.

The keyboard then works as a keyboard. I find it counter intuitive, but hey! It works.

@pmdci Capture.PNG

This is a screenshot of my directory and my amiberry works great.

We may have to amend the docs and don't recommend ds4drv anymore. Try with regular bluetooth pairing again - it should work.