[Amiga] Amiberry + WHDLoad = Holy Grail - Amiberry's official thread
What about controller config - I couldn't really find anything about this.. Is it easy to map keys to use an iPac, just like the retroarch.cfg files?
maxbeanz last edited by
@andershp Unfortunately, custom controls are still not possible yet and the porters of the Raspberry Pi version haven't made any progress in several months :-(
(On a side note, the Android version works great!)
So.. keyboard is necessary, or?
EctoOne last edited by
@andershp depends on the games. you can map some keys to your pad with xboxdrv, but setting up different mappings for each game requires some work.
I'd really love a retroarch based Amiga emulator.
Hi, where can I find a full list of what these numbers are? I need to re-set up my controls for buttons 0 and 9 on the keyboard and i, and w and things like that. My machine uses a keyboard encoder so I'm having trouble getting amiberry to recognise my fire buttons...
@ballboff : you could use the utility "jstest" on the command line to find out your button ID number. Just log to your Retropie via SSH and type in
jstest /dev/<your joypad>.
@AndersHP : I'd love to see one in Retroarch too! For the time being, keyboard/mouse is only necessary for a small set of games which rely intensively on these devices (ie. Populous 1 & 2, Worms, LucasArts games, etc). No need to have these to have fun with Speedball2 or any Bitmap Bros amazing games for instance though.
@maxbeanz & all: I do slightly disagree with you on one thing. Games run at normal speed with this method. At least I didn't notice anything that would make the games completely unplayable. To be on the safe side there's a parameter you must enforce in the .uae files. It is this one =>
gfx_framerate=0. Just make sure it's there with a 0-value and you should be good to go. Of course it will be perfect when 'Cycle Accuracy' you mentioned will be implemented within Amiberry.
@maxbeanz: the link I'm refering to definitely contain outdated packages however my goal was not to direct users to a site with the latest packages available. First it's against rules of this forum as @EctoOne pointed out. Second people could find these without my help :) I was just willing to share this WHDLoad discovery with the community and give the people a few hints about it. After that people, like I did, could find the latest/newest packages (tip: find the latest updates on WHDLoad for your game then... Google is still your friend). With the WHDLoad method to update a game is as simple as deleting old files from a game directory and copying over the new ones and you're sure it's going to work.
I've tested with nearly 130+ games and I have no troubles except the ones listed -mostly AGA- in this Github report. By the way, Midwan is still around and looking after the Amiberry project (yay!). Look at the comment in the aforementioned report.
Amiberry (UAE4ARM based) and WHDLoad truly are your best friends if you want to emulate Amiga on a Pi in the easiest way possible. Really. Just give it a try and if you have any issue, post them here.
maxbeanz last edited by maxbeanz
@nemo93 The gfx_framerate=0 command you're referring to just turns off Frameskip. You should never have frameskip on in the first place as it halves the framerate to 25fps. Not sure why anyone would have this set on as default, thats just sillyness. There are lots of WHDLoad games that run too fast. I haven't used them for a while now as nearly all ADF versions play at the correct speed, and the games I like to play don't take long to load with floppy speed 400 (which is safe for all games). For example, one game that I remember was Barbarian The Ultimate Warrior, try playing that in WHDLoad !
I tried to give the Amiberry + WHDLoad combo a shot and managed to get my hands on some auto-install scrips that allows you to automatically create .uae config file of each of your games, with folders for standard games, AGA, CD32, etc.. It does work nice for some games, but also fails for some others. I've found a romset with its specific .uae config file set but like @maxbeanz pointed out, it might be an outdated pack. Still i feel very enthusiast about it since it does provide a fast "1-click to play" solution right from the ES menu, with a ready-to-scrape list.
Now i just have to find that better pack :)
Whenever the best solution has been found (or the best middle-ground, i mean), a step-by-step tutorial video might be VERY helpful for non-expert users like my sorry-self.
maxbeanz last edited by maxbeanz
Still i feel very enthusiast about it since it does provide a fast "1-click to play" solution
Did you know that you can start ADF games from the ES menu with 1-click ? Multi disk games are a bit hit or miss though. I like using ADF's as that was the original back in the day. Hardly anyone had HardDrives and WHDLoad wasn't even invented, and nearly all ADF games have a trainer cheat menu ! There are tons of games that I had about 25 years ago that I never even got past the second level (but never bothered cheating at the time because I had better things to do) !
At the end of the day the Amiga is a computer so you should really use/need a keyboard. CD32 games would be best for a Joypad only experience but currently custom controls on Amiberry don't work and it's only hacked to use a PS3 controller. 'RecalBox' has a fully working CD32 addon with working controls.
@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.
@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.
@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.
@nemo93 Wow, thanks for that! I'm gonna try those config files this week and let you know!
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.
@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?
@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).
@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
@nemo93 Sorry for the late reply but it took me a while to figure a few things out. You suggested to check the
whdscript_debugfile and it was indeed a good place to stard since the debug file was repeating the lines
DOS-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.
@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?