caitsith01 wrote:Hi all
First up let me say a big thanks for all of your work on this great project, especially Chips. I was able to build and run the latest version on an RPi3 with minimal problems.
One comment about installation - I had issues installing in place of my existing UAE4ARM installation because the config directory was read only for the default pi user. This resulted in weird freezes in the GUI and also in me not being able to save my config settings.
Now... I have questions. Many questions. Some of them are only half addressed in this thread, I think. I hope someone will help if they can:
1. Is there a button combination to exit the emulator using a joypad? Using both an 8bitdo SNES pad and an X360 wired controller, the conventional start+select does nothing for me.
2. Custom joypad button mapping... does this actually work at all? The option in the GUI for this allow me to tick it and allocate buttons, but they never do anything. For example, I want to map mouse L-R to joypad X-Y so that when stupid "crack" screens come up before games which require a mouse click to skip, I can just hit X. But even when I set this, it doesn't stick. No matter what I do, the emulator only recognises the d-pad plus A and B on my joypad, but never lets me use X and Y or the other buttons for anything.
3. No matter what I do, the emulator still wants to use my mouse. If I completely disable the mouse, or even if I set Port0 to joypad and Port1 to mouse (via nubs) I can't use the mouse at all. Does the emulator actually work with just a joypad and no mouse? What about two joypads?
4. People are talking about hardware resolutions... where are these set? The only options I can see appear to be directed to letting you set the emulated (Amiga) res, not the screen res of your actual hardware. E.g. how do I force 1080p output (and do I want to do this anyway)?
Regarding 1 and 2, you may want to give my version a try - it has improvements in that area specifically:
https://github.com/midwan/amiberry
3. I've never had to test this, but if this is a problem we should fix it of course. The best way to handle this would be to open an issue on github with a clear description...
4. The emulator will use whatever native screenmode you are running on the Pi, and scale the Amiga output to that.