Repository navigation
Releases
Bright Dawn v0.1.0-pre.157
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.150
- No change for players.
- A save made in the game is kept and loads after a restart (tried, no change needed).
- No change for players; a test for the cause of the black polygons in Saha Town.
- The game's interrupt handler runs natively: fewer instructions are interpreted. Build the game library again.
- "Sharp pixels, smooth edges" no longer blurs 3D scenes at window sizes that are not whole multiples.
- The graphics hardware draws translucent textures in the right order with other polygons.
Every commit: 92b0f87...v0.1.0-pre.157
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.
Bright Dawn v0.1.0-pre.150
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.147
- Fog is drawn with the graphics hardware too.
- The title screen's landscape is drawn again. Build the game library again.
Every commit: 7144c91...v0.1.0-pre.150
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.
Bright Dawn v0.1.0-pre.147
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.144
- The project map lists the next effects to fix at higher internal resolutions.
- Shadows under characters now show with the graphics hardware renderer at every internal resolution.
- Outlines drawn by the graphics hardware are softened as on the DS where the game asks for anti-aliasing.
- 3D models have the game's outlines with the graphics hardware too; Settings, Graphics, Outlines sets them to the original thickness, 1 pixel, or off.
- Battles and other effects that use the display capture are now drawn at the chosen internal resolution with the graphics hardware.
Every commit: 0e24db8...v0.1.0-pre.147
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.
Bright Dawn v0.1.0-pre.144
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.139
- With the graphics hardware drawing 3D, polygons are put in front of or behind each other as the game asks (by w), as with the processor.
- With the graphics hardware drawing 3D, the title screen no longer flickers between the two screens.
- The interrupt entry runs as native code, not in the interpreter.
- With the built game, logs/not-native-*.log lists where the game's code still runs in the interpreter, for the list of work to do.
Every commit: ebad645...v0.1.0-pre.144
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.
Bright Dawn v0.1.0-pre.139
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.137
- A gear on the launcher's first page opens the settings.
- 3D models move smoothly above 1x (Graphics, High-resolution coordinates).
- The game's thread switch runs as native code, not in the interpreter.
Every commit: 18895ac...v0.1.0-pre.139
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.
Bright Dawn v0.1.0-pre.137
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.133
- The launcher opens on Play and your save, on the game's own page of saves, in a 4 by 3 window; the first-time setup is simpler.
- The game's busiest loop now runs as translated code instead of in the interpreter.
Every commit: 5ca6aa4...v0.1.0-pre.137
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.
Bright Dawn v0.1.0-pre.136
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.133
- The game's busiest loop now runs as translated code instead of in the interpreter.
Every commit: 5ca6aa4...v0.1.0-pre.136
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.
Bright Dawn v0.1.0-pre.133
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.131
- Music and sound effects play, through the computer's audio device; Settings, Sound has an on/off switch and a volume.
Every commit: d6c3030...v0.1.0-pre.133
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.
Bright Dawn v0.1.0-pre.131
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.128
- 3D shown on both screens (as on the title screen) is now drawn by the graphics hardware at the higher resolution, and the automatic 3D resolution costs less.
Every commit: 891994b...v0.1.0-pre.131
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.
Bright Dawn v0.1.0-pre.128
Warning
Not playable yet. The game starts from a ROM you supply yourself and
runs through its opening to the name entry. It has not been tried beyond
that. There is no sound. The game's save is kept between runs.
Interpreted, the game runs at about a third of the DS's speed; built from
your ROM, about twice as fast as that. Expect crashes: please report them
with the log (see the end of this page).
Changes since v0.1.0-pre.125
- 3D scenes are drawn by the graphics hardware, sharper, at up to 8 times the DS's resolution.
Every commit: 711f284...v0.1.0-pre.128
Download and start
Automated pre-release, built from main after all checks passed. No ROM and
no game data are included.
bright-dawn-windows-x86_64.zip: Windows, 64-bitbright-dawn-linux-x86_64.tar.gz: Linux, 64-bit (needs X11 or Wayland)SHA256SUMS.txt: checksums of the packages
Unpack and start bright-dawn. The first time (and after each update) it
opens the setup: choose your ROM (it is remembered) and build the game from
it, its code translated to C++ and compiled on your computer, which the
program then runs natively. Then the launcher opens: play, the settings, and
the log, in the look of the game's own settings menu and font, read from your
ROM. It draws through Vulkan, or the system's own renderer where Vulkan is
not there. Nothing needs installing for that: the compiler
(and on Windows, Python, if it is not installed) is downloaded for the build,
checked, and deleted with everything else the build made; about 2 GB of free
space is needed while it runs. The built game gets as far as the
interpreted one (the name entry) and runs about twice as fast.
Keyboard: arrow keys, X = A, Z = B, S = X, A = Y, Q = L, W = R, Enter =
Start, Right Shift = Select. The left mouse button on the touch screen is the
stylus. Controllers work by button position, as on the DS. Escape (or a
controller's guide button): the menu, with the settings. F11 or Alt+Enter:
full screen. Tab: screens side by side or stacked. F12: whole-number scaling
or filling the window.
The game's save is kept in saves in the user data folder (below), with a
copy of it as it was before the last run that changed it (.sav.backup).
Reporting a problem
Report a problem, on the launcher's Log page or in the pause menu
(Escape), opens the project's form for a report on GitHub with the version,
system, renderer, game code and built game or interpreter filled in, and the
folder of the logs. Every run writes a log, in logs in the user data folder
(%LOCALAPPDATA%\BrightDawn on Windows, ~/.local/share/bright-dawn on
Linux): please attach it. Never attach the ROM, saves or other game files.