Emulation General Wiki

Emulation issues and roadblocks: Difference between revisions

← Older edit
undoRtim (talk | contribs)
8,382 edits
VisualWikitext
Ahayri (talk | contribs)
24,008 edits
No edit summary
Rtim (talk | contribs)
8,382 edits
mNo edit summary
 
(34 intermediate revisions by one other user not shown)
Line 8: Line 8:
:There are several systems that require more attention from the emulation community. While multiple emulators may exist, none of them appear particularly promising. These systems for which a PC cannot yet fully replicate the experience, because emulators are incomplete, or lack support for key hardware features, peripherals, or specialized components. As a result, certain software or functions remain usable only on original hardware.
:There are several systems that require more attention from the emulation community. While multiple emulators may exist, none of them appear particularly promising. These systems for which a PC cannot yet fully replicate the experience, because emulators are incomplete, or lack support for key hardware features, peripherals, or specialized components. As a result, certain software or functions remain usable only on original hardware.
*[[Gizmondo emulators|Gizmondo]]
*[[Gizmondo emulators|Gizmondo]]
*[[IPod Classic emulators|Apple iPod]]
*[[IPod emulators|Apple iPod]]
*[[IOS_emulators|Apple iOS]]
*[[IOS_emulators|Apple iOS]]
*[[PlayStation Mobile]]
*[[PlayStation Mobile]]
Line 32: Line 32:
*[[Official emulators]]
*[[Official emulators]]


=Home Computers=
==Windows XP==
==Windows XP==
{{Main|Windows NT 5.x emulators}}
{{Main|Windows NT 5.x emulators}}
For PC games up to roughly 1997, emulators such as [[86Box]] and [[DOSBox#Forks]] accurately recreate the hardware environment of the era. Beginning around 1998, however, PC games increasingly depended on hardware-accelerated 3D graphics, SSE instructions, and substantially more CPU performance. A fully [[Emulation accuracy|cycle-accurate]] implementation of an entire [[Windows NT 5.x emulators|Windows XP-era]] PC including the CPU, chipset and graphics hardware is impractical due to the computational cost of faithfully reproducing that generation of x86 systems.
For PC games up to roughly 1997, emulators such as [[86Box]] and [[DOSBox#Forks]] accurately recreate the hardware environment of the era. Beginning around 1998, however, PC games increasingly depended on hardware-accelerated 3D graphics, SSE instructions, and substantially more CPU performance. A fully [[Emulation accuracy|cycle-accurate]] implementation of an entire 2001-2006 [[Windows NT 5.x emulators|Windows XP-era]] PC including the CPU, chipset and graphics hardware is impractical due to the computational cost of faithfully reproducing that generation of x86 systems.


Instead, modern PC emulation generally relies on either [[wikipedia:Hardware_virtualization#Hardware-assisted_virtualization|hardware-assisted virtualization]] (such as [[Hypervisors#Type 1 hypervisors|KVM]] or [[Hypervisors#Hyper-V Subsets|WHPX]]) or [[High and low-level emulation#Modern Dependencies.2C Advancements and Optimization Strategies|dynamic binary translation]] (DBT). Hardware-assisted virtualization executes guest code directly on the host processor and therefore [[Hypervisors#Performance impact|provides substantially higher CPU performance]], but requires compatible host hardware and introduces a dependency on the host operating system's virtualization facilities. Generic dynamic binary translation engines such as QEMU's TCG/MTTCG provide a flexible software-only foundation but generally do not deliver sufficient performance in their standard form. Nevertheless, projects such as [[Xemu]], [[RPCS3]] and [[Cemu]] demonstrate that carefully optimized, workload-specific dynamic recompilers can achieve practical performance even for systems that very complex.
Instead, modern PC emulation generally relies on either [[wikipedia:Hardware_virtualization#Hardware-assisted_virtualization|hardware-assisted virtualization]] (such as [[Hypervisors#Type 1 hypervisors|KVM]] or [[Hypervisors#Hyper-V Subsets|WHPX]]) or [[High and low-level emulation#Modern Dependencies.2C Advancements and Optimization Strategies|dynamic binary translation]] (DBT). Hardware-assisted virtualization executes guest code directly on the host processor and therefore [[Hypervisors#Performance impact|provides substantially higher CPU performance]], but requires compatible host hardware and introduces a dependency on the host operating system's virtualization facilities. Generic dynamic binary translation engines such as QEMU's TCG/MTTCG provide a flexible software-only foundation but generally do not deliver sufficient performance in their standard form. Nevertheless, projects such as [[Xemu]], [[RPCS3]] and [[Cemu]] demonstrate that carefully optimized, workload-specific dynamic recompilers can achieve practical performance even for systems that very complex.


Unlike console emulators, Windows XP emulation targets the same general x86 instruction set used by modern desktop processors. Although privilege levels, segmentation, paging, exceptions, self-modifying code and other architectural differences still require translation, guest instructions can often be mapped to relatively efficient native host code. Rather than attempting cycle-accurate execution, a specialized recompiler could instead optimize frequently executed code paths through techniques such as larger translation blocks, aggressive block linking, profile-guided optimization and guest operating system-aware fast paths. The performance target is also substantially lower than native execution on modern processors. Many games released in that era were designed to run on hardware comparable to a Pentium 4 or Athlon XP paired with a DirectX 8 or DirectX 9 graphics accelerator. Consequently, a software emulator does not necessarily need to approach native CPU performance; it instead needs to provide performance broadly comparable to contemporary hardware while minimizing translation overhead. The largest remaining technical challenge for the 1998–2005 era is efficient 3D graphics acceleration. While projects such as [[Windows NT 5.x emulators#Other solutions|QEMU 3dfx]] demonstrate that application-level API pass-through is feasible, these solutions typically rely on guest-side wrapper libraries, manual configuration, and external translation layers. Other projects including [https://github.com/JHRobotics/softgpu SoftGPU], [https://github.com/iXit/wine-nine-standalone Gallium Nine], and experimental [https://github.com/virtio-win/kvm-guest-drivers-windows/pull/943 virtio-gpu] implementations explore different approaches to accelerating legacy graphics APIs. A fully integrated software emulator combining a high-performance dynamic recompiler with a paravirtualized graphics architecture remains an area of active research rather than an established solution.
But unlike a typical console emulator, a Windows XP emulator could target the same general x86 instruction set used by modern desktop processors. Although privilege levels, segmentation, paging, exceptions, self-modifying code and other architectural differences still require translation, guest instructions can often be mapped to relatively efficient native host code. Rather than attempting cycle-accurate execution, a specialized recompiler could instead optimize frequently executed code paths through techniques such as larger translation blocks, aggressive block linking, profile-guided optimization and guest operating system-aware fast paths. The performance target is substantially lower than native execution on modern processors; many games and applications released during this period were designed to run on hardware comparable to a 32-bit Intel Pentium 4 "Prescott" CPU with SSE3 support.<ref>While the Prescott microarchitecture was designed with Intel 64 capabilities, the initial desktop models shipped with 64-bit support disabled. Consequently, these early variants do not qualify as x86-64-v1 processors and function strictly as 32-bit x86 processors with SSE3 support. Intel later enabled 64-bit support in subsequent Prescott revisions, such as the 5xxF and 6xx series.</ref> Consequently, the software emulator only needs to match this legacy performance while minimizing translation overhead. The most significant remaining technical hurdle for the 2001–2006 era is efficient 3D graphics acceleration; a DirectX 9.0c Shader Model 3.0 GPU would be the perfect target to run the vast majority of software from this generation. While projects such as [[Windows NT 5.x emulators#Other solutions|QEMU 3dfx]] demonstrate that application-level API pass-through is feasible, these solutions typically rely on guest-side wrapper libraries, manual configuration, and external translation layers. Other projects including [https://github.com/JHRobotics/softgpu SoftGPU], [https://github.com/iXit/wine-nine-standalone Gallium Nine], and experimental [https://github.com/virtio-win/kvm-guest-drivers-windows/pull/943 virtio-gpu] implementations explore different approaches to accelerating legacy graphics APIs. A fully integrated software emulator combining a high-performance dynamic recompiler with a paravirtualized graphics architecture remains an area of active research rather than an established solution.


=== Approach 1: User-Space API Pass-Through ===
=== Approach 1: User-Space API Pass-Through ===
Line 48: Line 49:
* '''Drawbacks:''' Because interception occurs above the graphics driver layer, compatibility depends on successfully replacing or proxying application-visible libraries. The resulting configuration process is often complex, requiring manual installation of wrapper DLLs, per-game configuration, and system modifications. Compatibility can vary between titles, particularly for applications that rely on undocumented behavior or interact directly with graphics resources outside the expected API pathways. In addition, implementations frequently rely on host virtualization technologies (such as WHPX or KVM), introducing another software layer whose behavior and timing characteristics are outside the emulator's direct control.
* '''Drawbacks:''' Because interception occurs above the graphics driver layer, compatibility depends on successfully replacing or proxying application-visible libraries. The resulting configuration process is often complex, requiring manual installation of wrapper DLLs, per-game configuration, and system modifications. Compatibility can vary between titles, particularly for applications that rely on undocumented behavior or interact directly with graphics resources outside the expected API pathways. In addition, implementations frequently rely on host virtualization technologies (such as WHPX or KVM), introducing another software layer whose behavior and timing characteristics are outside the emulator's direct control.


<div style="font-size: 80%; line-height: 1.2;">
<pre>
<pre>
+───────────────────────────────────────────────────────────────────────────+
+───────────────────────────────────────────────────────────────────────────+
Line 83: Line 85:
+───────────────────────────────────────────────────────────────────────────+
+───────────────────────────────────────────────────────────────────────────+
</pre>
</pre>
</div>


=== Approach 2: Paravirtualized GPU Device ===
=== Approach 2: Paravirtualized GPU Device ===
Line 89: Line 92:
* '''Guest-side virtual graphics driver:''' The guest installs an OS-compliant virtual graphics driver consisting of a User-Mode Driver (UMD) and a Kernel-Mode Miniport Driver (KMD). Applications continue using the original Microsoft Direct3D runtime (such as <code>d3d8.dll</code> or <code>d3d9.dll</code>) without modification. Rendering requests naturally flow through the registered virtual graphics device instead of requiring per-game DLL replacement or API hooks.
* '''Guest-side virtual graphics driver:''' The guest installs an OS-compliant virtual graphics driver consisting of a User-Mode Driver (UMD) and a Kernel-Mode Miniport Driver (KMD). Applications continue using the original Microsoft Direct3D runtime (such as <code>d3d8.dll</code> or <code>d3d9.dll</code>) without modification. Rendering requests naturally flow through the registered virtual graphics device instead of requiring per-game DLL replacement or API hooks.
* '''Shared-memory command transport:''' Rather than performing expensive hypercalls for every rendering operation, the emulator exposes a shared-memory command queue (such as a ring buffer). The guest graphics driver serializes rendering commands, resource updates, and synchronization events into this queue, allowing the host to consume them asynchronously with minimal virtualization overhead.
* '''Shared-memory command transport:''' Rather than performing expensive hypercalls for every rendering operation, the emulator exposes a shared-memory command queue (such as a ring buffer). The guest graphics driver serializes rendering commands, resource updates, and synchronization events into this queue, allowing the host to consume them asynchronously with minimal virtualization overhead.
* '''Host-side virtual GPU renderer:''' The emulator reconstructs the guest rendering state from the command stream and executes it using a dedicated virtual GPU renderer implemented on top of a modern graphics API such as Vulkan or OpenGL. Unlike application-level wrapper projects, the renderer operates entirely within the emulator rather than inside the guest operating system.
* '''Host-side virtual GPU renderer:''' The emulator reconstructs the guest rendering state from the command stream and executes it using a dedicated virtual GPU renderer implemented on top of a modern, low-level explicit graphics API backend such as Vulkan. Unlike application-level wrapper projects, the renderer operates entirely within the emulator rather than inside the guest operating system.


<div style="font-size: 80%; line-height: 1.2;">
<pre>
<pre>
+───────────────────────────────────────────────────────────────────────────+
+───────────────────────────────────────────────────────────────────────────+
Line 108: Line 112:
                                   ▼
                                   ▼
                   =================================
                   =================================
                  SHARED MEMORY COMMAND QUEUE
                    SHARED MEMORY COMMAND QUEUE
                   =================================
                   =================================
                                   │
                                   │
                                   ▼
                                   ▼
+─────────────────────────────────┴─────────────────────────────────────────+
+───────────────────────────────────────────────────────────────────────────+
|                          HOST OS / EMULATOR                              |
|                          HOST OS / EMULATOR                              |
|                                                                          |
|                                                                          |
Line 120: Line 124:
|  [ Virtual GPU Command Decoder ]                                        |
|  [ Virtual GPU Command Decoder ]                                        |
|            │                                                              |
|            │                                                              |
|            ▼                                                             |
|            ▼ (Unified Internal Rendering Representation)                  |
|  [ Virtual GPU Renderer ]                                                |
|  [ Virtual GPU Renderer ]                                                |
|            │                                                              |
|            │                                                              |
|            ▼                                                             |
|            ▼ (Shader Translation / Backend Interface)                    |
|  [ Vulkan / OpenGL Backend ]                                             |
|  [ Vulkan / Direct3D 12 / Metal Backend ]                               |
|            │                                                              |
|            │                                                              |
|            ▼                                                              |
|            ▼                                                              |
Line 130: Line 134:
+───────────────────────────────────────────────────────────────────────────+
+───────────────────────────────────────────────────────────────────────────+
</pre>
</pre>
</div>


Unlike application-level API forwarding, the virtual graphics driver does not simply relay Direct3D API calls to the host. Instead, it implements a complete virtual graphics device whose command stream serves as the interface between the guest operating system and the emulator. The guest driver translates Direct3D operations into commands understood by the virtual GPU, while the emulator reconstructs those commands and executes them using a modern graphics backend such as Vulkan or OpenGL. This avoids the considerably more difficult task of emulating the register-level behavior and rendering pipeline of a physical GPU while still allowing Windows and applications to interact with what appears to be standard graphics hardware.
Unlike application-level API forwarding, the virtual graphics driver does not simply relay Direct3D API calls to the host. Instead, it implements a complete virtual graphics device whose command stream serves as the interface between the guest operating system and the emulator. The guest driver translates Direct3D operations into commands understood by the virtual GPU, while the emulator reconstructs those commands and executes them using a modern graphics backend. This avoids the considerably more difficult task of emulating the register-level behavior and rendering pipeline of a physical GPU while still allowing Windows and applications to interact with what appears to be standard graphics hardware.


Since rendering is performed entirely on the host GPU, completed frames generally do not need to be copied back into the guest frame buffer except when required for compatibility (for example, guest software that reads the front buffer directly). Instead, the emulator presents the rendered output directly within its own display window while maintaining guest-visible synchronization state.
Since rendering is performed entirely on the host GPU, completed frames generally do not need to be copied back into the guest frame buffer unless required for compatibility (such as guest software that reads the front buffer directly). Instead, the emulator presents the rendered output directly within its own display window while maintaining the guest-visible synchronization state. Consequently, the primary challenge is implementation complexity rather than raw GPU performance. A complete virtual graphics device must faithfully virtualize Direct3D state management, resource creation, explicit synchronization primitives, presentation, capability reporting, shader handling, and device-loss behavior so that Windows and its applications observe behavior consistent with physical hardware. To manage this complexity across multiple host operating system ecosystems (beyond just Windows machines), a modern implementation could rely on a unified internal rendering architecture. Under this approach, the virtual GPU command stream is decoded into an implementation-defined rendering representation describing pipeline state, resources, synchronization primitives, and draw commands independently of any particular host graphics API. Shader programs are translated separately into an appropriate intermediate representation for the selected backend, such as SPIR-V for Vulkan, or into DXIL or Metal Shading Language (MSL) for Direct3D 12 and Metal. This separation allows the same rendering architecture to target multiple host APIs while minimizing duplicated implementation effort. Legacy fixed-function features such as table fog or texture combiners that no longer exist on modern programmable GPUs can be reconstructed through generated shader programs or specialized rendering passes rather than game-specific compatibility hacks. Likewise, legacy implicit synchronization semantics can be mapped onto modern explicit primitives such as timeline semaphores and fine-grained synchronization barriers provided by contemporary graphics APIs.
 
The primary challenge is implementation complexity rather than raw GPU performance. A complete virtual graphics device must faithfully virtualize Direct3D state management, resource creation, synchronization primitives, presentation, capability reporting, shader handling, and device-loss behavior so that Windows and applications observe behavior consistent with physical hardware. Although modern GPUs provide orders of magnitude more rendering performance than hardware from the Windows XP era, overall performance depends primarily on efficient command serialization, state tracking, and translation rather than GPU throughput alone.


Compared to application-level API forwarding, this approach offers several advantages:
Compared to application-level API forwarding, this approach offers several advantages:
* The original Microsoft graphics runtime remains untouched, avoiding per-game DLL replacement and compatibility hacks.
* '''Pristine Guest Environment:''' The original Microsoft graphics runtime remains entirely untouched, avoiding error-prone per-game DLL replacement, manual system tweaks, and compatibility hacks.
* Graphics virtualization occurs at the device-driver level, allowing all applications to use the same rendering pipeline automatically.
* '''Universal Virtual Pipeline:''' Graphics virtualization occurs at the device-driver level, allowing all legacy software, system components, and multimedia applications to use the exact same accelerated rendering infrastructure automatically.
* The virtual GPU provides a stable hardware abstraction for the guest while the emulator translates its command stream into modern graphics APIs, eliminating the need to emulate an entire legacy GPU architecture.
* '''Architectural Hardware Abstraction:''' The virtual GPU provides a stable, modern hardware abstraction for the guest while the emulator translates its command stream directly into explicit APIs, eliminating the need to emulate obsolete register-level structures or specific physical GPU architectures.
* Shared-memory command transport minimizes synchronization overhead compared to frequent VM exits or hypercalls.
* '''Low-Overhead Command Flow:''' Shared-memory command transport paired with modern explicit timeline synchronization minimizes host-guest messaging overhead and prevents VM exits or hypercall stalls.
* Rendering logic resides entirely within the emulator, resulting in a more centralized and maintainable graphics architecture.
* '''Centralized Rendering Architecture:''' All translation logic, shader recompilation pipelines, and backward-compatible fixed-function approximations reside entirely within the host-side emulator engine, creating a highly organized, modular, and maintainable subsystem.


For more information about PC emulation and their reverse engineering;
For more information about PC emulation and their reverse engineering;
Line 172: Line 175:
* [[Compatibility layers]]
* [[Compatibility layers]]
* [[Windows NT 5.x emulators#Hypervisors|Hypervisor's Virtual GPU Adapters for legacy operating systems]]
* [[Windows NT 5.x emulators#Hypervisors|Hypervisor's Virtual GPU Adapters for legacy operating systems]]
* [https://github.com/libcdio/libcdio libcdio], [https://github.com/polpo/picogus picogus], Duckstation's [https://github.com/stenzek/duckstation/blob/master/src/util/cd_image_ccd.cpp cd image ccd], [https://github.com/stenzek/duckstation/blob/master/src/util/cd_image_cue.cpp cd image cue], [[Ymir]]'s [https://github.com/StrikerX3/Ymir/tree/main/libs/ymir-core/src/ymir/hw/cdblock low-level cd block] and [https://github.com/PCSX2/pcsx2/tree/master/pcsx2/CDVD PCSX2's CDVD] - Could be beneficial for implementing reading capability for [[Ripping games#Disc-based|capable disc image formats]].
* [https://github.com/libcdio/libcdio libcdio], [https://github.com/polpo/picogus picogus], Duckstation's [https://github.com/stenzek/duckstation/blob/master/src/util/cd_image_ccd.cpp cd image ccd], [https://github.com/stenzek/duckstation/blob/master/src/util/cd_image_cue.cpp cd image cue], [[86Box]]' [https://github.com/86Box/86Box/pull/7424 aaru support], [[Ymir]]'s [https://github.com/StrikerX3/Ymir/tree/main/libs/ymir-core/src/ymir/hw/cdblock low-level cd block] and [https://github.com/PCSX2/pcsx2/tree/master/pcsx2/CDVD PCSX2's CDVD] - Could be beneficial for implementing reading capability for [[Ripping games#Disc-based|capable disc image formats]].
* [https://github.com/aaronsgiles/ymfm ymfm]
* [https://github.com/aaronsgiles/ymfm ymfm]
==Mac OS X and macOS==
===PowerPC===
Currently, no 3rd-party Macintosh emulators support hardware graphics acceleration, due to [https://www.emaculation.com/forum/viewtopic.php?t=8396 certain CPU instructions left unimplemented in their upstream PPC softcores]. This means no GLIDE, RAVE, or OpenGL. Fortunately, though as was generally the case in every platform of the period significant visual and feature differences exist between the two, the majority of Mac-exclusive software using these APIs also included software fallback renderers. It is however possible to pass through a real GPU to a PowerPC Mac being emulated by QEMU provided you have one that's compatible with OpenFirmware
===x86===
Despite an x86-based Mac is very similar to a general non-Apple PC in hardware architecture (which makes [[wikipedia:/Boot_Camp_(software)|Boot Camp]] and [[wikipedia:Hackintosh|Hackintosh]] possible), it still contains Apple proprietary hardware such as closed-source EFI BootROM, System Management Controller (SMC) and later T1/T2 security chip that either requires bypassing or emulation in order to run macOS. macOS also contains countermeasures that prevent it from being run on a non-Apple PC such as the infamous [https://www.tonymacx86.com/threads/dont-steal-mac-os-x-kext.51175/ Don't Steal Mac OS X.kext].
Another big hurdle is that macOS only contains drivers for hardware components used in actual Mac computers, which means a large portion of PC users who use different hardware combinations than actual Mac computers need to bypass, patch, or port drivers for their hardware in order to boot macOS and promote it to a usable state, and might still with crippled functionalities due to no or imperfect solutions to drive some of the hardware.
===ARM===
Hurdles in emulating ARM-based Mac are basically the same as emulating iOS devices: Apple's proprietary M1/M2 SoC which has little to no documentation, and hardened security measures inherited from iOS devices. However if Apple discontinues support for x86 in XCode, there will be no way to code modern iOS apps on other platforms or use macOS apps in general. If an ARM macOS emulator is sucessful, modern iOS emulation will be "cracked" too (apart from Corellium though).
=Home Consoles=
==Pioneer LaserActive==
The LaserActive Project wishes to document all LaserActive media. On their FAQ page, they have this to say about the possibility of creating a LaserActive emulator:
<blockquote>Emulation of the LaserActive, if attempted at all, would be an incredibly difficult task – due to the hybrid nature of the system's hardware (utilizing Sega/NEC hardware in synchronization with the unique LD player hardware) and the analog-digital composite image (analog video background, digital in-game graphics generated by said Sega/NEC hardware).<ref>https://laseractive.wordpress.com/faq/</ref></blockquote>
Emulator developer Nemesis has made an effort to dump [https://segaretro.org/LaserActive#List_of_games the games for the system] (except for porn games).<ref name="Nemesis">https://gendev.spritesmind.net/forum/viewtopic.php?t=1647&postdays=0&postorder=asc&start=0</ref> Copies of the games sent to him were supposed to be dumped and then returned.<ref name="Nemesis"/>
[[ares]] has made the most significant progress to date, featuring active support for a majority of the LaserActive's [[LaserActive#PACs|expansion PACs]].
==Philips CD-i==
The accurate emulation of the Philips CD-i (Compact Disc Interactive) system presents several significant challenges for developers. These complexities have historically limited the availability and completeness of CD-i emulators. The primary difficulties can be categorized as follows:
*Limited Demand: Compared to highly popular gaming consoles and computer systems (such as the NES, SNES, PlayStation series, or Xbox series), the demand for a fully functional CD-i emulator is relatively low. This lower interest translates into a smaller pool of developers willing to invest the substantial time and effort required for such a complex project.
*Hardware Proliferation and Variation: The CD-i platform saw a wide array of hardware releases. There are at least 32 known distinct CD-i player models, many of which underwent major internal revisions. Nearly every model featured some degree of hardware difference. These variations ranged from minor (e.g., the Philips CD-i 550 model essentially being a CD-i 450 with a pre-installed Digital Video Cartridge) to complete mainboard overhauls (e.g., the CD-i 220 model is known to have at least five revisions, each with a different mainboard). Compounding this, a diverse range of peripherals was available for CD-i players. Consequently, for an emulator to be considered "fully functional," it would ideally need to accurately replicate the behavior of every known player model and peripheral.
*Scarcity of Technical Documentation: While foundational aspects of the CD-i standard and its players are understood – such as their common reliance on the Philips SCC68070 CPU (a specialized variant of the Motorola 68000) or its derivatives (like the MC68341 Integrated CD-i Engine), and the identification of many common support chips – detailed public documentation for critical components is scarce. CD-i players utilized numerous custom integrated circuits (ICs) that were often exclusive to the platform. The lack of public datasheets and technical information for these custom chips means that emulating their precise behavior often requires extensive and time-consuming reverse-engineering. The development of CD-i Emu, currently the most feature-complete CD-i emulator, exemplifies this challenge. Its developer, known as CDiFan, has made a significant personal investment of time, financial resources, and effort over nearly two decades. This includes amassing an extensive personal collection of CD-i hardware and software, which has reportedly been instrumental in the complex reverse-engineering process necessary to understand the functions of various player components. The developer has stated that CD-i Emu represents over 120,000 lines of hand-written code. This substantial individual effort highlights the barrier posed by the lack of public documentation. A core aspect of CD-i operation that influences emulation is that the entire player hardware must be simulated, not just the software environment for a game or application. This includes the player's boot sequence into its operating system shell (the menu). Therefore, emulators require a ROM image (firmware dump) from an original CD-i player to function, even for running "base-case" titles that do not require specialized add-on hardware. Further complicating emulation efforts is the optional [[CD-i_emulators#Digital_Video_Cartridge|Digital Video Cartridge (DVC)]]. The DVC provided two main benefits: an additional 1.5 MB of RAM and, more significantly, the hardware capabilities for decoding and playing back MPEG-1 video. This video processing was handled by yet more custom chips, which also suffer from a lack of comprehensive public documentation. The DVC contains its own ROM, distinct from the player's main ROM, which is necessary for emulating titles that utilize its FMV/video playback features (including [[Home_media_players#Emulators_that_support_multimedia_capabilities_of_the_system|CD-i Digital Video and VCD support]]).
As of early 2025, DVC MPEG-1 emulation support is largely in a proof-of-concept stage and is primarily, if not exclusively, found in CD-i Emu. Other emulators generally do not yet offer DVC functionality.
A notable consideration in the CD-i emulation landscape is that the source code for CD-i Emu is not publicly available. While this is the prerogative of the author, it means that prospective contributors to CD-i emulation who wish to build upon existing advanced work may be unable to do so directly with this codebase. Instead, new efforts often necessitate starting an emulation project from the ground up. The significant undertaking of managing an open-source project, particularly for a developer working largely solo as a hobby, is a factor in such decisions. Furthermore, the pool of developers possessing both the requisite skills and the specific interest in CD-i emulation may be inherently limited, potentially mitigating the impact of a closed-source approach on overall development velocity within the niche. The developer of CD-i Emu offers a full version of the emulator for a fee, a decision understandable in light of the extensive, long-term personal investment involved in its creation.
Despite these hurdles, progress in CD-i emulation continues, albeit concentrated. [[MiSTer|CDi_MiSTer core]] and the developer of CD-i Emu is actively working on improving the emulator.


==PlayStation==
==PlayStation==
Line 223: Line 260:
* [https://psx-spx.consoledev.net/ psx-spx.consoledev.net]
* [https://psx-spx.consoledev.net/ psx-spx.consoledev.net]
* [https://problemkaputt.de/psxspx-contents.htm no$psx: Playstation Specifications]
* [https://problemkaputt.de/psxspx-contents.htm no$psx: Playstation Specifications]
==Sega Saturn==
:''This section was copied from Wikipedia in 2014. For an up-to-date explanation, see [[wikipedia:Sega Saturn#Technical specifications|Sega Saturn § Technical specifications]]''
The complexity of the system has made the creation of a proper emulator for it rather difficult.
<blockquote>One very fast central processor would be preferable. I don't think all programmers have the ability to program two CPUs — most can only get about one-and-a-half times the speed you can get from one SH-2. I think that only 1 in 100 programmers are good enough to get this kind of speed [nearly double] out of the Saturn. "Yu Suzuki reflecting upon Saturn's ''Virtua Fighter'' development<ref name="YuSuzukiNG">Next Generation (magazine) issue 2, 1995</ref>.</blockquote>
The Saturn had technically impressive hardware at the time of its release, but its complex design, with two CPUs and six other processors, made harnessing this power difficult for developers accustomed to conventional programming.  The biggest disadvantage was that both CPUs shared the same bus and were unable to access system memory at the same time. Making full use of the 4&nbsp;kB of cache memory in each CPU was critical to maintaining performance.  One example of how the Saturn was utilized was with ''Virtua Fighter''<nowiki>'</nowiki>s use of one CPU for each character<ref name=YuSuzukiNG/>. Many of the Saturn's developers, such as Lobotomy Software programmer Ezra Dreisbach, found it difficult to develop for compared to the PlayStation because of its more complex graphics hardware<ref name=DreisbachCG>{{cite web|title=Interview: Ezra Dreisbach |publisher=Curmudgeon Gamer |date=July 9, 2002|url=http://curmudgeongamer.com/article.php?story=20021008212903265 |accessdate=July 19, 2007|archiveurl = http://web.archive.org/web/20070927211250/http://curmudgeongamer.com/article.php?story=20021008212903265 <!-- Bot retrieved archive --> |archivedate = September 27, 2007}}</ref>. In order to port ''Duke Nukem 3D'' and ''PowerSlave'' to the Saturn, Lobotomy Software had to almost entirely rewrite the Build engine to take advantage of the Saturn's unconventional hardware<ref name=DreisbachCG/>.  Third-party development was initially hindered by the lack of useful software libraries and development tools, requiring developers to write in assembly language to achieve good performance. During early Saturn development, programming in assembly could offer a two to fivefold speed increase over C language<ref name=YuSuzukiNG/>. Sega responded to these criticisms by writing new graphics libraries which were claimed to help make development easier<ref name="NextGenDec95">''So many 32-Bit Systems To Choose From'' Next Generation (magazine) issue 12, 1995</ref>. These libraries were presented as a new operating system by Sega of Japan<ref name="NextGenDec95"/>.
Unlike the PlayStation and Nintendo 64 which used triangles as their basic geometric primitive, the Saturn rendered quadrilaterals with forward texture mapping. This proved to be a hindrance because most of the industry's standard design tools were based on triangles, with independent texture UV coordinates specified per vertex. One of the challenges brought forth by quadrilateral-based rendering was problems with textured surfaces containing triangles. To make a triangular-shaped object, rendering had a fourth side with a length of zero. This technique proved problematic as it caused texture distortion and required careful reworking to achieve the desired appearance—Sega provided tools for remapping textures from UV space into rectangular tiles. These complications can be seen in the Saturn version of ''Tomb Raider''<ref name=DreisbachCG/>.
For more information about Sega Saturn hardware and its reverse engineering;
* [https://www.copetti.org/writings/consoles/sega-saturn/ Rodrigo Copetti: Sega Saturn Architecture analysis]
* {{YouTubeVideo|ODJl6U1lp_Q|MVG: How the SEGA Saturn CD Security was defeated}}
* [https://www.psdevwiki.com/ps4/Sega_Saturn_Emulation PSDevWiki: PS4's Sega Saturn Emulation]
* {{YouTubeVideo|jChtlWNIAL4|LGR: Oddware - Diamond Edge 3D (nVidia NV1+Sega Saturn Ports)}}
* [https://www.yabasanshiro.com/blog/2026-05-31_new_vdp2_emulation yabasanshiro blog: new vdp2 emulation]
==Sega Dreamcast==
Developer interest in Dreamcast emulation was previously hindered by the availability of the closed-source but "good enough" Chankast, and by less interest in the console relative to other 6th generation consoles. For the emulators that are either mature or maturing, a very large percentage of games work well, but some games still have problems and glitches.
For more information about Dreamcast hardware and its reverse engineering;
* MVG: {{YouTubeVideo|rj56VU_VmWg|How the Sega Dreamcast Copy Protection Worked - And how it Failed}}, {{YouTubeVideo|rN0vEa8Y4J4|The Sega Dreamcast 20 years later 9-9-99}}, {{YouTubeVideo|NMDpPRGuaq8|The Arcade Sega Dreamcast - Revisiting the Sega Naomi Arcade Hardware}}, {{YouTubeVideo|QKHSlBi5qok|What happened to Windows CE on the SEGA Dreamcast?}}
* [https://www.copetti.org/writings/consoles/dreamcast/ Rodrigo Copetti's Dreamcast Architecture Practical Analysis], {{YouTubeVideo|lWGiHgTdLBc|The Original Xbox is the Sega Dreamcast 2?}}


==PlayStation 2==
==PlayStation 2==
Line 257: Line 319:
** '''IEEE 1394 (i.LINK):''' Early PlayStation 2 models included an IEEE 1394 interface intended primarily for multiplayer connectivity. Only a small number of commercial titles utilized the port, making it a relatively low priority for emulator development compared to other subsystems.
** '''IEEE 1394 (i.LINK):''' Early PlayStation 2 models included an IEEE 1394 interface intended primarily for multiplayer connectivity. Only a small number of commercial titles utilized the port, making it a relatively low priority for emulator development compared to other subsystems.
** '''[https://www.psdevwiki.com/ps2/DEV9C DEV9C]:''' The expansion interface controller responsible for the network adapter and hard disk drive (HDD) systems. Emulating its sub-registers is documented extensively across historical progress reports.<ref>https://pcsx2.net/blog/2025/pcsx2-2.4_2.2/#dev9-fixes</ref><ref>https://pcsx2.net/blog/2023/q1-2022-progress-report#dev9</ref>
** '''[https://www.psdevwiki.com/ps2/DEV9C DEV9C]:''' The expansion interface controller responsible for the network adapter and hard disk drive (HDD) systems. Emulating its sub-registers is documented extensively across historical progress reports.<ref>https://pcsx2.net/blog/2025/pcsx2-2.4_2.2/#dev9-fixes</ref><ref>https://pcsx2.net/blog/2023/q1-2022-progress-report#dev9</ref>
** '''CDVD:''' The PlayStation 2's CD/DVD subsystem is responsible for reading game data from optical media and exposing it to software through the I/O Processor (IOP). The CDVD hardware works alongside several system modules such as `CDVDMAN` and `CDVDFSV`, allowing games to access files, stream assets, and read disc metadata. While optical drive emulation is generally considered a more mature area of PlayStation 2 emulation than the Emotion Engine, Vector Units, or Graphics Synthesizer, accurate CDVD behavior remains important for compatibility. Some titles continuously stream data from disc during gameplay, requiring the emulator to provide data at rates and timings consistent with software expectations. Improper handling of disc reads can lead to loading issues, audio synchronization problems, or streaming-related bugs in affected titles. The PlayStation 2 supported multiple media formats, including CD-ROM, DVD-5, and DVD-9 discs. Internally, PCSX2 emulates the system software interfaces used by games to communicate with the CDVD hardware rather than attempting to model every physical characteristic of the optical drive at a mechanical level. Modern versions generally provide highly compatible CD/DVD emulation, and CDVD behavior is no longer considered one of the primary obstacles to PlayStation 2 emulation.
** '''[[Disc_Drive_emulation#DVD|CDVD]]:''' The PlayStation 2's CD/DVD subsystem is responsible for reading game data from optical media and exposing it to software through the I/O Processor (IOP). The CDVD hardware works alongside several system modules such as `CDVDMAN` and `CDVDFSV`, allowing games to access files, stream assets, and read disc metadata. While optical drive emulation is generally considered a more mature area of PlayStation 2 emulation than the Emotion Engine, Vector Units, or Graphics Synthesizer, accurate CDVD behavior remains important for compatibility. Some titles continuously stream data from disc during gameplay, requiring the emulator to provide data at rates and timings consistent with software expectations. Improper handling of disc reads can lead to loading issues, audio synchronization problems, or streaming-related bugs in affected titles. The PlayStation 2 supported multiple media formats, including CD-ROM, DVD-5, and DVD-9 discs. Internally, PCSX2 emulates the system software interfaces used by games to communicate with the CDVD hardware rather than attempting to model every physical characteristic of the optical drive at a mechanical level. Modern versions generally provide highly compatible CD/DVD emulation, and CDVD behavior is no longer considered one of the primary obstacles to PlayStation 2 emulation.


::{| class="wikitable"
::{| class="wikitable"
Line 283: Line 345:
* '''System Controllers & Security'''
* '''System Controllers & Security'''
** '''MechaCon:''' A dedicated security microcontroller responsible for console authentication, boot security, optical disc authentication, and coordinating security features such as '''MagicGate''' memory card authentication and KELF decryption. Because portions of its operation rely on proprietary cryptographic material, complete emulation presents unique legal and technical challenges.<ref>https://github.com/PCSX2/pcsx2/pull/4274#issuecomment-795316629</ref><ref>https://github.com/PCSX2/pcsx2/pull/10836#issuecomment-1954866179</ref>
** '''MechaCon:''' A dedicated security microcontroller responsible for console authentication, boot security, optical disc authentication, and coordinating security features such as '''MagicGate''' memory card authentication and KELF decryption. Because portions of its operation rely on proprietary cryptographic material, complete emulation presents unique legal and technical challenges.<ref>https://github.com/PCSX2/pcsx2/pull/4274#issuecomment-795316629</ref><ref>https://github.com/PCSX2/pcsx2/pull/10836#issuecomment-1954866179</ref>
** '''MagicGate:''' Sony's authentication and encryption technology used primarily by PlayStation 2 memory cards. Community projects have implemented varying degrees of MagicGate support, although these generally require user-supplied cryptographic material dumped from original hardware. See the [[#DVD player]] and [[#Arcade hardware variants|Konami Python 2]] sections.
** '''MagicGate:''' Sony's authentication and encryption technology used primarily by PlayStation 2 memory cards. Community projects have implemented varying degrees of MagicGate support, although these generally require user-supplied cryptographic material dumped from original hardware. See the [[Disc_Drive_emulation#DVD|PS2's DVD player]] and [[PlayStation_2_emulators#Arcade hardware variants|Konami Python 2]] sections.
** '''Syscon:''' A dedicated system controller responsible for power management, the real-time clock, thermal monitoring, and coordinating system startup and shutdown. Most commercial software interacts with Syscon only indirectly through the BIOS.
** '''Syscon:''' A dedicated system controller responsible for power management, the real-time clock, thermal monitoring, and coordinating system startup and shutdown. Most commercial software interacts with Syscon only indirectly through the BIOS.


Line 519: Line 581:


The Wii and Wii U versions of [[Virtual Console]] use extremely dark color palettes. This is apparently not an accuracy issue, but rather an anti-epilepsy measure. For the Nintendo Switch Online service, the games were directly edited to remove seizure-inducing patterns, allowing it to use a normal palette.
The Wii and Wii U versions of [[Virtual Console]] use extremely dark color palettes. This is apparently not an accuracy issue, but rather an anti-epilepsy measure. For the Nintendo Switch Online service, the games were directly edited to remove seizure-inducing patterns, allowing it to use a normal palette.
==PC Engine (TurboGrafx-16)==
===Color palette===
[[File:PCE_TG16_Composite_RGB_Palette.png|thumb|250px|An example of the color inaccuracy with the regular RGB color palette when compared to the Composite palette. Take note of the second blue gradient in the sky in both images.]]
The color palettes generated by the PC Engine for Composite and RGB actually differ due to its own color tables being non-linear. This can result in colors ending up looking wrong or blended when the system is emulated or played in RGB. A composite palette was eventually made mathematically and with some extra tweaks from the PC Engine's RGB to YUV lookup table after its HuC6270 video chip had been decapped. This palette is used by default in the PC Engine core for the [[MiSTer]]<ref>https://www.retrorgb.com/pc-engine-palette-improvements-the-amazing-people-behind-the-technology.html</ref>. It [https://github.com/Kitrinx/TG16_Palette can be downloaded] for use in other emulators and devices.


==Nintendo 64==
==Nintendo 64==
Line 577: Line 644:
* [https://www.copetti.org/writings/consoles/wii/ Rodrigo Copetti's Wii practical analysis]
* [https://www.copetti.org/writings/consoles/wii/ Rodrigo Copetti's Wii practical analysis]


==See also==
==Nintendo Switch and Switch 2==
For more information about Nintendo Switch hardware and its reverse engineering;
* MVG: {{YouTubeVideo|xQmN-cxg21M|How the Nintendo Switch Security was defeated}}
* Ryujinx: [https://web.archive.org/web/20241007214154/https://blog.ryujinx.org Blog], [https://discord.gg/ryujinx Discord]
* yuzu: [https://web.archive.org/web/20240304180918/https://yuzu-emu.org/entry/ Blog]
* Torzu: [http://vub63vv26q6v27xzv2dtcd25xumubshogm67yrpaz2rculqxs7jlfqad.onion/torzu-emu/torzu/src/branch/master/blog Blog] (NotABug [https://notabug.org/litucks/torzu/src/master/blog mirror])
* [https://switchbrew.org/wiki/Main_Page SwitchBrew]
* [https://github.com/dekuNukem/Nintendo_Switch_Reverse_Engineering dekuNukem - Nintendo Switch reverse engineering attempts]
* [https://reswitched.github.io/awesome/ ReSwitched - Awesome Switch: resources]
 
The Switch 2's custom processor, unlike the vulnerable Tegra X1 with pre-existing exploits, is likely built with stronger security measures. With Nintendo [[Legal_status_and_history_of_emulation#Nintendo| targeting emulators like Yuzu and Ryujinx]], and their forks, hacking and emulator development have been discouraged. Homebrew development faces issues in the current environment. Even if a Switch 2 emulator emerges in a few years, it will likely be tightly controlled within private communities, limiting accessibility. See [https://gbatemp.net/threads/best-practice-for-preserving-switch-2-exploitability.671473/ GBATemp thread] for rumors about Switch 2 exploitability.
 
=Handhelds=
==Game Boy (Color)==
===Oversaturation===
[[File:Gbc over saturation2.png|thumb|right|350px|Comparison of saturation levels in [[VisualBoy Advance#VBA-M|VBA-M]] and [[Gambatte]].]]
The Game Boy Color's screen is under-saturated. Game developers often work around this by using brighter colors knowing it'll be compensated for on hardware. This does not translate well in emulation, because standard LCD screens don't account for this sort of issue. Many emulators attempt to combat this issue with options that adjust accordingly; if not directly, then [[Shaders_and_Filters#Image_Adjustment|shader functionality]] may be implemented.
 
This issue also affects [[Game Boy Advance emulators#Oversaturation|Game Boy Advance emulation]].
 
====Emulator options====
'''mGBA:''' Under Tools > Settings > Shaders, you will find three customizable '''Desaturation''' parameters.
 
'''VBA-M:''' Under Options > Game Boy, you will find the '''GB color option'''. The recent nightly builds also include the '''LCD Filter''' option.
 
For more information about Game Boy hardware and its reverse engineering;<br>
* meganesu: [https://meganesu.github.io/generate-gb-opcodes/ Game Boy CPU Instructions]
* Rodrigo Copetti: [https://www.copetti.org/writings/consoles/game-boy/ Game Boy Architecture Practical Analysis]
* MVG: {{YouTubeVideo|zQE1K074v3s|How Graphics worked on the Nintendo Game Boy}}, {{YouTubeVideo|FzPTK91EJY8|Learn to code and write games on the Nintendo Game Boy}}, {{YouTubeVideo|I1cUIGHZLGA|Secrets of the Nintendo Game Boy Boot Logo}}, {{YouTubeVideo|gYQMdox5gzI|How Cartridges worked on the Nintendo Game Boy}}
* kOOPa and nocash: [https://problemkaputt.de/pandocs.htm Pan Docs]
* [https://gbdev.gg8.se/wiki/articles/Main_Page Game Boy Development Wiki]
 
==Game Boy Advance==
===Oversaturation===
[[File:1406913527173-1-.png|400px|thumb|right|'''Left:''' The default game.<br>'''Right:''' The "Game Boy Colors" mode on [[VisualBoy Advance#VBA-M|VBA-M]].]]
The screen on the original Game Boy Advance is not backlit and can be hard to see in some conditions. To compensate, game developers often used oversaturated colors by default so that the result would look normal on hardware. On standard computer screens, saturation is not an issue, so this can look jarring and undesirable for gameplay. Some games made after 2003 may have also taken the Game Boy Advance SP model (AGS-001) into account, since its screen was actually frontlit; a newer model, AGS-101, was released in 2005 that was actually backlit. For everything else though, emudevs have given some solutions:
 
====Emulator Options====
'''No$GBA:''' Under "Emulation Options," select "GBA Mode". There are four modes.
 
* '''GBA (no backlight):''' Strong desaturation
* '''GBA SP (backlight):''' Strong desaturation
* '''Nintendo DS in GBA mode:''' Some desaturation
* '''VGA Mode (poppy bright):''' No desaturation
 
'''mGBA:''' Under Tools > Settings > Shaders > Load New Shader, select "gba-color.shader"
 
'''VBA-M:''' (nightly only): Under Options > Game Boy Advance, you will find the option, '''LCD Filter'''.
 
'''higan:''' Under Settings > Video Filter, you will find the "Color Emulation" checkbox.
 
* '''Color Emulation off:''' No desaturation
* '''Color Emulation on:''' Gamma correction and adjusted color range.
'''NanoBoyAdvance''': Enabled by default. Under Config > Video > Color Correction > GBA
 
'''SkyEmu''': Color Correction is set by default to 1.00 force in this emulator, and there are 2 types of desaturation methods. The first one is named SkyEmu and is selected by default, and the other one is named Higan and, as its name suggests, is based on higan's color correction. Change the desaturation type by pressing the ≡ button, then select GBA Color Correction Type. You can also change the intensity of the desaturation: slide the slider to 0.00 to brighten the screen a tad bit.
 
====Shaders====
Cg [[Shaders and Filters|shaders]] can be used in [[OpenEmu]] or [[RetroArch]] that adjust the colors to those of a real GBA screen, as well as other screen types. These are available in GLSL<ref name="GLSL">https://github.com/libretro/glsl-shaders/tree/master/handheld/shaders/color</ref> for OpenGL, and Slang<ref name="Slang">https://github.com/libretro/slang-shaders/tree/master/handheld/shaders/color</ref> for Vulkan.
 
For GBA, there is <code>gba-color.cg</code><ref>https://github.com/libretro/common-shaders/blob/master/handheld/shaders/color/gba-color.cg</ref>, which simulates the color profile of a GBA screen under an external light source more accurately than VBA-M or No$GBA color options. If you prefer the darker color options that those emulators have, then use <code>vba-color.cg</code><ref>https://github.com/libretro/common-shaders/blob/master/handheld/shaders/color/vba-color.cg</ref> instead.
 
There is also <code>nds-color.cg</code><ref>https://github.com/libretro/common-shaders/blob/master/handheld/shaders/color/nds-color.cg</ref> and <code>psp-color.cg</code><ref>https://github.com/libretro/common-shaders/blob/master/handheld/shaders/color/psp-color.cg</ref>, which simulates the color profiles of the original Nintendo DS frontlit screen and the PSP-1000/PSP-2000 backlit screen, respectively.
 
For Game Boy Advance shader presets, see the "Shader Presets" page;
{{Main|Shader_Presets}}
 
===Horrible Sound Quality===
As a handheld rushed to the market (because of the WonderSwan Color competition), the Game Boy Advance had some cut corners. The sound hardware was affected the hardest: while it could play Game Boy Color sound in addition to samples and sequenced music like what would be heard on the SNES, the actual playback quality is awful compared to the sound samples stored internally in the ROM.
 
There were [https://www.romhacking.net/utilities/881/ tools] made to extract the internal high-quality music (as midi files plus a sound font, to be played on foobar2000); however, interest remains limited in implementing its playback in real-time on emulators. It's worth noting that NanoBoyAdvance includes an high quality audio mixer and there's a very experimental feature exists on [[mGBA]] (nightly versions) under Enhancements as "XQ GBA Audio", but it's very buggy and still limited to games using the standard sound engine, the so-called "Sappy" engine, which is still a big part of the GBA's software library.
 
===High Resolution Affine Transformation Graphical Effects===
Similarly to the scaling effects used on the Super NES known commonly as "Mode 7" graphics, the Game Boy Advance has affine transformation effects for some backgrounds and individual sprites that can be done in hardware. Due to the GBA's lower resolution, some detail may be lost.
 
The [[mGBA]] emulator added an Enhancements menu where you can change the resolution of those graphical effects, for a smoother effect. The graphical render engine will need to be OpenGL for those to take effect. It won't work on games where those effects are done in software instead of the hardware scaling features (like the 3D environment in Asterix & Obelix XXL)
 
===Save formats===
Originally, when saves were implemented, nobody settled on a format, so the Visual Boy Advance devs made their own. Because other emulators often went with raw data, having to exchange different saves caused problems. The original Visual Boy Advance tries to figure out which format a given save is but often fails at it. By explicitly telling the emulator to read it as a specific type using a file called <code>vba-over.ini</code>, VBA complies. VBA-M includes this config file by default, but older revisions like VBA 1.7.2 and VBALink don't.
 
The VBA-Next and VBA-M cores in Libretro have the file baked into the binary so that it can load raw .sav files. However, they convert the format to its own derivative at exactly 136 KB every time, with save type info contained within the file. This completely avoids the previous issues at the cost of incompatibility with standalone VBA and most others.
 
To solve this incompatibility, Libretro devs created a
[https://github.com/libretro/vba-next/blob/master/libretro/gbaconv/gbaconv.c command-line tool] to convert .srm save files made from these cores to raw .sav save data for other emulators. It takes standard input (i.e., drag and drop the .srm onto the executable) and outputs accordingly. It can also be done in reverse. A [https://thysbelon.github.io/gbaconv-web/ website version of this tool can be found here].
 
For more information about Game Boy Advance hardware and its reverse engineering;<br>
* Rodrigo Copetti: [https://www.copetti.org/writings/consoles/game-boy-advance/ Game Boy Advance Architecture Practical Analysis]
* MVG: {{YouTubeVideo|R43k-p9XdIk|The Story of Quake on the Game Boy Advance}}, {{YouTubeVideo|_Qqg4VCZ0k8|How the Game Boy Advance knew it was running a Game Boy Game}}, {{YouTubeVideo|_GVSLcqGP7g|Tomb Raider on the Nintendo Game Boy Advance is incredible}}, {{YouTubeVideo|mpNWEbZdXNw|How Graphics worked on the Nintendo Game Boy Advance}}
* martin korth: [https://problemkaputt.de/gbatek-contents.htm gbatek]
* [https://akkera102.sakura.ne.jp/gbadev/ akkera102.sakura gbadev (Japanese)]
* [https://gbadev.net/gbadoc/ gbadev - gbadoc]
* [https://en.wikibooks.org/wiki/GBA_Development/Resources WikiBooks - GBA Development Resources]
 
==PlayStation Portable==
For more information about PSP hardware and its reverse engineering;
* MVG: {{YouTubeVideo|nCzY-QhBxaE|PSP in 2023}}, {{YouTubeVideo|qIxKPu20R58|How the Sony PlayStation Portable PSP Security was defeated}}, {{YouTubeVideo|vY1j30jzRsE|A closer look at the Sony PSP DTP-T1000 Development Kit}}, {{YouTubeVideo|3HfaAlS7ons|Another look at the Sony PSP GO Handheld in 2018}}
* [https://www.copetti.org/writings/consoles/playstation-portable/ Rodrigo Copetti's PSP Architecture Practical Analysis]
* PPSSPP: [http://www.ppsspp.org/blog/ Blog], [https://discord.gg/5NJB6dD Discord], [https://www.ppsspp.org/docs/development/ Docs]
* [https://www.psdevwiki.com/psp/Main_Page PSDevWiki - PSP]
 
==Nintendo 3DS==
For more information about Nintendo 3DS hardware and its reverse engineering;
* MVG: {{YouTubeVideo|YAKujG8SXKY|The most important Nintendo 3DS Game Ever Made}}, {{YouTubeVideo|jjFGxIfDX70|Homebrew on a $100 New Nintendo 3DS LL}}, {{YouTubeVideo|-guh8hXo1bc|The Nintendo 3DS eShop Is Going Offline Forever. How to Play All Games After 2023}},
* Citra: [https://web.archive.org/web/20240304201632/https://citra-emu.org/tags/progress-report/ Blog]
* Tanuki3DS: [https://discord.gg/6ya65fvD3g Discord]
* Azahar: [https://azahar-emu.org/pages/bloglist/ Blog]
* [https://www.3dbrew.org/wiki/Main_Page 3dbrew]
* [https://wiki.gbatemp.net/wiki/3DS_Homebrew_Development GBATemp - 3DS Homebrew Development]
* [https://3ds.hacks.guide/ 3DS Hacks Guide]
* [https://fosdem.org/2024/schedule/event/fosdem-2024-1726-panda3ds-climbing-the-tree-of-3ds-emulation/ FOSDEM '24: Panda3DS - Climbing the tree of 3DS emulation]
 
=See also=
*[[Emulator scams]]
*[[Emulator scams]]
*[[Console-specific development wikis]]
*[[Console-specific development wikis]]
Retrieved from "https://emulation.gametechwiki.com/index.php/Emulation_issues_and_roadblocks"