The detail view renders raw memory as pixels: every bit is one pixel. Each row is one bitplane scanline, so graphics in chip RAM show up as recognizable images. Drag or scroll to move through memory; type an address in the $ field to jump, or pick a detected bitplane from the list on the left to jump straight to it.
Bitplane detection
The panel continuously tries to work out which memory areas are currently used as bitplanes by watching the Amiga's DMA and measuring the line-to-line stride. The detected areas are listed on the left, largest first.
With auto-select enabled, the detail view automatically follows bitplane 1: whenever the guessed bpl1 area changes (for example on a screen or buffer flip), the view jumps along with it so you keep seeing the active image. Turn it off to stay parked at a fixed address.
Colors (write tracking)
Freshly written memory briefly lights up in the color of whoever wrote it, then fades back to the amber cold palette. This shows which areas are being written right now, and by whom:
set bit (1)
cleared bit (0)
Cold (idle >5 s)
Blitter
CPU
Great for telling apart blitter graphics build-up from CPU writes.
Fade length
How many rendered frames a write stays highlighted before fading back to the cold palette. The fade freezes while the emulation is paused.
250 frames
Slomo speed
How fast slow-motion single stepping runs: the delay between the frames it steps through. Lower = faster.
one step / 500 ms
resetting machine, please wait ...
loading please wait ...
converting to Amiga hard disk ...
Amiga Operating System ROM
The emulator needs a kickstart system ROM file. Please drag the missing file into the empty chip socket. Or just touch or click the sockets.
kickstart rom
kickstart ext
(optional)
Once loaded vAmigaWeb will try to store these files to your browsers local storage. Then on subsequent starts it will take the rom files from your browsers local storage instead of asking you again for them.
vAmigaWebpowered by vAmigaCore
most settings are permanent and will be saved to your local browser storage
tap on individual workload charts to visualise bus activity (dma debug)
use shader rendering for full resolution in interlace modes
run ahead reduces input lag by pre computing frames. The lag improvement is 20ms per number of frames ahead. Basically emulation itself introduces a slight lag of less than 20ms. Therefore, setting run ahead = 1 frame already ensures the original responsive feeling. run ahead = 0 frame saves battery life at the cost of a slight lag.
one fire button when using virtual touch joystick the right half of screen is that button. All external controller buttons are mapped to button1. (original Amiga games before 1990 had only 1 button)
two fire buttons when using the virtual touch joystick the right half of screen is divided in two vertical stacked touch areas. All external controller buttons are mapped alternating to button1 and button2. When using keyboard joystick emulation button2 is mapped to key 'B'.
three fire buttons when using the virtual touch joystick the right half of screen is divided in three vertical stacked touch areas. All external controller buttons are mapped alternating to button1, 2 and 3. When using keyboard joystick emulation button2 is mapped to key 'B' and button3 to key 'N'.
touch joystick and mouse touchpad layout
move | buttons the left half of the screen detects movement input and the right half detects button presses
buttons | move the left half of the screen detects button presses and the right half detects movement input This layout can be more comfortable for left handed players
exact timing autorepeat and simultaneous keycap presses (disables default scroll gestures on keycaps, scroll gesture possible only on gaps around the keys)
smartphone like native scroll gestures on keycaps (press starts after finger is lifted from keycap for a duration of 100ms)
mix of both tries to mix both worlds... i.e. exact timing and simultaneous presses but also scrolls keyboard when swiping the finger on keycaps. disadvantage: also does a keypress when only scrolling was intended