uae4arm v0.5 - testrun under retropie4.1 by amiga professional

[RustyMG]

@voljega. Ratte's cd32 emu setup definitely uses uae4arm. I know this as during the setup process you need to pick the correct version depending on what Pi you have, deleting the other 2.

[lolo]

Amiberry is uae4arm emulator updated and optimized with bug fixes.
This is the version to have.

[Ratte]

@Substring said in uae4arm v0.5 - testrun under retropie4.1 by amiga professional:

@RustyMG If you're talknig about retropie, their philosophy is much different than ours. In their opinion, it's up to the user to configure every emulator on their own, when recalbox aims a "configuration-less" experience. Of course I could have added an amiga emulator and say "guyz, plug a keyboard, and you're on your own to configure", but that's not how we, at Recalbox, see things.

With the CD32 Emulator this is no longer a problem.
No keyboard - done
No mouse - done
One unified configuration - done

So, as long as we can't release a "recalbox-spirit emulator", we don't do it.

recalbox-spirit - done (in my opinion)

we only add emulators that have a meaning

It is listed under "Board Compatibility"
https://github.com/recalbox/recalbox-os/wiki/Board-Compatibility-(EN)
I understand this as "emulator that have a meaning"

Anyway, no time yet for amiga. Among things i'm trying to solve, C64 is the priority.
Amiberry is raspberry pi only, which is quite a b*mmer for odroid boards
... Having an arch specific emulator is not what I believe to be the best thing for recalbox. It would really sadden me (and take sooo much dev time) to have say amiberry for pi, uae4arm on odroid and fs-uae for x86 ...

The offical way seems to be different ...
https://github.com/recalbox/recalbox-os/wiki/Board-Compatibility-(EN)
It is not the only emulator thats integrated for one specific system.
Take x86 (Wii) or missing emulators for PI1&PI2.
From this perspective, I find your argument quite weak.

And CD32 is like emulating A1200 ... it's still the same deal : have the emulator, and preconfigure it in the recalbox philosophy and scripts. To be honest, I personnaly don't have much time for now to do anything else than support.

You've listed a lot of personal reasons.
I feel somewhat reminded of the 80/90s computer wars.
Where can I find offical developer support?

BR
André

[Substring]

@Ratte said in uae4arm v0.5 - testrun under retropie4.1 by amiga professional:

Where can I find offical developer support?

That's me dude. I'm one of the developpers. Depending on what you're trying to achieve, there is a wiki for compilation basics. The next big thing is understanding buildroot as we don't add pre-compiled binaries.

[Ratte]

@ Substring
Before I start with things like compiling and buildroot i would like to understand the internal workflow of recalbox.
Right now i start the emulator with the following command:
<Command> ./ usr / bin / uae4arm / scripts / start.sh% ROM% </ command>

All other emulators are started by:
<Command> python /usr/lib/python2.7/site-packages/configgen/emulatorlauncher.pyc% CONTROLLERSCONFIG% -system% SYSTEM% -rom% ROM% -emulator% EMULATOR% -core% CORE% -ratio% RATIO% </ Command>

Is there any description or document how to add an emulator in the right way?

Thanks in advance.
BR
André

[Ratte]

@Substring:
reminder

[Substring]

@Ratte yo gotta learn python ... but as i'm the one who mostly works on configgen, consider yourself a lucky man ^^

There is no doc, it's not such a big tool. The easiest is to read a generator, understand that we generally have 3 files for a generator :

• the generator itself which drives the wole configuration + launch of the emulator
• sometimes a controller file that handles controls configuration
• sometimes a config file to handle general configuration of the emulator

Next is to edit emulatorlauncher.py :

• add the dependencies (all the import sutff)
• Add a Emulator['amiga'] default line

Don't forget to add the necessary files in the setup.py.

The only step-by-step i could recommend you for now is :

• create a uae folder in generators
• find a small xxxGenerator.py, copy it over, rename functions/methods as well as the file, and just add a hard coded launch command
• add the necessary lines in emulatorlauncher.py
• add the necessary lines in setup.py
• copy over to the pi, regen the setup
• learn to manually start configgen rather than by ES

configgen is half of the job, the other half (the package) is a whole different story. I made the necessary packages for uae4arm-rpi, i guess they could be a good start depending on the dependencies of the emulator you wish to add.

[DerSchatten]

@korni said in uae4arm v0.5 - testrun under retropie4.1 by amiga professional:

@Ratte

Ich habe mich mal an dem Theme versucht...

Hier zum Download: http://bit.ly/2nAFaeP

does anyone still have these files, please?
The link is dead.

[voljega]

@derschatten see the other thread it's still alive there

[DerSchatten]

what other thread do you mean?
The AMIGA CD32 EMULATION - HOW TO - ? There is no link to this svg inside.

[voljega]

@derschatten oh sorry i thought you were speaking about the full emulated solution

[DerSchatten]

nothing??? Nichts? Gaaar nichts?

[ejr]

Hi, ok voljega I tried your "amiga solution" and it's great. But there is only one problem I have... Buttons and directions on my Arcade pad doesn't work. the only one key that works is "square" (or X in xbox controller) which quits emulator. The keyboard and mouse is working fine. What can I do with it?

edited: I forgot I have uae4arm gui, but when I select the correct stick and save config it doesnt save, I have to set all again at start each time. Hmm maybe I will try to exchange saved config with the default one...

[ejr]

I cant edit my post above... so edited2: I just configured everything in the gui using mouse and keyboard then saved configuration. Then I moved saved configuration to the main folder and renamed it as default one and then I ran genUAE script for all my games and it now works great