Files
James Dansereau 1d15e5695a v0.5.0 final pass: AI and Deck fixes (D565-D567), docs and site refresh
Fixes:
- D565: AI awareness no longer follows two player render settings. Fog
  distance is floored at 100 (below it the shortened clip hid guards from
  AI on-screen checks); the D466 gameplay fog cull is rescaled to the game's
  own FOV (identity at defaults).
- D566: Steam Deck Game Mode no longer shows the on-screen keyboard at
  launch (SDL text input stopped; screen-keyboard hint off).
- D567: opening PC Options from the front end with a pad no longer drags
  the game's crosshair to the top-left corner.

Docs and site:
- README News/Status/Features/controls brought up to date; the unpublished
  v0.4.1 work is folded into v0.5.0 everywhere; stats to v0.5.0.
- Release notes reordered: player-facing highlights first, finding labels
  and verification at the bottom.
- Site status rewritten; favicon is now the exe icon (make_icon.py writes
  docs/favicon.ico).
- ROADMAP: AI review results, update-check follow-up, stale rows closed.

Verified: Windows + Linux builds; Windows pixel gate Surface 1 PASS;
Deck build deployed for the maintainer's Game Mode checks.
2026-10-06 21:06:48 -04:00

1.2 KiB

title, description, date, modified_time
title description date modified_time
Saves How the GoldenEye 007 PC port backs the N64's EEPROM save with a plain file you can back up. 2026-10-05 2026-10-05

Saves

GoldenEye's N64 save is EEPROM-based — the controller's EEPROM (osEeprom*), not a Memory Pak. The port backs it with a plain file, data/ge007.eep next to the executable, so your progress is a file you can copy to back it up (or move to another machine).

A few details:

  • The PFS / Memory-Pak and motor (Rumble Pak) code is only for accessory detection and is stubbed to report "no accessory," so the game proceeds without a Memory Pak.
  • Emulator saves load directly — an emulator-format ge007.eep placed in data/ is converted on first launch, so a Project64, mupen or 1964 save continues in the port (see the README's Using an emulator save).
  • The save's checksum is part of the file format. The PRNG/CRC the save depends on is kept byte-stable, because changing it would silently invalidate existing saves — a porting-notes finding (D9).
  • -fresh (a launch option) wipes the save and settings for a clean-slate run.

More: internals §7; the checksum finding is porting notes D9.