Replies: 2 comments 2 replies
-
I actually have a MegaAGS setup here ~ typically I go for fullscreen, but in this YT video I've opted to show windowed mode. I could've double-clicked on the icon, but chose right-click, execute.... for the longhand effect ;) I have tested on teevee, but alas I really dislike Amiga titles + widescreen aspect ratios...usually speaking, that's part of one of my x86-64 thin-client setups, connected to 19" 4:3 display (with builtin CRT modes), and it works best there (I consider 16:9 aspect ratio somewhat 'blasphemous' wrt properly rendering Amiga titles to scene ... workbench being the exception of course =) I honestly have no idea what the config.uae looks like ~ I created it with the amiberry GUI ....it's not very often I find the need to futz with amiberry.conf directly. I'll include it for reference's sake. Probably I just wanted to more or less demonstrate your last point above, as being entirely possible. I do know this however...fs-uae 3.x is a very different thing to amiberry, in many different ways =) Obviously, midwan will have to weigh in on the technical questions. |
Beta Was this translation helpful? Give feedback.
-
Jumping straight to the bullet points:
I've found the best results to be either using Full-window or Windowed mode. Fullscreen mode under SDL2 sometimes gave... unpredictable results. However, Full-window mode does mean that we'll be using the current resolution the host has, and the GPU will do the scaling to the full size of it. I haven't seen a problem with this approach, except with scenarios where the refresh rate is less than the emulated one (e.g. on 4K TVs which might be doing 25Hz instead of 50Hz, as is the case with the RPI4 by default). Obviously this would work fine with 640x480 as well, and the output will be scaled accordingly automatically.
I don't have Integer Scaling as an option implemented yet. Only Aspect Ratio correction, which is enabled by default. Maybe in a future update :)
This is available as the "Auto-Crop" function. It can be enabled by default (from
There is no shader support in Amiberry yet. This was planned with an OpenGL back-end, which has not really materialized yet (there is some experimental code, but it's still buggy). There is Scaline support built-in, but it's not as good as a proper shader. It might be "good enough" for your needs. :)
This is do-able as well, since you can associate Amiberry as the default handler of such files. The alternative would be to have a shortcut that runs a script, which executes the emulator along with any optional parameters you may want. The later approach was usually done in older versions of Amiberry, but with the recent updates to handle filetypes directly as a parameter, it should not be necessary.
See my comments about using Full-Window above, instead of Fullscreen. Keep in mind that if you ask for Auto Crop to be enabled, the actual image output will no longer be the Amiga native one, but smaller (depending on the active pixels). It will still be scaled keeping the aspect ratio, of course. Also, the |
Beta Was this translation helpful? Give feedback.
-
Hello! I am one of the maintainers of the AmigaVision project, and we aim to take out the complexity and frustration out of Amiga emulation. The project started on MiSTer, also works on original hardware (A1200/A4000/CD32), as well as Analogue Pocket FPGA and other FPGA boards like MiST and SiDi.
We recently started to look into seriously supporting emulators, and it’s been… a journey. UAE configs are extremely confusing, and when you layer things like WinUAE/FS-UAE/Amiberry/PUAE on top, it gets messy, and I still don’t have an emulator setup that lives up to the standard we are trying to provide.
High level, here’s what we are trying to accomplish (from the end-user side) — I don’t know if Amiberry can do this, but here’s what we’re aiming for:
AmigaVision.fs-uae
, and the emulator loads straight into the setup.Is there anything in this list that seems hard to implement with an Amiberry setup? I have hit some walls/bugs around trying to request 1080p via either fullscreen or “fake fullscreen” via a window, but I don’t know enough to file useful bug reports yet. No matter what I specify of the combinations, it either ends up at the native resolution of the display, or falls back to 800×600px in the settings.
Here’s what I have tried so far in
amiberry.conf
:Beta Was this translation helpful? Give feedback.
All reactions