It might look like a lot of effort, but Amiga games need a fair bit of tweaking before they’re run well on any version of UAE. There is a GUI but the mouse is all messed up in the current build. Once loaded up you use the Select button to switch between mouse and joystick. for Robocod: kickstart_rom_file=/home/modeler/Amiga/ROMs/Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).romįloppy0=/home/modeler/Amiga/Games/James Pond 2 - Codename Robocod (1991)(Millennium).adf uae extension, for example this is my config. You have to create a configuration file for the disk(s) you want to load, then save it with a. How do I use an Amiga core whilst running retroarch/Lakka on a Raspberry Pi 2? I wonder if this is configurable or perhaps the video output is not completely “hooked up” to libretro? RetroArch’s refresh rate is set to 59.950 Hz, so it looks like the core make up its own mind. I was wondering if anyone else can verify this before I submit it as an issue on github?ĮDIT: I just tried the core on a different Linux box (Openbox based) and the vsync was much better, comparable to Android. As I understood things, RetroArch itself handles the refresh rate and if one core vsyncs perfectly at 60 Hz, shouldn’t they all? I’m thinking then, PUAE is somehow not in sync with RetroArch but the Android build of the same core is? It’s clearly a core issue since the FBA SVN core and others run perfectly on the same Linux box. There is even some tearing at the top of the screen at times. Using exactly the same options on Linux (same version of RetroArch, v.1.3.4 which works perfectly with other cores) the scrolling is all over the place. When running the Android version at 60 Hz (ntsc=true) on my Nexus 5, the scrolling is perfectly smooth. Just playing around with PUAE v2.6.1 in RetroArch and something odd is happening.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |