Hi everyone, hope you're are doing fine (and staying safe!).

Since the last update, there have been a few but important updates. The biggest one of them all, is a feature that has been coming for quite a long time and I'm sure many people would want to see:

- Cycle-Exact mode (only for 68000 emulation). This can now be enabled from the GUI in one of two places: CPU panel (there's a new checkbox there) or the Chipset panel (the Cycle-Exact mode options were there already, but were not fully implemented. They are now). Keep in mind this mode is kind of slow, so it only makes sense on an RPI4 or faster device. It's not needed in most cases that we've tested, but there are a few that would not work properly unless this was enabled. To avoid any disruption to existing configs, this option is disabled by default (when selecting an A500 config) - this is the opposite of WinUAE, where it's enabled by default. Perhaps this will change in the future, we'll see.

Other than Cycle-Exact, we also have a bunch of improvements and bug fixes:

- Fast copper improvements

- Fixes for Load/Save of statefiles

- 64-bit JIT bugfix (DIVS)

- Added support for showing floppy images bootblock information in the GUI (new "?" button added). Note: this works best if you include the new "abr" directory and its contents in the same location as the Amiberry executable. It contains 2 XML files which help recognizing "known" bootblocks.

- Added Restart input event

- Custom chipset fixes from latest WinUAE beta

- Added the value for the CPU Idle slider on the GUI. 

- Hardfile handling improvements

- Added "$VER:" version information string in Amiberry binary, so that AmigaOS "version" tools can use it. This means that you can call "version" on the Amiberry binary from AmigaOS, and get back the current version string. It works with scripts that you might want to check with IF WARN etc. (e.g. in startup-sequence).

Meanwhile, we're still testing AmiKit for the RPI, and things are going well so far. The release date is getting closer, but we all prefer to postpone it a bit if necessary (to fix known bugs), than rush things unnecessarily. I hope you understand. :)