[UAE4arm] building issues? + control issues - help
-
hi, I've updated from source this emulator as I was unsure if the latest github code is part of the binary that comes with RP. Compiling went well but then I've spotted the first issue: the
emulators.cfg
file gets updated in the process. Problem is I'm using what's being described in RP wiki to launch games straight from ES. No need for the+Start UAE4arm.sh
whatsoever I only had that line:uae4arm = "pushd /opt/retropie/emulators/uae4arm/; ./uae4arm -f %ROM%"
but the RP update process replaces that line by something else. I figured out how to avoid that. I simply add a line as follows:
auto-uae4arm = "pushd /opt/retropie/emulators/uae4arm/; ./uae4arm -f %ROM%" default="auto-uae4arm"
and I hope it would do the trick. That was the first issue, no big deal.
Second issue is that controls are not working any longer I'm not sure to understand. It worked flawlessly before (RP 3.8 at least). I'm wondering if it's due to RP or emulator itself. In short, mouse and pad are not recognized during games. I could use the GUI no problem and games launch as normal I simply can't get to play the game as I can't control anything. I'm using a 360 wireless, I got a standard USB keyboard and mouse.
-
it is normal that it will update the emulators.cfg commandline - as you have found out, if you want custom ones, you need to use your own names etc.
There have been controller related changes upstream - may be related - install the binary to compare (which was built a couple of weeks ago or more)
-
I'm building latest as there are also new changes being added. I'll test also with the binary. I'll report here the outcome.
NEW ISSUE: when updating from binary or source the kick roms are being deleted each time from the "BIOS" directory and have to be copied over again. This is annoying :-(
-
Building of the new code base fails here. I've updated via the "binary" but same issue as stated above... I'm a bit puzzled. I could see mention of CD32 in the GUI perhaps I've done something wrong? All I did is try to update the emulator via RP menu first via the source (failed) then via the binary...
My system details here: https://retropie.org.uk/forum/topic/3624/fba-next-can-t-compile-install-from-source
-
aah you are the one with the badly ungraded raspbian - I suspect something is still wrong with your setup still and I don't think it's worth my time debugging this - try from a fresh image/raspbian.
-
You probably have old wheezy packages kicking around still - if you try from a fresh image and it till doesn't work we can go from there.
-
Correct I'm that one :( Sorry about that. I've done a complete review of the system and package-wise it's all good, really. I've removed everything that matters to build stuff and let RP script install the correct packages (sweet btw!). Outcome differs slightly:
- I was able to build the latest uae4arm this time, no problem (yet the deletion of kick roms still persists :(((()
Still got the issue with fba-next, it keeps throwing me error. but not as same location every time... Start to wonder if it's not an overclock issue or something (my rpi2 is overclocked to the pi2 setting from raspi-config that's all).
I still need to do more thorough testing with this new uae4arm version (which brings CD32 support yeah!). However the issue with the kickstart roms is really annoying if you could have a look at it please? The deletion occurs each time the uae4arm package from RP menu is updated irrespective of the method... Thanks and sorry for my packages :(
-
I will look into the kickstart issue. Where are you placing them out of interest ? (full path please).
-
I see the kickstart issue. will fix.
-
I place these files under
/home/pi/Retropie/BIOS/
. The 2 of them,kick13.rom
andkick31.rom
. Do note that I got a couple of other files (syscard3.pce and SCPH1001.BIN) there and 2 directories (fba and mame2003). Those are not being deleted. Only the kickstarts. -
Should be fixed now if you update retropie-setup
-
wow that was fast indeed!! I'm currently building again fba-next with lower overclock setting hence give me some time please. I don't see how your fix wouldn't work! thanks again!!
-
I do confirm issue with the deletion of the kick roms is now gone (either via binary or source options). Yet I still having issue with the controls. I'll keep checking in the coming days to see if upstream got fixes. Though the binary option from RP doesn't help and I'm really puzzled by that.
I'll give another look soon. THANKS.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.