[Amiga] Amiberry + WHDLoad = Holy Grail - Amiberry's official thread

Aphex

@maxbeanz I meant "1-click to play" as a quick way to launch a game without having to bother setting up the amiga emulator for each games, not as in a keyboard-less setup :) I just thought having a .uae config file to automatically set up the emulator with best/optimized settings to be quite a plus.

I did try games in .adf format but i couldn't manage any of them to work. Now it was my first attempt at Amiga on Retropie back then and i think i my kickroms weren't in the right folders or something else i missed, i don't know. All i had was either black screens or that floppy loading screen.

nemo93

@Aphex please find below some example files that I do use as templates for all my games. Here we go...

to be used for any WHDLoad package/game that uses OCS/ECS and joystick as controller (eg. Battle Squadron, Speedball2 and many other games)
=> uae file
for any WHDLoad package/game that uses AGA and joystick as controller (eg. Chaos Engine 1&2, Alien Breed2, etc.)
=> uae file
for any WHDLoad package/game that uses OCS/ECS and mouse as controller (eg. Syndicate, MegaloMania, Cannon Fodder 1 & 2, etc.)
=> uae file

Just make sure to set the proper paths in those files to match your actual setup.

For the sake of accuracy below the parameters and value to set in the uae files depending on the chipset and controller type you want to emulate. The following settings are the most compatible I've found.

Those settings should work for most games either ECS or AGA:

; Display / Screen Setup
gfx_framerate=0
gfx_width=640
gfx_height=256
gfx_width_windowed=320
gfx_height_windowed=240
gfx_width_fullscreen=640
gfx_height_fullscreen=480
gfx_lores=false
gfx_resolution=hires
gfx_correct_aspect=False
ntsc=False

; CPU options
cpu_type=68020
cpu_speed=real
finegrain_cpu_speed=1024
;cpu_model=<<cpumodel>>
cpu_compatible=False
cpu_24bit_addressing=True
cachesize=0
cpu_cycle_exact=True

; Memory 
a1000ram=false
chipmem_size=4
bogomem_size=0
fastmem_size=4
z3mem_size=0
z3mem_start=0x1000000

; Chipset 
chipset=aga
chipset_refreshrate=0.000000
collision_level=playfields
fast_copper=False
immediate_blits=False

rtg_nocustom=true
rtg_modes=0x502
gfxcard_size=0
gfxcard_type=ZorroIII

; Misc
bsdsocket_emu=False
show_leds=false
kbd_led_num=-1
kbd_led_scr=-1
kbd_led_cap=-1

; Sound
sound_output=exact
sound_channels=stereo
sound_stereo_separation=3
sound_stereo_mixing_delay=0
sound_frequency=44100
sound_interpol=none
sound_filter=off
sound_filter_type=standard
sound_volume_cd=20
sound_auto=yes
synchronize_clock=yes

@maxbeanz: you're absolutely right regarding Barbarian (Palace version... what a game!!). I've added it to my bug report on Github. To be honest, it's the first game running at too high speed to be playable that I've been able to see. As I wrote earlier I've tested something like 130+ games, all running fine. If you have other good cases please let me know or feel free to add them to Github as Midwan is closely watching for it.

ballboff

@nemo93 Hey thanks for your advice. However, I couldn't get this to work as when I loaded up jstest every button I pressed came up with a letter as it thinks I have a keyboard attached. So my buttons are 7, 9, z and 1, and then h, 0, x and 5. 1 and 5 are start and select, 7,9 and z are a, b and c.

Aphex

@nemo93 Wow, thanks for that! I'm gonna try those config files this week and let you know!

ballboff

I feel like i'm getting closer. I've created a config file for alfred chicken. When I load this up in notepad it says that button a is 61 and button b is 63. These are equals and question mark according to the reference file. However, when I press page up (or down I can't remember) that seems to be my fire button A?! Escape quits back to the menu and space takes me into the options menu.

Aphex

@nemo93 I checked your settings and applied them, yet i still have problems with the same games. For exemple, try Dune if you have it. It's just stuck on a black screen as soon as i launch it :/ If yours is working, then maybe my problems are rom-related?

nemo93

@Aphex Dune does run fine (as well as Dune 2, both are amazing btw!). I'm using version 2.5 (29.01.14), which is the latest version as of typing. I'm using the french version and I don't even have the famous intro bug as described here (see notes bottom of the page). If you're using any other langage version there should be no problem whatsoever. Try to have a look at the file created during launch process and named after whdscript_debug, open it with a text editor. Sometimes there are useful info about why the game didn't start or launch.

The uae file I'm using is there yet it's no different from the settings shared earlier. Make sure you also have a copy of the kickstart roms in this folder as described in my first post <RETROPIE>/roms/amiga-data/_BootWHD/Devs/Kickstarts/ (where there are a bunch of *RTB files).

@ballboff I'm really sorry but I have no idea what you mean by "keyboard encoder". At this stage, I can only direct you to the Github page of Amiberry where you could log an entry to find a solution to your problem (if you do so make sure to share useful and detailed info about the hardware you're using as well as your current setup).

ballboff

@nemo93 I'm using an arcade setup. Just assume for arguments sake i'm using a usb keyboard because that's essentially what the pi recognises it as. My settings are hardcoded to use page down as fire button A and I think button B is something like the home button.

Whatever I set the controls to within the settings of the emulator itself it ignores these settings. This means I can't seem to change the controls. I need fire button A to be mapped to keyboard button 7 and I need button B to be mapped to keyboard button 9

Aphex

@nemo93 Sorry for the late reply but it took me a while to figure a few things out. You suggested to check thewhdscript_debugfile and it was indeed a good place to stard since the debug file was repeating the linesDOS-Error #205 (object not found) on reading "devs:kickstarts/kick34005.a500". So i went on to check and compare folders and files of different working RetroPie setups i've found online...

I checked that/Devs/Kickstarts/folder and it turned out there was a few file size difference between the kickroms of my setup and the working ones. So i replaced them with the ones from the working setup (still wouldn't work), then i replaced the files from the/amiga-data/_BootWDHfolder (still wouldn't work), then replaced the game files (actually, only the auto-startupfile was different). And now it worked!

tldr version: my kickrom files, WDHLoader files and some configuration files were different, even though the project source i've got them from was all about proposing a fully working archive paired with configuration files...

I think i'm gonna start everything over from scratch with the latest version of Amiberry and make sure i have all the right files.

AndersHP

@ballboff I'm on an arcade setup also, with my buttons acting like keyboard presses. Before I dive into this Amiga Emulation, I have to be positive that there's a way to map game buttons to specific keyboard buttons. Seems like this is still not possible?

ballboff

@andershp I've seen on the github page they are still working on it. I'm not sure if uae4arm is capable of this as I have seen if you name the disks disk 1 of 2 etc it will autoinsert all the disks needed and no disk swap us required. Meaning you don't need the whd setup that amiberry uses

nemo93

Folks, just to keep this thread active I'm glad to inform you that Midwan has returned and he's working on updating Amiberry. You could see that by yourself by checking the dedicated github page I've mentioned earlier. Stay tuned and keep posting feedbacks!

H3RBSKI

@nemo93 thanks for the reply in my thread about amiberry not showing in my list.
i followed the steps in your reply but still no joy:( its driving me mad. any other suggestions are great

HoraceAndSpider

Just to pick up a few points in this thread...

Many of the games which run too fast could be fixed for everyone if the fixed setting (slower cpu speed) was submitted to the UAE Config Maker GitHub for the specific game ;)

Regarding "out of date" slaves the UAE Config Maker will have auto-slave updating added to it in the future(if anyone has a python script capable to unpacking LHA files,ideally universally, then this could be addressed very quickly!)

At the moment I am working with the Amiberry primary dev (midwan) and I am adding lots of new elements into the controls section, including more universal (retroarch) controller mapping and game-specific custom control mapping. There are videos online of this if you want to see it in action, and a GitHub branch of Amiberry for you to find for yourselves :)

Lots of winuae codebase changes are coming in the next Amiberry release which will hopefully improve compatibility and the stabilisation of speed issues is something that is being looked at. On a related note the uae4arm pandora dev has been directly contributing to Amiberry also.

HoraceAndSpider

@andershp next version of Amiberry has cursors and other buttons used for cd32 layout mapping ro the keyboard.

I am going to look at how to make this remappable to other keys (at user preference) also but this might be 2 releases away.

HoraceAndSpider

@administrators hopefully there is no problem with the links being provided to the guide anymore following this announcement, and the changes to the parent site that have been implemented today:

http://www.ultimateamiga.co.uk/index.php/topic,10013.0.html

I have also emailed @BuZz to explain the situation in detail, as I am hoping this will help in having more active involvement with the 'WHDLoad for RetroPie' project directly with this forum, without the need for you guys having to worry about copyright issues.

@nemo93 are you on the Facebook support group? It sounds like your input could be quite useful

@Aphex if you have issues getting configs created for any games which you obtain, please speak to me so that i can resolve the issues. :)

nemo93

Many thanks @HoraceAndSpider, truly awesome and fantastic to read you here :) Unfortunately I'm not on Facebook. Yet I'll be glad to help or assist any way I could as I have some spare time these days. That's why I did my best to answer any questions about Amiberry/WHD on this forum lately. Let me know how I could help you and Midwan. I have no dev knowledge so all I could do is to test games/roms and provide feedbacks as I did already on the Amiberry's github page as well as helping others to configure their Retropie.

@H3RBSKI: thanks to @HoraceAndSpider we could now safely share this ultimate guide here without breaking any forum rules. Everything is explained in great details and this is basically the one I've followed the first time to install and configure Retropie on my Pi3. Focus on Step 2 where it's explained how to make Amiberry to appear in EmulationStation. If you still got issue let us know.

Can't wait to put my hands on Amiberry newest version ;)

AndersHP

Following this with great interest. I have an original Amiga 1200 with registered WHDLoad installed, but I'd really love to have my Amiga games available on my bartop arcade also. Especially shooters and pinball games will be awesome!

psyke83

Regarding the advice to use edit the gfx_framerate, I would suggest that it's unnecessary. A Pi 3 is capable of emulating an A600/A1200 at stock speed (it can do much better, in fact).

If you notice odd stuttering, the problem is your TV/monitor refresh rate. 99% of Amiga systems and games are PAL, which synchronize the vblank to 50Hz, but the Pi uses 60Hz modes by default.

The real solution is to enter the runcommand menu for the Amiga emulator, and change the screen mode to an appropriate resolution with a 50Hz refresh. This should eliminate 100% of stutter, at least on a Pi 3.

HoraceAndSpider

i agree regarding gfx_framerate=0

i dont know how the default ended up being =1 if i'm honest. I recall a user having problems with the =0 and I added the option to change this into the hostconfig line of the UAE Config Maker.

Somehow maybe this ended up in the default settings as =1 but can easily be fixed when generating your own Config Files