An unofficial native PC port of the original Xbox version of 007: Everything or Nothing, with extended graphics options and other enhancements. The game's own x86 code is statically recompiled into Windows executables with the Xbox XBE Recomp tool; the Xbox's graphics, sound and system libraries are reimplemented for Windows (Direct3D 12 or 11, XAudio2, SDL). It is not an emulator.

The European (PAL) and USA (NTSC) Xbox releases of 007: Everything or Nothing (title id 45410042). Both European discs hold the same code; the USA disc is another build of the game, which the build recognises by its default.xbe and recompiles with its own configuration (config/usa_*.toml):

The game is two programs: the driving missions are a second xbe that the game launches and returns from. Both are recompiled, into EoN.exe and EoNDriving.exe, and the switch between them happens on its own. The log names the SHA-1 of each xbe it found.

There are two ways to get the game running. Both build the game's code on your own PC from your own disc: it is never downloaded, only the program around it.

EoNLauncher.exe does everything for you: no Visual Studio, no Git, no command line, nothing installed in Windows and no admin rights needed.

You need:

• Windows 10 or 11, 64 bit, and a GPU with Direct3D 12 or Direct3D 11.
• Your own copy of the game (Europe or USA): an .iso image of your disc, or a folder with the disc's files.
• About 1 GB free, plus room for your copy of the game, and an internet connection for the game's package (under 100 MB).

Steps:

1. Download EoNLauncher.exe from the latest release.
2. Put it in a folder of its own with a short path (for example C:\Games\EoN) and run it. Everything it makes goes in an EoN folder beside it. Windows may warn about an unrecognised app: choose More info, then Run anyway.
3. Your game: choose your disc image or the folder with the disc's files. The launcher checks that it is a supported release.
4. Get the game ready: the launcher downloads your disc's package (the program and a compiler, no game code; one for the European discs, one for the USA disc), then your PC builds the game's code from your disc, in a minute or so on a recent PC. You can stop at any time; it carries on where it left off.
5. Play: press Play. In the game, F1 opens the PC settings.

When a new release is out, the launcher offers it at the top of its window: Update the launcher downloads it, checks it and restarts, then Update puts the new version in place, keeping your saves and settings. The new version is built beside the game and only replaces it once it is ready, so a failed or stopped update leaves the game as it was.

Coming from 1.0.3 or earlier: those versions built everything from source with about 1.4 GB of tools. The new launcher shows A faster way to play: press Update. Your game keeps playing until the new one is ready, and your saves and settings are kept. Afterwards, Manage > Remove the old build tools frees the space they took.

The launcher's pages: Game (your disc, the steps, Play), Manage (the install, its folders, removing build files, building the game again if it will not start) and Log.

Files, all under the EoN folder beside the launcher:

• play\ the game: EoN.exe and EoNDriving.exe, EoN.dll and EoNDriving.dll (the game's code, built on your PC), settings.toml, hdd\ (saves), logs\ (the game's logs), compiler\ (what builds the code)
• launcher.log the launcher's log (send it with any problem)

To remove everything, delete the launcher and its EoN folder (keep play\hdd if you want your saves).

You need: Windows 10 or 11 (64 bit), Git, Visual Studio 2022 (Community is fine) with Desktop development with C++ (build.bat offers to add C++ Clang tools for Windows and C++ CMake tools for Windows), about 3 GB free, and your disc's files: default.xbe, driving.xbe and the game's folders.

1. Clone the repository with its SDK:

   git clone --recurse-submodules https://github.com/hk21x/007eon-recomp.git
   cd 007eon-recomp
   

   Cloned without --recurse-submodules? Run git submodule update --init.
2. Put your game files in the assets folder: assets\default.xbe with driving.xbe and the game's folders beside it.
3. Run build.bat. The first build recompiles both xbe files and takes a while; later builds are quicker. On Windows the game's code is built into EoN.dll and EoNDriving.dll beside the exes.
4. Run out\build\release\EoN.exe. It finds the assets folder beside itself or in any folder above it.

launcher.bat builds EoNLauncher.exe itself. release-package.bat, after build.bat, makes the package for a release: once with a European disc in assets and once with the USA disc, each in a checkout of its own. Files the game writes beside the exe: settings.toml, hdd\ (saves; delete it to start again from a first boot), logs\, shadercache.bin (compiled shaders) and CrashDumps\ if it crashes.

Settings window: press F1. Display, graphics, game options and controls; changes are saved at once to settings.toml.

In the game's own menus: Options, then PC Settings, has most of the same settings, in the main menu and in the pause menu's Options tab: the first row turns the page, left and right (or a click) change a value. Key bindings, the wheel and the monitor are in the F1 window.

Smooth slow motion (Direct3D 12, driving missions at 60): slow motion moves in steps, as on the console; this fades each step into the next. It can show some ghosting on fast movement. Direct3D 11 always shows the steps.

Language: the settings window's Language choice takes effect at the next start and carries into the driving missions. Each disc has its own languages: English, Spanish, Italian, Dutch and Swedish on one European disc, French and German on the other, English alone on the US disc. A language your disc does not have is ignored.

Keyboard and mouse (remappable in the Controls tab, two keys per input):

In the menus the mouse shows a pointer: the item under it is highlighted and a click selects it; a click on a value's arrows changes it. The wheel scrolls, the right button goes back (driving missions' menus: the wheel, and the left button selects).

Driving missions have a layout of their own (rebound apart from the on-foot keys, while driving):

Controllers: Xbox, PlayStation and Switch controllers, with hot plugging and rumble.

• Display Modes - Fullscreen, borderless window or window, at any resolution the monitor offers.
• Widescreen - The game's own 16:9 mode on a widescreen display.
• Ultrawide - With aspect = "screen", the 3D view widens to fill a 21:9 or wider screen; the HUD and menus keep their 16:9 shape in the centre.
• Widescreen Driving - The driving missions, 4:3 on the console, widen to the screen's shape too, with the scenery drawn out to the screen's edges (no pop-in at the sides); their HUD and radar keep their 16:9 shape in the centre.
• Field of View - fov_percent (50 to 150, 100 the game's) widens or narrows the view on foot; cutscenes widen with it.
• Frame Rate - Vsync, a frame rate cap and an FPS counter.

• Render Scale - Renders at a percentage of the screen.
• Anisotropic Filtering, MSAA and edge smoothing (FXAA or SMAA).
• Sharpening - Sharpens the finished picture, 0 to 100% (sharpen, F1 > Graphics).
• Sharp Text and HUD - The text, menus' and HUD's pictures are enlarged with sharp edges for high resolutions (sharp_2d, on by default).
• Modern Button Pictures - The prompts show today's Xbox pad: A B X Y in the modern style, LB and RB in place of the White and Black buttons, LT and RT, and the Menu and View buttons in place of Start and Back (modern_buttons, on by default). They are drawn at four times the console's resolution, so they stay sharp at 1440p and 4K.
• Shader Cache - Compiled shaders are kept in shadercache.bin, so each is compiled once rather than in every session, and later sessions do not stutter while they compile.

All off vs. all on, at 3440x1440, at the start of Train Chase.

Edges: roof struts and the railing, enlarged three times.

• MSAA smooths the edges of the 3D scene and keeps textures sharp. The more samples, the slower.
• FXAA and SMAA smooth the finished frame, HUD included; FXAA softens it a little, SMAA less so.
• Render scale draws the picture larger than the screen: the smoothest fine detail, and the slowest.

Sharpening: a concrete wall, enlarged twice.

• Sharpening brings out texture detail that the smoothing settings soften.

• Full Driving Mix - The driving missions' music, speech and engine sounds, which the game mixes into six channels itself, are all heard on stereo speakers and headphones.

• Mouse aiming - The mouse turns the camera and aim directly (not through the stick's curve), with sensitivity and invert options; the cursor stays in the window while playing.
• Mouse in menus - The wheel scrolls, the left button selects and the right button goes back; in play the buttons do what they are bound to.
• Keyboard prompts - While you play on the keyboard and mouse, the game's button prompts show the keys and mouse buttons bound to them; they switch back when you pick up the controller.
• Every key and mouse button can be rebound in the settings window (F1, Controls tab).

• Launcher - EoNLauncher.exe: choose your disc, Build, Play, Update; portable build tools, nothing installed.
• 60 FPS Driving - The driving missions draw at 60 frames a second instead of 30, the game's timing unchanged (driving_60fps, on by default).
• Quit Game - The main menu has a Quit Game item under Options (where the console's unused Online item was), and the settings window (F1) has a Quit game button.
• Achievements - 39 achievements (every mission, medals, 00 Agent, Bond moments) with pop-ups and a list in the settings window, written in RetroAchievements' condition format; the set and its memory map are in ACHIEVEMENTS.md.
• Hide HUD - Clears the HUD on foot and in the driving missions, for screenshots (hide_hud, F1 > Game; at once). The pause screens and menus stay.
• Skip Intro Movies - skip_intro = true goes past the THX, MGM and EA logos at start.
• Cutscenes - A PAL disc's cutscenes play (the game runs as on a PAL console at 60 Hz).
• Saves - Kept on an emulated hard disk beside the exe.

• Boot Splash - Place a splash.png (or .bmp) beside the exe to display a splash screen at launch.
• Diagnostics - Logs in logs\, and frame captures (F3, with XBE_CAPTURE_DIR set).

Plays on foot and in the driving missions, with saves, up to the last mission; widescreen and ultrawide, keyboard and mouse, sharp 2D and 60 FPS driving are in. Progress is in PROGRESS.md, and technical findings in FINDINGS.md.

• Something wrong: the first lines of the log in logs\ list the settings, the GPU and any XBE_* or EON_* environment variables; leftover ones from experiments change how the game runs.
• The launcher's build failing: send EoN\launcher.log. Press Build again after a network problem: it carries on where it stopped.
• A short stutter the first time a new area or effect appears: its shaders are being compiled. They are kept in shadercache.bin, so it does not happen there again; the log's frames: lines say how many were compiled.
• Linux, Steam Deck or Bazzite (through Proton or Wine; not supported, but reported working on a ROG Ally X): if the game runs but shows nothing, or its log has compile failed lines, Wine's own shader compiler is rejecting the shaders. Install Microsoft's into the game's prefix. In Desktop Mode, with the game closed, run protontricks -l, find the launcher's App ID (a line such as Non-Steam shortcut: EoNLauncher (1234567890)), then run protontricks 1234567890 d3dcompiler_47 with that number and start the game again. If it then stops on a loading screen, rebuild it in the launcher. The next release should not need this.
• A first boot again: delete the hdd folder beside EoN.exe (EoN\play\hdd with the launcher, out\build\release\hdd when built from source). This deletes your saves.

• OS - Windows 10 or 11, 64 bit
• GPU - with support for Direct3D 12 or Direct3D 11 (F1, Graphics, Renderer; applies at the next start)

• Xbox XBE Recomp, the recompiler and runtime this is built on.
• XenonRecomp for the overridable function layout and instruction hooks.
• Zydis for decoding x86 instructions, toml++ for the configs, Dear ImGui for the settings overlay and SDL for the window, input and controllers.