Populate from feature requests on GitHub
parent
b752831619
commit
74dff51417
|
@ -1,4 +1,25 @@
|
||||||
This page documents various emulator core candidates and specific user requests for systems
|
This page documents various emulator core candidates and specific user requests for systems.
|
||||||
|
|
||||||
|
### (3DS) Citra
|
||||||
|
Tracking as [#3180](https://github.com/TASEmulators/BizHawk/issues/3180).
|
||||||
|
|
||||||
|
### (Amiga) FS-UAE or WinUAE
|
||||||
|
Tracking as [#2003](https://github.com/TASEmulators/BizHawk/issues/2003).
|
||||||
|
|
||||||
|
### (Atari 5200) Altirra or Atari800
|
||||||
|
Tracking as [#3317](https://github.com/TASEmulators/BizHawk/issues/3317).
|
||||||
|
|
||||||
|
### (Atari Jaguar) Virtual Jaguar or Phoenix
|
||||||
|
Tracking as [#1907](https://github.com/TASEmulators/BizHawk/issues/1907).
|
||||||
|
|
||||||
|
### (BBC Micro) beebjit or BeebEm or B-Em
|
||||||
|
Tracking as [#2031](https://github.com/TASEmulators/BizHawk/issues/2031).
|
||||||
|
|
||||||
|
### (Flash) Ruffle
|
||||||
|
Tracking as [#2032](https://github.com/TASEmulators/BizHawk/issues/2032).
|
||||||
|
|
||||||
|
### (Pokémon mini) GB Enhanced+ or PokeMini
|
||||||
|
Tracking as [#3162](https://github.com/TASEmulators/BizHawk/issues/3162).
|
||||||
|
|
||||||
### DosBox
|
### DosBox
|
||||||
- https://github.com/schellingb/dosbox-pure (fork)
|
- https://github.com/schellingb/dosbox-pure (fork)
|
||||||
|
@ -6,4 +27,4 @@ This page documents various emulator core candidates and specific user requests
|
||||||
- https://github.com/TASVideos/BizHawk/issues/2547
|
- https://github.com/TASVideos/BizHawk/issues/2547
|
||||||
- Core Analysis
|
- Core Analysis
|
||||||
- Early attempts (2010 or so) to add rerecording suggesting it is highly sync unstable. Situation may have changed since then. Waterbox highly recommended.
|
- Early attempts (2010 or so) to add rerecording suggesting it is highly sync unstable. Situation may have changed since then. Waterbox highly recommended.
|
||||||
- In particular, according to Ilari it had a lot of reentrancy with HLE operations, so you could get to a "frame end" while servicing an x86 BIOS call in HLE code, requiring the ability to save and load with different call sequences on the stack.
|
- In particular, according to Ilari it had a lot of reentrancy with HLE operations, so you could get to a "frame end" while servicing an x86 BIOS call in HLE code, requiring the ability to save and load with different call sequences on the stack.
|
Loading…
Reference in New Issue