AmigaVision is the ultimate Amiga games & demo scene setup for MiSTer & Pocket FPGAs, Raspberry Pi + emulators — and Amiga 1200, 4000 & CD32.

It prioritizes low latency, correctness, and consistency across real hardware, FPGA, and emulation — with minimal setup time and a single unified distribution.

There are several other Amiga setups available for various types of hardware. This overview is meant to show how AmigaVision compares to other setups, and what we find important.

Why AmigaVision?

AmigaVision is not about having the largest collection of files — it’s about having the right versions, running correctly, with minimal latency, and minimal time between power-on and play. Our core design priorities are:

⏱️ Device Power On → Playable Game

Time-to-fun matters. From power-on to interacting with a game, the entire startup path is designed to be short, deterministic, and free of unnecessary layers, configuration screens, splash screens, or guesswork.

🧠 Intelligent Version Selection

The correct PAL/NTSC and OCS/AGA version is selected automatically. You shouldn’t need deep Amiga knowledge to know which variant runs correctly, has the right timing, or avoids known bugs — AmigaVision makes that choice for you.

⏱️ Lowest End-To-End Latency & Hardware-Accurate Behavior

Input, video, and audio timing are treated as a single system. Wherever possible, buffering, abstraction layers, and latency-adding defaults are avoided so games behave and feel as close to real hardware as possible.

📦 Download Size & Installed Size

Smaller disk images are a result of curation, not a limitation. Duplicate titles, broken releases, incorrect regional variants, and unused versions are intentionally excluded to keep the system efficient — with respect for both your time and your storage space.

🧩 Single, Consistent Experience Across Platforms

Real Amigas, FPGA, and emulation should behave the same. Platform-specific quirks and “this works differently over there” setups are a non-starter — the goal is one coherent system with consistent behavior everywhere it runs. You should be able to use the same setup across many different devices and platforms.

Everything else in AmigaVision — platform support, configuration choices, filesystem layout, and library curation — flows from these decisions.

The goal is to have a setup that feels like using a well-maintained Amiga rooted in the demo scene and games development from back in the day — not a collection of compromises.

Legend ✅ Supported
❌ Not Supported
⬜️ Not Applicable to Platform

🖥️ Hardware & Platform Support

  AmigaVision AGS 3 PiMiga 5
Real Amiga Hardware Supported ✅ ✅ ❌
Mister FPGA Supported ✅
❌
1		 ⬜️
Analogue Pocket FPGA Supported ✅ ❌ ⬜️
Raspberry Pi Supported ✅ ✅ ✅
Emulators Supported ✅ ✅ ✅
PiStorm on Real Amiga Supported ✅ ✅ ⬜️

🕹️ Device Power-On → Game Selection

  AmigaVision AGS 3 PiMiga 5
MiSTer 13s
35s
2		 ⬜️
Raspberry Pi 5 22s 2m 46s
30s
3
Emulator 4 10s 1m 6s ⬜️
TheA500 & Mini 5 5s 32s ⬜️

📦 Distribution & Curation

  AmigaVision AGS 3 PiMiga 5
Download Size 4 GB
17‑34 GB
6		 37 GB
Installed size 9 GB
30‑52 GB
7		 57 GB
Single Download for All Platforms 8 ✅ ❌ ⬜️
Duplicate-Free Game Library 9 ✅ ❌ ❌
Curated Game Lists 10 ✅ ❌ ❌
Open Source License ✅ ❌ ❌

⏱️ Performance, Accuracy & Latency

  AmigaVision AGS 3 PiMiga 5
Lowest End-To-End Latency 11 ✅ ❌ ❌
Optimal OCS/AGA & PAL/NTSC Version of a Game Selected Automatically 12 ✅ ❌ ❌
Cycle-Accurate Amiga 500 Setup for MiSTer
(Important for Demo Scene productions)		 ✅ ⬜️ ⬜️
Low-Latency Joystick & Input Timing 13 ✅ ❌ ❌

📺 Display & Video Output

  AmigaVision AGS 3 PiMiga 5
High-Resolution RTG Display Support ✅ ✅ ✅
Analog Video Output With No Added Lag 14 ✅ ❌ ❌
Per-Game 5×PAL Overscale Support 15 ✅ ❌ ❌
Correct NTSC Pixel Aspect Ratio 16 ✅ ❌ ❌

🌐 Networking & Online Features

  AmigaVision AGS 3 PiMiga 5
Easy Network File Transfer to the Amiga Without Removing SD Card 17 ✅ ❌ ❌
Internet Stack Included (Online Out-of-the-Box) 18 ✅ ❌ ❌

💾 Upgrade Model & Data Persistence

  AmigaVision AGS 3 PiMiga 5
Separate Persistent Saves / User Data Volume 19 ✅ ✅ ❌
User Data Survives Upgrades ✅ ✅ ❌
Upgrade Path Documented ✅ ❌ ❌
Custom startup-sequence entries survive upgrades 20 ✅ ❌ ❌

🧱 File System & Reliability

  AmigaVision AGS 3 PiMiga 5
Uses Corruption-Resistant File System (PFS), Designed to Minimize File System Damage 21 ✅ ✅ ❌

📐 CRTs, Scaling & Display Calibration

  AmigaVision AGS 3 PiMiga 5
Scanline Presets Included 22 ✅ ❌ ❌
Shadow Mask Presets Included 23 ✅ ❌ ❌
External HDMI Scaler Profiles Included
(e.g. RetroTink 4K, Morph 4K)		 ✅ ❌ ❌

🕰️ Era-Accurate & Specialized Setups

  AmigaVision AGS 3 PiMiga 5
Era-Accurate A500HD & A600HD Setups Included 24 ✅ ❌ ❌
Turn-Key Amiga CD32 Setup for MiSTer 25 ✅ ❌ ⬜️

Any errors in this comparison?

We strive to keep this overview accurate, and recognize that we can’t always be up-to-date on everything as the projects evolve. If you see anything that mis-represents any of the projects mentioned, file a bug in our issue tracker, and we will correct it.

Download AmigaVision

You can download AmigaVision here.

Frequently Asked Questions

PiMiga & AGS seem to have way more games and bigger size images?

They do — and that also means:

  • Duplicate AGA/OCS titles
  • Erroneous PAL/NTSC variants
  • Broken releases
  • Various random content (photo collections, etc)

AmigaVision intentionally curates fewer, verified titles so you don’t need deep Amiga knowledge to get the correct experience. And it is not leaving anything out, just removing unnecessary and duplicate content that is not considered relevant — respecting both your time to download and your storage space.

Why not RetroArch or generic emulation?

Amiga emulation is unusually sensitive to:

  • Cycle timing
  • Chipset behavior
  • Input latency
  • Display scaling

Generic emulator stacks optimize for flexibility.
AmigaVision optimizes for Amiga-specific correctness.

Why does latency matter this much?

Because the Amiga was designed around:

  • CRT displays
  • Direct joystick polling
  • Tight audio/video synchronization

Added latency fundamentally changes how games feel, even if they can seem to look correct in a screenshot or video.

Who is AmigaVision for?

  • People who care how games play, not just how many there are
  • FPGA, emulator and real-hardware users who want parity with the original experience
  • Anyone tired of tweaking configs instead of playing

What AmigaVision is Not

AmigaVision is not a “maximum content” distribution

It does not aim to include every known dump, crack, or regional variant. Games are selected and curated so that the correct version runs by default.

AmigaVision is not a RetroArch-style abstraction layer

It does not try to make the Amiga behave like a generic “core” inside a universal frontend. Amiga-specific behavior is preserved, and it has an Amiga-native launcher that works identically on every setup.

AmigaVision is not a “tweak it yourself” hobby project

You should not need deep Amiga knowledge, endless config edits, or per-game fixes just to get accurate results.

AmigaVision is not trying to replace original hardware — instead aiming to make it easier to use

Real Amigas, original disks, and hands-on experience is respected — AmigaVision exists to make those experiences easier to access, not to redefine or obsolete them. The AmigaVision team was part of this experience in the 80s and 90s, and treasures it for the real revolution it was at the time.

  1. AGS can be made to work with MiSTer if you edit out a lot of the startup-sequence, but it does not run on MiSTer out of the box. It also does not make use of MiSTer-specific features, like shared network drives, MiSTer’s RTG high resolution graphics support, etc. ↩

  2. AGS can be made to work with MiSTer if you edit out a lot of the startup-sequence, but it does not run on MiSTer out of the box. It also does not make use of MiSTer-specific features, like shared network drives, MiSTer’s RTG high resolution graphics support, etc. ↩

  3. Theoretical — PiMiga does not show a game selection screen but gets to Workbench where you can locate and start a game launcher. We added about 5 seconds for this step. ↩

  4. Tests done on the only Amiga emulator that runs on Windows, Mac and Linux: FS-UAE. Tests done on a MacBook M1 with SSD, with CPU settings set to Amiga 1200, but with uae_cpu_speed=max. ↩

  5. Time is from selecting the setup in TheA500 launcher until the game selector is available, as there is no way to autoboot a setup. ↩

  6. AGS has multiple different setups with widely different file sizes, so this lists the lower and upper range. ↩

  7. AGS has multiple different setups with widely different file sizes, so this lists the lower and upper range. ↩

  8. Some setups have different files for every setup — e.g. one for RetroArch, one for MiSTer, one for Raspberry Pi, one for real hardware, etc. This means you need to juggle many different versions of the same setup if you have more than one device where you use Amiga. AmigaVision has a single setup that works across all platforms. ↩

  9. AmigaVision excludes any broken and redundant versions of games, and does not have duplicated NTSC and PAL versions, since we pick the right one automatically. We only include multiple version of the same game (e.g. ECS and AGA version) when they have meaningful differences — e.g. different level sets. ↩

  10. In addition to top lists, AmigaVision includes curated lists made by creators, games organized by publisher, by musician, by theme, etc. ↩

  11. This includes input, audio and output latency, and refers to latency on systems that are variable, like Raspberry Pi. On systems that support FPGAs, like MiSTer, the latency will be generally be identical across setups. ↩

  12. AmigaVision picks the correct NTSC or PAL resolution based on where the game was developed, you don’t have to know which one is the correct version. We also pick the best version between the OCS and AGA versions — unless the game has substantial differences, like a different level set or game-breaking bugs. ↩

  13. AmigaVision uses 1ms USB polling on systems that support it, like MiSTer and Raspberry Pi. If running emulators on a desktop OS like Windows, macOS or Linux, it is up to the operating system settings. ↩

  14. Most ways to output Amiga to analog CRT TVs from computers and Raspberry Pi introduce latency. AmigaVision is configured for zero-lag MiSTer analog output, and on the Raspberry Pi via the RGB-Pi 2 adapter, supported in RePlayOS, which is what AmigaVision is built on. ↩

  15. For 4K and 1080p displays, 5×PAL Overscale will let you run a lot of games using much more of your display. This is currently supported on MiSTer, and we are working on getting it supported in WinUAE, FS-UAE, and Amiberry too. ↩

  16. Most Amiga setups scale NTSC resolutions incorrectly. NTSC does not have square pixels, instead they use taller pixels. This is currently supported on MiSTer and Amiberry. ↩

  17. This refers to a shared drive mounted inside the Amiga that you can transfer files in and out using a computer. Currently supported on MiSTer, and we hope it will be available on Raspberry Pi shortly. Not available on real hardware without network hardware. ↩

  18. Includes TCP/IP stack and basic networking tools for use with specialized Amiga internet tools; not intended to provide modern web browsing parity. ↩

  19. User data is stored on a separate HDF/volume that is excluded from system updates. ↩

  20. AmigaVision gives you a custom startup-sequence that gets stored on the separate Saves drive that you keep between upgrades, so you can customize AmigaVision without losing those customizations when a new version is available. ↩

  21. PFS is chosen for improved robustness over Amiga’s default FFS file system; no filesystem is immune to power loss or hardware failure. ↩

  22. AmigaVision defaults to using CRT scanlines on all supported platforms, since this is how Amiga games and demos looked like in the past. You can of course disable these, but friends don’t let friends play Amiga games with sharp pixels. 😉 ↩

  23. Shadow masks emulate the way CRT TVs Supplied on platforms that support shadow masks, like MiSTer. ↩

  24. Workbench setups for AmigaOS 1.3 and AmigaOS 2.0. The standard AmigaVision setup uses AmigaOS 3.1. ↩

  25. This is MiSTer-specific, and lets you load CD32 games directly from the menu. For emulator setups, there is usually specific functionality to play CD32 games. ↩