GoldenEye startup and modern-control setup.

The report and what remains unknown

The owner reported that GoldenEye stalls while Dam loads or its opening scene begins on another computer. That computer’s failure has not been reproduced here, and its cause remains unestablished. The update changes a costly optional startup feature and adds visible runtime diagnostics while the investigation continues.

Complete the native control setup, then apply Modern

The owner confirmed that Modern had been selected only in the website, while the original game’s native control style had not been changed. The two-controller analog bridge expects native 2.2 Galore. With native 1.1 still selected, its second stick is not used for that movement scheme and the first stick retains classic movement behavior.

Selecting Modern dual sticks · setup required now opens the setup steps while original N64 input remains active. Modern input stays disabled until the acknowledgement is checked and Apply modern controls is selected.

1. Start or resume a solo mission using Original N64 mapping. Open Bond’s watch with Start/Menu/Options.
2. Choose Controller Configuration → Control Style → 2.2 Galore.
3. In General Options choose Look up/down: Upright and Aim Control: Hold, then close the watch.
4. In the website panel confirm those settings, select Apply modern controls, and release both sticks and all buttons.

The acknowledgement is the player’s confirmation. The page does not inspect or change GoldenEye’s native watch settings. The native analog bridge remains the basis: left stick moves/strafes, right stick looks, RT fires and LT aims. It retains GoldenEye’s original aim-mode crouch/zoom behavior.

State loading and rewinding reset the setup acknowledgement. Reconfirm native settings after changing game folders, importing progress or returning to earlier settings. To use classic play, select Original N64 mapping here and a matching 1.x style in the watch. This update preserves the earlier 1.0.2 module as a separate historical file.

Choose history before starting

Earlier wrapper releases prepared rewind history on every launch, even when the optional playback-speed controls were off. This edition starts with Enable experimental rewind history for this session unchecked. The default runtime configuration explicitly disables rewind history. Fast-forward remains available.

To opt in, check that startup option before starting the game. The retained history settings are 32 MiB and a granularity of six. Changing the history choice requires a fresh session. It is labeled experimental because recording history adds runtime work and can be unsuitable for a particular computer. Removing that work from normal startup is a precaution; it does not establish the cause of the reported freeze.

With history off, the optional playback panel offers fast-forward only: RT fast-forwards while that panel is enabled, and LT keeps its normal aim action. With experimental history prepared, enabling the playback controls can reserve RT/LT for fast-forward/rewind. With playback controls off, both triggers keep their game actions. Loading a state still blocks rewind according to the existing save helper’s compatibility rules.

Read the playback diagnostics accurately

The new expandable Playback diagnostics panel displays a runtime callback counter. If it stops changing for more than 15 seconds while the session is ready, visible and unpaused, the panel can show a delayed-runtime message. It also reports graphics-context loss and errors associated with this player’s own runtime.

The counter advances at the entry to the frontend loop. It does not measure rendered FPS, mission progress, a completed stage load or a successful save. Advancing callbacks alone cannot prove that GoldenEye has moved beyond a frozen scene. The monitor reads no game RAM and changes no native preferences or save data.

Why serialization was examined

The retained EmulatorJS 4.2.3 configuration code exposes rewind configuration separately from the wrapper’s visible playback controls. That allowed the normal startup path to stop preparing history while preserving an explicit opt-in.

Mupen64Plus-Next PR 662 discusses a savestate/audio deadlock on Android with OpenSL and the nonthreaded GLideN64 renderer. It informed the risk review. Its platform and audio path differ from this browser player; the report does not establish an Edge diagnosis. This release includes no patch from that PR and changes no core bytes.

What stays preserved

The supplied cartridge, pinned standard nonthreaded WebGL2 core, runtime identity, configuration file and native-save helper remain byte-for-byte unchanged. The retained 1.0.2 modern module is unchanged; the new versioned 1.0.3 wrapper adds the explicit setup gate. Stable cartridge filenames, browser databases, eight state slots and mission-notebook identities remain intact. Previous releases, notes, modules and downloadable archives are retained.

The new editable modules are player-1.0.3.js, speed-controls-1.0.3.js, runtime-health-1.0.3.js and modern-controls-1.0.3.js. These wrapper changes write no ROM, game RAM or native control preferences.

Verification scope

The final candidate check used one 242.359-second core launch on an isolated local Microsoft Edge origin, with Original mapping, experimental history unchecked, and time controls and cheats off. Readable startup, Dam 00 Agent briefing and the native world were observed. Changing weapon animation and world/HUD visibility were observed continuously for the timed interval; walking and physical-controller input were not verified.

Before launch, selecting Modern displayed the required setup, unchecked acknowledgement and disabled Apply. Original mapping was restored for the stage check. The optional native controller page later showed 1.1 Honey; 2.2 Galore, Upright and Hold were not all established. No acknowledgement or Apply was performed. The observed setup gate does not establish actual dual-stick play or a successful full setup.

The session was paused normally and closed at 13:56:13.874 UTC. Runtime callbacks were supplemental diagnostics; the changing native imagery and ordered watch/world responses provide the stated local continuity evidence. These observations do not reproduce the other computer’s freeze, establish its cause, prove an experimental-history session or establish public delivery.

The first Edge baseline and candidate sessions both produced black native images. During the candidate inspection, the primary Edge window was found minimized. Responsive wrapper buttons and slowly advancing callbacks did not establish native stage continuity. Both sessions were paused and closed; neither is a passing visual comparison or evidence that the other computer’s reported problem has been fixed. That first comparison remains incomplete; the later foreground candidate observations below are a separate check.

Source checks passed: 33 speed/input, 28 runtime-health, 31 modern-setup and nine integration checks. One isolated foreground Microsoft Edge candidate session observed Dam on 00 Agent with changing native weapon imagery and world/HUD visible over 40.936 seconds, followed by native watch open, close and resumed world. The website’s pending setup and disabled Apply button were observed; native 2.2 Galore/Upright/Hold setup, Apply and physical-controller behavior were not verified. The reported freeze on another computer has not been reproduced; its cause remains unestablished.

Source tests and local Edge observations are separate from reproducing the owner’s other-computer failure. Physical controller response, state execution, native cartridge save/reload durability, full campaign completion and cheat effects remain unverified.

Exact verification record · Open the player · Download website edition 1.0.3

Earlier notes: Modern dual-stick controls · Renderer repair · Original edition. Retained downloads: 1.0.2 · 1.0.1 · 1.0.0.