Libretro core v1.4

How to use the core

Libretro cores are shared libraries. To use this core you will need to have installed some libretro front-end, such as RetroArch, and import the core file into it.

Requirements

The Vircon32 core requires either OpenGL Core or OpenGL ES 2/3.

What's new in version 1.4?

This version modifies savestates to include the state of the BIOS and make them more robust. This will fix graphical glitches in some games. Note that this BREAKS COMPATIBILITY with previous savestates. If you try to load a savestate saved with previous core versions it will not work.

Also, this version changes the internal name of the core variable (from enable_frameskip to vircon32_enable_frameskip). Adding the core name as prefix helps certain front-ends and configuration systems. But again, note that it might break previous configurations.

Known issues

Game compatibility should be 100%, but there are a couple of things to note about playing Vircon32 using the libretro core:

• Savestates do not save the screen contents, which are persistent on Vircon32. This is done on purpose to reduce size and complexity on savestate handling. Otherwise it might get too taxing to enable rewinding. Most games will update the screen every frame, but once in a while you can have screen glitches for a moment if you save a state during menus or screen transitions.
• There is not an easy way to change the memory card on the fly. This is normally not needed but there could be (very few) games that rely on this, like the Chip-8 emulator. These might be better played on a standalone emulator.
• On the libretro core, currently all 4 gamepads are considered connected at all times. This is not an issue, but if you run the gamepads test it may behave differently to other Vircon32 emulators.

Supported systems

The core currently works under the following systems (possibly more):

• Windows
• Linux
• macOS
• Android
• iOS
• tvOS
• Raspberry Pi 4
• Nintendo Switch (libnx)

Libretro core v1.3

How to use the core

Libretro cores are shared libraries. To use this core you will need to have installed some libretro front-end, such as RetroArch, and import the core file into it.

Requirements

The Vircon32 core requires either OpenGL Core or OpenGL ES 2/3.

What's new in version 1.3?

This version adds support for savestates. With it, rewinding is now possible too. Netplay might work as well, but this has not been tested. Also, the embedded Vircon32 Standard Bios has been updated to version 1.2 to fix a couple of minor errors.

Known issues

Game compatibility should be 100%, but there are a couple of things to note about playing Vircon32 using the libretro core:

• Savestates do not save the screen contents, which are persistent on Vircon32. This is done on purpose to reduce size and complexity on savestate handling. Otherwise it might get too taxing to enable rewinding. Most games will update the screen every frame, but once in a while you can have screen glitches for a moment if you save a state during menus or screen transitions.
• There is not an easy way to change the memory card on the fly. This is normally not needed but there could be (very few) games that rely on this, like the Chip-8 emulator. These might be better played on a standalone emulator.
• On the libretro core, currently all 4 gamepads are considered connected at all times. This is not an issue, but if you run the gamepads test it may behave differently to other Vircon32 emulators.

Supported systems

The core currently works under the following systems (possibly more):

• Windows
• Linux
• macOS
• Android
• iOS
• tvOS
• Raspberry Pi 4
• Nintendo Switch (libnx)

Libretro core v1.2

How to use the core

Libretro cores are shared libraries. To use this core you will need to have installed some libretro front-end, such as RetroArch, and import the core file into it.

Requirements

The Vircon32 core requires either OpenGL Core or OpenGL ES 2/3.

What's new in version 1.2?

This version fixes a bug in OpenGL context handling that, in some libretro contexts, could cause crashes or even prevent the core from runnning. Other than that it has identical features to version 1.1.

Note that this fix was in the code some time ago, and the core integrated in Retroarch repositories already includes it. But no precompiled release was made to include it yet.

Supported systems

The core currently works under the following systems:

• Windows
• Linux
• macOS
• Android
• iOS
• tvOS
• Raspberry Pi 4
• Nintendo Switch (libnx)

Libretro core v1.1

How to use the core

Libretro cores are shared libraries. To use this core you will need to have installed some libretro front-end, such as RetroArch, and import the core file into it.

Requirements

The Vircon32 core requires either OpenGL Core or OpenGL ES 2/3.

What's new in version 1.1?

• From version 1.1 the standard Vircon32 BIOS is integrated into the core itself, so it is not needed to install it externally. However you can use a different BIOS file by placing it in the system directory of your front-end, with the name Vircon32Bios.v32.
• Graphics for this version have been optimized, and performance should be quite better.
• A core option was added to enable automatic frame skip. This will avoid audio crackling on systems where Vircon32 cannot reach 60fps. However keep in mind that turning on this option may create other problems like video stutter and missed inputs.

Supported systems

The core currently works under the following systems:

• Windows
• Linux
• macOS
• Android
• iOS
• tvOS
• Raspberry Pi 4
• Nintendo Switch (libnx)

Libretro core v1.0

How to use the core

Libretro cores are shared libraries. To use this core you will need to have installed some libretro front-end, such as RetroArch, and import the core file into it. This core also requires the Vircon32 BIOS file, that you can download here. Place it in the system directory of your front-end.

Requirements

The Vircon32 core requires either OpenGL Core or OpenGL ES 2/3.

Supported systems

The core currently works under Windows, Linux, Android and the Raspberry Pi 4. Other people can also tested it under Apple systems: MacOS, iOS and tvOS.