NocturneDecomp 0.1.10

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Which build?

Every platform comes in two flavours:

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

Windows

Archive	System	Flavour
nocturne-0.1.10-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.10-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne.exe replaces the game's own.
3. Set up the cutscenes (below).

Reporting a crash: the game shows a message box naming the crash report it saved,
nocturne_crash.txt: in %LOCALAPPDATA%\NocturneDecomp\, or beside the nocturne_*.log files
when the game was started with --data-dir or --user-dir. Attach it, along with those logs.

macOS

Archive	System	Flavour
nocturne-0.1.10-exe-macos-arm64.tar.gz	Apple silicon	Enhanced
nocturne-0.1.10-exe-macos-vanilla-arm64.tar.gz	Apple silicon	Vanilla
nocturne-0.1.10-exe-macos-x86_64.tar.gz	Intel	Enhanced
nocturne-0.1.10-exe-macos-vanilla-x86_64.tar.gz	Intel	Vanilla

1. Unpack the archive and move Nocturne.app (or Nocturne Vanilla.app) wherever you like,
   such as /Applications.
2. The app is not signed with a developer identity, so Gatekeeper refuses it at first. Clear the
   download flag once: xattr -dr com.apple.quarantine /Applications/Nocturne.app.
3. Start the app once. It creates ~/Library/Application Support/NocturneDecomp/, opens it in
   Finder, and asks for the game files.
4. Copy everything from a Nocturne install folder into it: a Windows install, or one made under
   Wine or CrossOver. Both apps share this folder, saves included.
5. Set up the cutscenes (below), then start the app again.

Reporting a crash: macOS saves its own crash report to
~/Library/Logs/DiagnosticReports/ as Nocturne-<date>.ips (Nocturne Vanilla-<date>.ips for the
vanilla app). Attach the newest one, along with the nocturne_*.log files from
~/Library/Application Support/NocturneDecomp/.

The macOS builds are compiled in CI but have had little testing on real Macs yet.

Linux

Archive	System	Flavour
nocturne-0.1.10-exe-linux-x86_64.tar.gz	x86-64	Enhanced
nocturne-0.1.10-exe-linux-vanilla-x86_64.tar.gz	x86-64	Vanilla
nocturne-0.1.10-exe-linux-aarch64.tar.gz	64-bit Arm	Enhanced
nocturne-0.1.10-exe-linux-vanilla-aarch64.tar.gz	64-bit Arm	Vanilla

1. Copy a Nocturne install folder onto the machine: a Windows install, or one made under Wine.
2. Unpack the archive into that folder, so nocturne sits beside the game's own files.
3. Set up the cutscenes (below).

Reporting a crash: start the game from a terminal (./nocturne) and attach what it prints,
along with the nocturne_*.log files from the game folder. On distributions that use
systemd-coredump, coredumpctl info nocturne shows the backtrace of the most recent crash.

The Arm builds are compiled and unit-tested in CI but have had little testing on real machines yet.

Cutscenes

The game looks for its movies in a video folder, but they ship in AVI, which is why the retail
game never played them. Create a video folder in the game folder and copy the .AVI files into
it. The name isn't case-sensitive, even on Linux and macOS.

Keeping the engine apart from the game

On Windows and Linux, run the engine from anywhere with --data-dir <game folder>. Add
--user-dir <folder> to keep saves, settings and logs somewhere else too; the game folder is
then only read. On macOS, --data-dir replaces the Application Support folder, or put the
game folder's path in a data_dir.txt there.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version                                # Windows and Linux
/Applications/Nocturne.app/Contents/MacOS/Nocturne --version   # macOS

What's Changed

• Add modern game controls and mod support to README by @NearlyTRex in #45
• A bunch more recreation work, annotation updates for deformable models, etc by @NearlyTRex in #47
• Bump the actions group across 1 directory with 10 updates by @dependabot[bot] in #48
• Widescreen, 4K resolutions, HUD layout, anti-aliasing, camera movement, Epilogue fix by @NearlyTRex in #49
• Release v0.1.10 by @github-actions[bot] in #50

Full Changelog: v0.1.9...v0.1.10

NocturneDecomp 0.1.9

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Which build?

Every platform comes in two flavours:

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

Windows

Archive	System	Flavour
nocturne-0.1.9-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.9-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne.exe replaces the game's own.
3. Set up the cutscenes (below).

Reporting a crash: the game shows a message box naming the crash report it saved,
nocturne_crash.txt: in %LOCALAPPDATA%\NocturneDecomp\, or beside the nocturne_*.log files
when the game was started with --data-dir or --user-dir. Attach it, along with those logs.

macOS

Archive	System	Flavour
nocturne-0.1.9-exe-macos-arm64.tar.gz	Apple silicon	Enhanced
nocturne-0.1.9-exe-macos-vanilla-arm64.tar.gz	Apple silicon	Vanilla
nocturne-0.1.9-exe-macos-x86_64.tar.gz	Intel	Enhanced
nocturne-0.1.9-exe-macos-vanilla-x86_64.tar.gz	Intel	Vanilla

1. Unpack the archive and move Nocturne.app (or Nocturne Vanilla.app) wherever you like,
   such as /Applications.
2. The app is not signed with a developer identity, so Gatekeeper refuses it at first. Clear the
   download flag once: xattr -dr com.apple.quarantine /Applications/Nocturne.app.
3. Start the app once. It creates ~/Library/Application Support/NocturneDecomp/, opens it in
   Finder, and asks for the game files.
4. Copy everything from a Nocturne install folder into it: a Windows install, or one made under
   Wine or CrossOver. Both apps share this folder, saves included.
5. Set up the cutscenes (below), then start the app again.

Reporting a crash: macOS saves its own crash report to
~/Library/Logs/DiagnosticReports/ as Nocturne-<date>.ips (Nocturne Vanilla-<date>.ips for the
vanilla app). Attach the newest one, along with the nocturne_*.log files from
~/Library/Application Support/NocturneDecomp/.

The macOS builds are compiled in CI but have had little testing on real Macs yet.

Linux

Archive	System	Flavour
nocturne-0.1.9-exe-linux-x86_64.tar.gz	x86-64	Enhanced
nocturne-0.1.9-exe-linux-vanilla-x86_64.tar.gz	x86-64	Vanilla
nocturne-0.1.9-exe-linux-aarch64.tar.gz	64-bit Arm	Enhanced
nocturne-0.1.9-exe-linux-vanilla-aarch64.tar.gz	64-bit Arm	Vanilla

1. Copy a Nocturne install folder onto the machine: a Windows install, or one made under Wine.
2. Unpack the archive into that folder, so nocturne sits beside the game's own files.
3. Set up the cutscenes (below).

Reporting a crash: start the game from a terminal (./nocturne) and attach what it prints,
along with the nocturne_*.log files from the game folder. On distributions that use
systemd-coredump, coredumpctl info nocturne shows the backtrace of the most recent crash.

The Arm builds are compiled and unit-tested in CI but have had little testing on real machines yet.

Cutscenes

The game looks for its movies in a video folder, but they ship in AVI, which is why the retail
game never played them. Create a video folder in the game folder and copy the .AVI files into
it. The name isn't case-sensitive, even on Linux and macOS.

Keeping the engine apart from the game

On Windows and Linux, run the engine from anywhere with --data-dir <game folder>. Add
--user-dir <folder> to keep saves, settings and logs somewhere else too; the game folder is
then only read. On macOS, --data-dir replaces the Application Support folder, or put the
game folder's path in a data_dir.txt there.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version                                # Windows and Linux
/Applications/Nocturne.app/Contents/MacOS/Nocturne --version   # macOS

What's Changed

• Updating readme, discussion, templates by @NearlyTRex in #34
• Add support for other Nocturne-engine games by @NearlyTRex in #35
• Adding recomp.json info by @NearlyTRex in #36
• More recreation work, adding upscalers, cleaning/condensing menu shims by @NearlyTRex in #40
• Test fixes by @NearlyTRex in #41
• Release v0.1.9 by @github-actions[bot] in #42

Full Changelog: v0.1.8...v0.1.9

NocturneDecomp 0.1.8

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Which build?

Every platform comes in two flavours:

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

Windows

Archive	System	Flavour
nocturne-0.1.8-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.8-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne.exe replaces the game's own.
3. Set up the cutscenes (below).

Reporting a crash: the game shows a message box naming the crash report it saved,
nocturne_crash.txt: in %LOCALAPPDATA%\NocturneDecomp\, or beside the nocturne_*.log files
when the game was started with --data-dir or --user-dir. Attach it, along with those logs.

macOS

Archive	System	Flavour
nocturne-0.1.8-exe-macos-arm64.tar.gz	Apple silicon	Enhanced
nocturne-0.1.8-exe-macos-vanilla-arm64.tar.gz	Apple silicon	Vanilla
nocturne-0.1.8-exe-macos-x86_64.tar.gz	Intel	Enhanced
nocturne-0.1.8-exe-macos-vanilla-x86_64.tar.gz	Intel	Vanilla

1. Unpack the archive and move Nocturne.app (or Nocturne Vanilla.app) wherever you like,
   such as /Applications.
2. The app is not signed with a developer identity, so Gatekeeper refuses it at first. Clear the
   download flag once: xattr -dr com.apple.quarantine /Applications/Nocturne.app.
3. Start the app once. It creates ~/Library/Application Support/NocturneDecomp/, opens it in
   Finder, and asks for the game files.
4. Copy everything from a Nocturne install folder into it: a Windows install, or one made under
   Wine or CrossOver. Both apps share this folder, saves included.
5. Set up the cutscenes (below), then start the app again.

Reporting a crash: macOS saves its own crash report to
~/Library/Logs/DiagnosticReports/ as Nocturne-<date>.ips (Nocturne Vanilla-<date>.ips for the
vanilla app). Attach the newest one, along with the nocturne_*.log files from
~/Library/Application Support/NocturneDecomp/.

The macOS builds are compiled in CI but have had little testing on real Macs yet.

Linux

Archive	System	Flavour
nocturne-0.1.8-exe-linux-x86_64.tar.gz	x86-64	Enhanced
nocturne-0.1.8-exe-linux-vanilla-x86_64.tar.gz	x86-64	Vanilla
nocturne-0.1.8-exe-linux-aarch64.tar.gz	64-bit Arm	Enhanced
nocturne-0.1.8-exe-linux-vanilla-aarch64.tar.gz	64-bit Arm	Vanilla

1. Copy a Nocturne install folder onto the machine: a Windows install, or one made under Wine.
2. Unpack the archive into that folder, so nocturne sits beside the game's own files.
3. Set up the cutscenes (below).

Reporting a crash: start the game from a terminal (./nocturne) and attach what it prints,
along with the nocturne_*.log files from the game folder. On distributions that use
systemd-coredump, coredumpctl info nocturne shows the backtrace of the most recent crash.

The Arm builds are compiled and unit-tested in CI but have had little testing on real machines yet.

Cutscenes

The game looks for its movies in a video folder, but they ship in AVI, which is why the retail
game never played them. Create a video folder in the game folder and copy the .AVI files into
it. The name isn't case-sensitive, even on Linux and macOS.

Keeping the engine apart from the game

On Windows and Linux, run the engine from anywhere with --data-dir <game folder>. Add
--user-dir <folder> to keep saves, settings and logs somewhere else too; the game folder is
then only read. On macOS, --data-dir replaces the Application Support folder, or put the
game folder's path in a data_dir.txt there.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version                                # Windows and Linux
/Applications/Nocturne.app/Contents/MacOS/Nocturne --version   # macOS

What's Changed

• Console and packaged-app support, pad cancel on the main menu, netplay and core shim tests, cmake split by @NearlyTRex in #29
• Adding code coverage for shims, fixing bug with mouse visibility, adding dpi scale hint by @NearlyTRex in #32
• Release v0.1.8 by @github-actions[bot] in #33

Full Changelog: v0.1.7...v0.1.8

NocturneDecomp 0.1.7

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Which build?

Every platform comes in two flavours:

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

Windows

Archive	System	Flavour
nocturne-0.1.7-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.7-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne.exe replaces the game's own.
3. Set up the cutscenes (below).

Reporting a crash: the game shows a message box and saves a crash report to
%LOCALAPPDATA%\NocturneDecomp\nocturne_crash.txt. Attach it, along with the nocturne_*.log
files from the game folder.

macOS

Archive	System	Flavour
nocturne-0.1.7-exe-macos-arm64.tar.gz	Apple silicon	Enhanced
nocturne-0.1.7-exe-macos-vanilla-arm64.tar.gz	Apple silicon	Vanilla
nocturne-0.1.7-exe-macos-x86_64.tar.gz	Intel	Enhanced
nocturne-0.1.7-exe-macos-vanilla-x86_64.tar.gz	Intel	Vanilla

1. Unpack the archive and move Nocturne.app (or Nocturne Vanilla.app) wherever you like,
   such as /Applications.
2. The app is not signed with a developer identity, so Gatekeeper refuses it at first. Clear the
   download flag once: xattr -dr com.apple.quarantine /Applications/Nocturne.app.
3. Start the app once. It creates ~/Library/Application Support/NocturneDecomp/, opens it in
   Finder, and asks for the game files.
4. Copy everything from a Nocturne install folder into it: a Windows install, or one made under
   Wine or CrossOver. Both apps share this folder, saves included.
5. Set up the cutscenes (below), then start the app again.

Reporting a crash: macOS saves its own crash report to
~/Library/Logs/DiagnosticReports/ as Nocturne-<date>.ips (Nocturne Vanilla-<date>.ips for the
vanilla app). Attach the newest one, along with the nocturne_*.log files from
~/Library/Application Support/NocturneDecomp/.

The macOS builds are compiled in CI but have had little testing on real Macs yet.

Linux

Archive	System	Flavour
nocturne-0.1.7-exe-linux-x86_64.tar.gz	x86-64	Enhanced
nocturne-0.1.7-exe-linux-vanilla-x86_64.tar.gz	x86-64	Vanilla
nocturne-0.1.7-exe-linux-aarch64.tar.gz	64-bit Arm	Enhanced
nocturne-0.1.7-exe-linux-vanilla-aarch64.tar.gz	64-bit Arm	Vanilla

1. Copy a Nocturne install folder onto the machine: a Windows install, or one made under Wine.
2. Unpack the archive into that folder, so nocturne sits beside the game's own files.
3. Set up the cutscenes (below).

Reporting a crash: start the game from a terminal (./nocturne) and attach what it prints,
along with the nocturne_*.log files from the game folder. On distributions that use
systemd-coredump, coredumpctl info nocturne shows the backtrace of the most recent crash.

The Arm builds are compiled and unit-tested in CI but have had little testing on real machines yet.

Cutscenes

The game looks for its movies in a video folder, but they ship in AVI, which is why the retail
game never played them. Create a video folder in the game folder and copy the .AVI files into
it. The name isn't case-sensitive, even on Linux and macOS.

Keeping the engine apart from the game

On Windows and Linux, run the engine from anywhere with --data-dir <game folder>. Add
--user-dir <folder> to keep saves, settings and logs somewhere else too; the game folder is
then only read. On macOS, --data-dir replaces the Application Support folder.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version                                # Windows and Linux
/Applications/Nocturne.app/Contents/MacOS/Nocturne --version   # macOS

What's Changed

• More reorganization and cleanup, adding unit testing coverage by @NearlyTRex in #27
• Release v0.1.7 by @github-actions[bot] in #28

Full Changelog: v0.1.6...v0.1.7

NocturneDecomp 0.1.6

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Which build?

Every platform comes in two flavours:

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

Windows

Archive	System	Flavour
nocturne-0.1.6-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.6-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne.exe replaces the game's own.
3. Set up the cutscenes (below).

Reporting a crash: the game shows a message box and saves a crash report to
%LOCALAPPDATA%\NocturneDecomp\nocturne_crash.txt. Attach it, along with the nocturne_*.log
files from the game folder.

macOS

Archive	System	Flavour
nocturne-0.1.6-exe-macos-arm64.tar.gz	Apple silicon	Enhanced
nocturne-0.1.6-exe-macos-vanilla-arm64.tar.gz	Apple silicon	Vanilla
nocturne-0.1.6-exe-macos-x86_64.tar.gz	Intel	Enhanced
nocturne-0.1.6-exe-macos-vanilla-x86_64.tar.gz	Intel	Vanilla

1. Unpack the archive and move Nocturne.app (or Nocturne Vanilla.app) wherever you like,
   such as /Applications.
2. The app is not signed with a developer identity, so Gatekeeper refuses it at first. Clear the
   download flag once: xattr -dr com.apple.quarantine /Applications/Nocturne.app.
3. Start the app once. It creates ~/Library/Application Support/NocturneDecomp/, opens it in
   Finder, and asks for the game files.
4. Copy everything from a Nocturne install folder into it: a Windows install, or one made under
   Wine or CrossOver. Both apps share this folder, saves included.
5. Set up the cutscenes (below), then start the app again.

Reporting a crash: macOS saves its own crash report to
~/Library/Logs/DiagnosticReports/ as Nocturne-<date>.ips (Nocturne Vanilla-<date>.ips for the
vanilla app). Attach the newest one, along with the nocturne_*.log files from
~/Library/Application Support/NocturneDecomp/.

The macOS builds are compiled in CI but have had little testing on real Macs yet.

Linux

Archive	System	Flavour
nocturne-0.1.6-exe-linux-x86_64.tar.gz	x86-64	Enhanced
nocturne-0.1.6-exe-linux-vanilla-x86_64.tar.gz	x86-64	Vanilla
nocturne-0.1.6-exe-linux-aarch64.tar.gz	64-bit Arm	Enhanced
nocturne-0.1.6-exe-linux-vanilla-aarch64.tar.gz	64-bit Arm	Vanilla

1. Copy a Nocturne install folder onto the machine: a Windows install, or one made under Wine.
2. Unpack the archive into that folder, so nocturne sits beside the game's own files.
3. Set up the cutscenes (below).

Reporting a crash: start the game from a terminal (./nocturne) and attach what it prints,
along with the nocturne_*.log files from the game folder. On distributions that use
systemd-coredump, coredumpctl info nocturne shows the backtrace of the most recent crash.

The Arm builds are compiled and unit-tested in CI but have had little testing on real machines yet.

Cutscenes

The game looks for its movies in a video folder, but they ship in AVI, which is why the retail
game never played them. Create a video folder in the game folder and copy the .AVI files into
it. The name isn't case-sensitive, even on Linux and macOS.

Keeping the engine apart from the game

On Windows and Linux, run the engine from anywhere with --data-dir <game folder>. Add
--user-dir <folder> to keep saves, settings and logs somewhere else too; the game folder is
then only read. On macOS, --data-dir replaces the Application Support folder.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version                                # Windows and Linux
/Applications/Nocturne.app/Contents/MacOS/Nocturne --version   # macOS

What's Changed

• Adding macos bundle generation, adding crash handler for windows, updating docs for release/building by @NearlyTRex in #25
• Release v0.1.6 by @github-actions[bot] in #26

Full Changelog: v0.1.5...v0.1.6

NocturneDecomp 0.1.5

Downloads

Each archive is a self-contained build of the engine for one platform and flavour:

Archive	Platform	Flavour
nocturne-0.1.5-exe-linux-x86_64.tar.gz	Linux, 64-bit	Enhanced
nocturne-0.1.5-exe-linux-vanilla-x86_64.tar.gz	Linux, 64-bit	Vanilla
nocturne-0.1.5-exe-linux-aarch64.tar.gz	Linux, 64-bit Arm	Enhanced
nocturne-0.1.5-exe-linux-vanilla-aarch64.tar.gz	Linux, 64-bit Arm	Vanilla
nocturne-0.1.5-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.5-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla
nocturne-0.1.5-exe-macos-arm64.tar.gz	macOS, Apple silicon	Enhanced
nocturne-0.1.5-exe-macos-vanilla-arm64.tar.gz	macOS, Apple silicon	Vanilla
nocturne-0.1.5-exe-macos-x86_64.tar.gz	macOS, Intel	Enhanced
nocturne-0.1.5-exe-macos-vanilla-x86_64.tar.gz	macOS, Intel	Vanilla

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Installing

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne (or nocturne.exe) sits
   beside the game's own files.
3. For the cutscenes: create a video folder in the install folder and copy the game's
   .AVI files into it. The original installer doesn't do this. The game looks in video, but
   the movies ship in AVI, which is why the retail game never played them. The name isn't
   case-sensitive, even on Linux.
4. On macOS: the build is not signed, so Gatekeeper refuses it at first. Clear the download
   flag once with xattr -dr com.apple.quarantine . inside the unpacked folder. The macOS and
   Arm builds are compiled and unit-tested in CI but have had little testing on real machines
   yet.

To keep the engine out of the install folder, run it from anywhere with
--data-dir <install folder>. Add --user-dir <folder> to keep saves, settings and logs
somewhere else too; the install is then only read.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version

What's Changed

• Recreation updates to main menu, some refactoring to make console ports easier by @NearlyTRex in #22
• Release v0.1.5 by @github-actions[bot] in #23
• Fix for older bash 3.2 support by @NearlyTRex in #24

Full Changelog: v0.1.4...v0.1.5

NocturneDecomp 0.1.4

Downloads

Each archive is a self-contained build of the engine for one platform and flavour:

Archive	Platform	Flavour
nocturne-0.1.4-exe-linux-x86_64.tar.gz	Linux, 64-bit	Enhanced
nocturne-0.1.4-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.4-exe-linux-vanilla-x86_64.tar.gz	Linux, 64-bit	Vanilla
nocturne-0.1.4-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Installing

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne (or nocturne.exe) sits
   beside the game's own files.
3. For the cutscenes: create a video folder in the install folder and copy the game's
   .AVI files into it. The original installer doesn't do this. The game looks in video, but
   the movies ship in AVI, which is why the retail game never played them. The name isn't
   case-sensitive, even on Linux.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version

What's Changed

• Some more netplay fixes by @NearlyTRex in #13
• First pass at reorg/cleanup work by @NearlyTRex in #14
• Some annotation fixes, mostly more recreation updates by @NearlyTRex in #15
• Annotation update and more recreation progress by @NearlyTRex in #16
• Bump the actions group across 1 directory with 8 updates by @dependabot[bot] in #17
• Update for CPickList annotations, readme by @NearlyTRex in #18
• More recreation worker (dialogs, loading screen, mission, actor base, ground, terrain) by @NearlyTRex in #19
• Release v0.1.4 by @github-actions[bot] in #20

New Contributors

• @dependabot[bot] made their first contribution in #17

Full Changelog: v0.1.3...v0.1.4

NocturneDecomp 0.1.3

Downloads

Each archive is a self-contained build of the engine for one platform and flavour:

Archive	Platform	Flavour
nocturne-0.1.3-exe-linux-x86_64.tar.gz	Linux, 64-bit	Enhanced
nocturne-0.1.3-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.3-exe-linux-vanilla-x86_64.tar.gz	Linux, 64-bit	Vanilla
nocturne-0.1.3-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Installing

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne (or nocturne.exe) sits
   beside the game's own files.
3. For the cutscenes: create a video folder in the install folder and copy the game's
   .AVI files into it. The original installer doesn't do this. The game looks in video, but
   the movies ship in AVI, which is why the retail game never played them. The name isn't
   case-sensitive, even on Linux.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version

What's Changed

• Netplay sync, Gabriella and Colonel actions, gameplay defect fixes, keep sync tooling by @NearlyTRex in #11
• Release v0.1.3 by @github-actions[bot] in #12

Full Changelog: v0.1.2...v0.1.3

NocturneDecomp 0.1.2

Downloads

Each archive is a self-contained build of the engine for one platform and flavour:

Archive	Platform	Flavour
nocturne-0.1.2-exe-linux-x86_64.tar.gz	Linux, 64-bit	Enhanced
nocturne-0.1.2-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.2-exe-linux-vanilla-x86_64.tar.gz	Linux, 64-bit	Vanilla
nocturne-0.1.2-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Installing

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne (or nocturne.exe) sits
   beside the game's own files.
3. For the cutscenes: create a video folder in the install folder and copy the game's
   .AVI files into it. The original installer doesn't do this. The game looks in video, but
   the movies ship in AVI, which is why the retail game never played them. The name isn't
   case-sensitive, even on Linux.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version

What's Changed

• Fixes for fog rendering, audio mixing, flashlight, vanilla build, fps overlay, ci tests by @NearlyTRex in #9
• Release v0.1.2 by @github-actions[bot] in #10

Full Changelog: v0.1.1...v0.1.2

NocturneDecomp 0.1.1

Downloads

Each archive is a self-contained build of the engine for one platform and flavour:

Archive	Platform	Flavour
nocturne-0.1.1-exe-linux-x86_64.tar.gz	Linux, 64-bit	Enhanced
nocturne-0.1.1-exe-windows-x86_64.zip	Windows, 64-bit	Enhanced
nocturne-0.1.1-exe-linux-vanilla-x86_64.tar.gz	Linux, 64-bit	Vanilla
nocturne-0.1.1-exe-windows-vanilla-x86_64.zip	Windows, 64-bit	Vanilla

• Enhanced includes the project's additions and fixes to the original's defects: the
  automap, save slots, gamepad support, windowed and borderless modes, and HUD scaling.
• Vanilla answers every authenticity toggle the way the shipped game did, so it plays as the
  retail game played, bugs included.

See docs/releasing.md
for exactly what differs.

No game data is included

These archives hold the engine only. The PODs and original executables are not redistributable,
so you need your own copy of Nocturne (1999) to play.

Installing

1. Install Nocturne from your own copy as usual.
2. Unpack the archive into that same install folder, so nocturne (or nocturne.exe) sits
   beside the game's own files.
3. For the cutscenes: create a video folder in the install folder and copy the game's
   .AVI files into it. The original installer doesn't do this. The game looks in video, but
   the movies ship in AVI, which is why the retail game never played them. The name isn't
   case-sensitive, even on Linux.

Verifying your download

Compare against SHA256SUMS.txt:

sha256sum -c SHA256SUMS.txt --ignore-missing

Each build also reports what it is, before it needs a window or any game data:

./nocturne --version

What's Changed

• Fixes for the built bundled SDL by @NearlyTRex in #1
• Fixes for vanilla mode by @NearlyTRex in #3
• Netplay fixes and additions, plus a handful of general fixes and a new debug trace by @NearlyTRex in #4
• Enhance README with project badges by @NearlyTRex in #5
• Release v0.1.1 by @github-actions[bot] in #6
• Fix for ci build by @NearlyTRex in #7
• Fixing build for windows by @NearlyTRex in #8

New Contributors

• @NearlyTRex made their first contribution in #1
• @github-actions[bot] made their first contribution in #6

Full Changelog: v0.1.0...v0.1.1