nnarain/dotrix

Gameboy Emulator UI using the Gameboy Core library

Hello! I'm Natesh.

I'm a software developer, focusing on systems programming, firmware and digital electronics.

Latest Blog Posts

• Makes of the Month (2024-05-26)
• Icarus April 2024 Update (2024-04-01)
• Makes of the Month (2024-02-03)
• 2023 Retrospective (2023-12-31)
• The Burnout Post (2023-11-28)

---

dotrix's Issues

Appveyor build matrix for different platforms and architectures

Folder Structure

Organize headers into folders.

Deployment

Add Qt CMake build

Build in Release mode

Build in release mode, currently being built in debug mode and the install Qt .dll files are release binaries

Move from Qt to SFML+ImGUI?

Would require entire rewrite...

The build would be smaller, and more flexible in terms of what is in a single window display.

Local multiplayer -> Boost.Asio
Scripting -> Boost.Python

Need a replacement for HTTP request (for dotrix-server though that isn't implemented at the moment anyways)

ImGUI emphasizes its use for debugging tools and visualization. Which is a good choice for:

• Color configuration
• audio visualization
• viewing memory and register states.
• Key binding confinguration

Embedded Python

Provide python scripts with the gameboy core for automation

Dialog that lists cartridge info (header)

Icon

Basic user input

Qt wrapper for GameboyCore

binds GameboyCore callback functions internally and emits signals for Qt objects

QGameboyCore

Create a source folder for .rst files in docs/

Custom key bindings

Redefine what this project actually is

General use of the emulators I write (like actually playing games with them) can be done through RetroArch using gameboycore-retro.

However, for running programs that can play the games requires something extra. This project can be used to run python scripts, step through the program or view memory.

Maybe it could be generic like libretro or just be for GameboyCore.

Catch and notify of run time exceptions in the core

Not captured because the core is updated in another thread

Audio

Requires complete APU module in the GameboyCore

Save entire CPU and Memory State

Save all RAM and Register values to a file. Then recover.

Requires changes to the GameboyCore.

Check for new version

Debian Package

Load game saves (Battery RAM)

Menu option to open online manual

Version info

Android build

Read the docs for an online manual

Running installed exe opens a console window

Travis CI

State machine for network server/client switching

Could probably create a state machine class, maybe with Qt signals/slots

Per game key bindings

Debugger

Charts - For Audio?

About dialog

Display version, license, and description.

Add GameboyCore library

Draw dotrix logo (tbd) when core is not running

Default path for configuration files

Local Networking

TCP or UDP to Link port

Perferences (Config File)

Emulation running too fast

I'm trying to use the gameboycore library and using this project as a reference. I cloned the source code, removed the networking part and compiled myself with VS2019+Qt 5.15.2.

However, when it comes to testing/playing, the game is just running too fast. For example, in game Mario the time counts down about 20 in game seconds per real time seconds.

I believe this part of code doesn't do what it supposed to do.

dotrix/include/emu/core_updater.h

Lines 21 to 27 in ea06cad

	void run()
	{
	while (running_)
	{
	core_.update(512);
	}
	}

The screen renders every 16ms, but the cpu cycles never stops. I changed the logic in this part as below, and it runs nearly normal:

void run() 
 { 
 	while (running_) 
 	{ 
 		core_.emulateFrame();
                msleep(16);
 	} 
 } 

Calling thread to sleep still doesn't seems right, I guess a proper signal/slot should be the final solution to this problem.

Open ROM file and run