| Both sides previous revision Previous revision Next revision | Previous revision |
| systems:jaguar [2022/03/01 01:07] – improve summary atari | systems:jaguar [2026/03/27 11:27] (current) – ↷ Links adapted because of a move operation 180.144.104.180 |
|---|
| It featured 64-bit graphical accelerators, making it technically the only console of its competitors (the [[systems:saturn|Saturn]] and the [[systems:psx|PlayStation]]) as it was proudly advertised as. However, this was //just// the graphical accelerators, the GPU itself was 32-bit and the CPU was only 16-bit, leading to some [[wp>Atari_Jaguar#Bit_count_controversy|controversy]]. The console itself was capable of 3D polygonal graphics, but the quality of the titles that utilized them were more comparable to the SNES's SuperFX chip than the Saturn's and PlayStation's graphical fidelity. | It featured 64-bit graphical accelerators, making it technically the only console of its competitors (the [[systems:saturn|Saturn]] and the [[systems:psx|PlayStation]]) as it was proudly advertised as. However, this was //just// the graphical accelerators, the GPU itself was 32-bit and the CPU was only 16-bit, leading to some [[wp>Atari_Jaguar#Bit_count_controversy|controversy]]. The console itself was capable of 3D polygonal graphics, but the quality of the titles that utilized them were more comparable to the SNES's SuperFX chip than the Saturn's and PlayStation's graphical fidelity. |
| |
| The Jaguar was a commercial failure, selling less 150,000 units than and having only 50 cartridge games in its library. This would mark Atari's last major home console release, relegating themselves to producing [[systems:plugnplay|plug and play TV games]]. | The Jaguar was a commercial failure, selling less 150,000 units than and having only 50 cartridge games in its library. This would mark Atari's last major home console release, relegating themselves to producing [[systems:tvgames|plug and play TV games]]. |
| |
| On May 14, 1999, Hasbro Interactive announced that it had released all patents to the Jaguar, declaring it an open platform, opening it up for homebrew developers to make their own software for it. | On May 14, 1999, Hasbro Interactive announced that it had released all patents to the Jaguar, declaring it an open platform, opening it up for homebrew developers to make their own software for it. |
| Emulation for the Jaguar is not that mature yet, there will be many instances of incompatible games. | Emulation for the Jaguar is not that mature yet, there will be many instances of incompatible games. |
| |
| The Atari Jaguar also received a CD add-on later in its life, with a total of twelve official games released using it. Currently, no emulators on Batocera support running Jaguar CD-ROMs. | The Atari Jaguar also received a CD add-on later in its life, with a total of twelve official games released using it. |
| |
| This system scrapes metadata for the "jaguar" group and loads the ''atarijaguar'' set from the currently selected theme, if available. | This system scrapes metadata for the "jaguar" group and loads the ''atarijaguar'' set from the currently selected theme, if available. |
| ==== Quick reference ==== | ==== Quick reference ==== |
| |
| * **Emulator:** [[#retroarch|RetroArch]] | * **Accepted ROM formats:** ''.cue'', ''.j64'', ''.jag'', ''.cof'', ''.abs'', ''.cdi'', ''.rom'', ''.zip'', ''.7z'' |
| * **Core:** [[#libretro:_virtualjaguar|libretro: virtualjaguar]] | |
| * **Folder:** ''/userdata/roms/jaguar'' | * **Folder:** ''/userdata/roms/jaguar'' |
| * **Accepted ROM formats:** ''.j64'', ''.jag'', ''.zip'', ''.7z'' | |
| | ^ Emulators ^ |
| | | [[#libretro:_virtualjaguar|libretro: virtualjaguar]] | |
| | | [[#bigpemu|BigPEmu]] | |
| |
| ===== BIOS ===== | ===== BIOS ===== |
| |
| ===== Saves ===== | ===== Saves ===== |
| | |
| | Saves can be found in ''/userdata/saves/jaguar''. |
| |
| When performing an in-game save, the Virtual Jaguar core creates both a Cartridge EEPROM save file and a CD-ROM EEPROM save file, regardless of the game type. | When performing an in-game save, the Virtual Jaguar core creates both a Cartridge EEPROM save file and a CD-ROM EEPROM save file, regardless of the game type. |
| ==== RetroArch ==== | ==== RetroArch ==== |
| |
| [[https://docs.libretro.com/|RetroArch]] (formerly SSNES), is a ubiquitous frontend that can run multiple "cores", which are essentially the emulators themselves. The most common cores use the [[https://www.libretro.com/|libretro]] API, so that's why cores run in RetroArch in Batocera are referred to as "libretro: (core name)". RetroArch aims to unify the feature set of all libretro cores and offer a universal, familiar interface independent of platform. | RetroArch has [[emulators:retroarch|its own page]]. |
| | |
| === RetroArch configuration === | |
| | |
| RetroArch offers a **Quick Menu** accessed by pressing ''[HOTKEY]'' + {{:wiki:south.png?nolink&20|South button (B SNES)}} which can be used to alter various things like [[:advanced_retroarch_settings|RetroArch and core options]], and [[:remapping_controls_per_emulator|controller mapping]]. Most RetroArch related settings can be altered from Batocera's EmulationStation. | |
| | |
| Standardized features available to all libretro cores: ''jaguar.videomode'', ''jaguar.ratio'', ''jaguar.smooth'', ''jaguar.shaders'', ''jaguar.pixel_perfect'', ''jaguar.decoration'', ''jaguar.game_translation'' | |
| | |
| ^ ES setting name ''batocera.conf_key'' ^ Description => ES option ''key_value'' ^ | |
| ^ Settings that apply to all cores of this emulator || | |
| | **GRAPHICS API ''jaguar.gfxbackend''** | Choose which graphics API library to use. Vulkan is better, when supported.\\ => OpenGL ''opengl'', Vulkan ''vulkan''. | | |
| | **AUDIO LATENCY ''jaguar.audio_latency''** | In milliseconds. Can reduce crackling/cutting out.\\ => 256 ''256'', 192 ''192'', 128 ''128'', 64 ''64'', 32 ''32'', 16 ''16'', 8 ''8''. | | |
| | **THREADED VIDEO ''jaguar.video_threaded''** | Improves performance at the cost of latency and more video stuttering.\\ => On ''true'', Off ''false''. | | |
| |
| === libretro: virtualjaguar === | === libretro: virtualjaguar === |
| |
| [[https://icculus.org/virtualjaguar/|Virtual Jaguar]] is an Atari Jaguar emulator. You can check its compatibility near the bottom of their webpage. This is the [[https://github.com/libretro/virtualjaguar-libretro|libretro port]] of it. | [[https://icculus.org/virtualjaguar/|Virtual Jaguar]] is an Atari Jaguar emulator, its compatibility can be checked near the bottom of [[https://icculus.org/virtualjaguar/|their webpage]] (most notably, it does not support Jaguar CD games in any capacity). This is the [[https://github.com/libretro/virtualjaguar-libretro|libretro port]] of it. |
| |
| == libretro: virtualjaguar configuration == | == libretro: virtualjaguar configuration == |
| | **SHOW BIOS BOOTLOGO ''global.bios_vj''** | Off is safer, On for specific games.\\ => Show ''enabled'', Skip ''disabled''. | | | **SHOW BIOS BOOTLOGO ''global.bios_vj''** | Off is safer, On for specific games.\\ => Show ''enabled'', Skip ''disabled''. | |
| | **DOOM RES HACK ''global.doom_res_hack''** | Enable for Doom to run at its correct resolution.\\ => Off ''disabled'', On ''enabled''. | | | **DOOM RES HACK ''global.doom_res_hack''** | Enable for Doom to run at its correct resolution.\\ => Off ''disabled'', On ''enabled''. | |
| | |
| | ==== BigPEmu ==== |
| | |
| | Created by [[https://www.richwhitehouse.com/jaguar/|Rich Whitehouse]], BigPEmu is the first Atari Jaguar emulator to offer compatibility with the entire library of commercially sold cartridges. It's worth noting that it was originally a closed-source emulator that was integrated into the Atari50 compilation. It has support for Jaguar CD games. |
| | |
| | This emulator is only available for x86_64. |
| | |
| | === Jaguar Game Drive === |
| | |
| | Some games are locked to be used on the Jaguar Game Drive (a hardware extension for the Jaguar console). BigPEmu has an option to emulate this hardware and allow these locked games to be played. This option can be enabled by pressing the ''[Esc]'' key, then going to **System** -> **Settings** -> **Force JGD Emulation**. |
| | |
| | === Per-Game Profiles === |
| | |
| | BigPEmu supports per-game profiles. This is accomplished by creating a BigPEmu configuration file of the same name as the software image you're loading, with a ''.bigpcfg'' extension. For example, if your software image file is named ''Cybermorph.j64'', you would create a ''Cybermorph.bigpcfg'' file alongside it. |
| | |
| | In order to create the per-game configuration file, it's recommended that you make a copy of your central BigPEmu configuration file. Under Windows (FIXME this isn't windows though, this is batocera), you can find this file at ''/userdata/saves/bigpemu-bottle/drive_c/users/root/AppData/Roaming/BigPEmu/BigPEmuConfig.bigpcfg''. It's sufficient to simply copy this file and rename it. |
| | |
| | Once you've created the game-specific configuration file, all configuration changes made through the menus while the game in question is loaded will apply and be saved only to this configuration file. If the software is unloaded, the central configuration will be used. |
| |
| ===== Controls ===== | ===== Controls ===== |