gameroy
pandocs
| gameroy | pandocs | |
|---|---|---|
| 6 | 7 | |
| 257 | 1 | |
| - | - | |
| 8.5 | 10.0 | |
| 2 months ago | almost 4 years ago | |
| Rust | Vue | |
| Apache License 2.0 | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gameroy
-
When Zig Outshines Rust – Memory Efficient Enum Arrays
I recently found https://github.com/Rodrigodd/gameroy to be a very complete implementation
-
Gameboy Doctor: debug and fix your gameboy emulator
Hey there! I've been working on a Game Boy emulator since last year and found the GameRoy project, which translated the PPU's logic from SameBoy, the (AFAIK) most accurate GB emulator around. I basically copied the PPU logic into my emulator and replaced the "state" property (an integer) with enums for some extra clarity.
https://github.com/nicolas-siplis/feboy
https://github.com/rodrigodd/gameroy
https://github.com/LIJI32/SameBoy/
- GameRoy: a cross platform and highly accurate Game Boy emulator
- Gameroy: A gameboy emulator, dissasembler and debugger written in rust
-
GameRoy: a highly accurate Game Boy emulator and debugger written in Rust
What I did was isolate the logic of every component apart from the CPU (video, sound, timer, etc.) behind a correspondent fn update(cycle_count: u64) method (like in the sound controller or in the timer). Currently, I am calling these methods every 4 cycles, but the idea is that I would only need to call it before a read or write to a component register, or before a possible interrupt (I would need to figure out if it is possible to efficiently predict the next interrupt).
pandocs
-
GameRoy: a cross platform and highly accurate Game Boy emulator
For Gameboy emulation, one of the most valuable resources are the pandocs: https://gbdev.io/pandocs/
-
I finally wrote my first ever emulator (GameBoy)
During the development, these were the main resources I used: * Pan Docs * CPU instruction table * CPU Manual
-
Are there guides on how any of the gameboys work (ie how they charge, play games etc) and if not how can I go about learning their structure?
if you just want to learn about how the hardware works, pandocs is the definitive guide to the game boy's hardware, and gbatek helped me a ton when writing my GBA emulator (it also includes some docs on the ds/dsi fwiw)
- A Game Boy Emulator written in Rust
- ¿Les interesaría aprender a programar, emulando un Game Boy?
-
[GameBoy] Problem with CD instruction.
Pandocs: https://gbdev.io/pandocs
-
Gameboy Graphics Drawing Question
The Ultimate Game Boy Talk has some amazing information in it. In particular, the info on the pixel fifos was brand new to me. You can certainly write an emulator that runs most software without really understanding them, though.
What are some alternatives?
IronBoy - A Gameboy emulator written in Rust as both a learning exercise and a love letter to the console that got me into gaming.
dmg-acid2 - 😀 The Acid2 test, now for the original Game Boy! 😀
exotracker-cpp
Gameboy-logs - Emulation logs of common beginner ROMs for the Gameboy.
SameBoy - Game Boy and Game Boy Color emulator written in C
awesome-gbdev - A curated list of Game Boy development resources such as tools, docs, emulators, related projects and open-source ROMs. [Moved to: https://github.com/gbdev/awesome-gbdev]
sprite-render-rs - A Rust Crate for Sprite Rendering (WIP)
raw-gl-context - cross-platform OpenGL context creation
GB - Game Boy Assembly Programming
Dn-FamiTracker - modifications and improvements for 0CC-FamiTracker (based on j0CC-FamiTracker 0.6.3)
cgb-acid2 - 😀 The Acid2 test, now for Game Boy Color! 😀