slaterain/nv-rs
slaterain/nv-rs has 330 GitHub stars and 40 forks. Star changes are not measured yet. Last checked 2026-11-18 04:42 UTC. Last push 2026-11-17.
Measured star growth
- in 24h
- Update delayed
- in 7 days
- Collecting history
- in 15 days
- Collecting history
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Fallout: New Vegas rebuilt in Rust from the original game's code. Windows preview out now; needs your own copy of the game.
Developer ToolsREADME.md
Original
nv-rs
Fallout: New Vegas, rebuilt in Rust, aiming to play exactly like the original.
nv-rs is a new engine for Fallout: New Vegas, written in Rust. It runs the game from your own copy's files. The goal: the game looks and plays exactly like the original, while everything underneath becomes a modern 64-bit engine: no 4 GB memory limit, every CPU core in use, high frame rates, fast loading, far fewer crashes, built-in modding and more platforms.
[!IMPORTANT] nv-rs is an independent project, not affiliated with or endorsed by Bethesda Softworks, ZeniMax Media, Obsidian Entertainment or Microsoft. It contains no game files; you need your own legally obtained copy of the game. See LEGAL.md.
Play the preview
Download the Windows preview: you need Fallout: New Vegas (version 1.4.0.525; only the Steam version has been tested so far) installed on a Windows PC.
- Extract the ZIP to a folder of its own, for example
C:\Games\nv-rs. - Double-click
Play.exe. It finds your game and starts it. Import my saves.cmdbrings your saves over;Settings.cmdhas the display options and the game fixes.
It never changes your game, your saves or your settings: everything it writes stays in its own folder. Windows may warn because the program isn't signed. It's a preview: so far it has only been run on one PC, so please report how it runs on yours (press F12 in the game to make a report). Keyboard and mouse only for now, and mods that need script-extender plugins (xNVSE, JIP) don't work yet. The download page lists what works and the known issues.
Where it stands
Playable. The whole game runs on its own translated code: the opening, the open world, quests, dialogue, combat, V.A.T.S., the Pip-Boy, saves, mods and the DLCs, with the original graphics and sound. Bugs remain, and it's slower than the original in busy places for now.
Next: moving the game's systems to native 64-bit Rust, one family at a time. That's what lifts the 4 GB memory limit, puts every CPU core to work and brings the speed. After it: new graphics on wgpu, a built-in script extender, more platforms, co-op and VR.
Progress
The bar counts how much of the original game's code is translated. That part is done; the table shows what's left.
| System | Status | |
|---|---|---|
| ✅ | The whole game: movement, physics, animation, graphics, sound, combat, AI, quests, dialogue, menus, saves, the open world and the DLCs | Translated, checked against the original and playable |
| ✅ | Fixes: bug fixes on by default, the original's behaviour one setting away | First fixes in: frame rate, physics, scripts, no shader-compile stutter on first use, shorter waits for loading at cell borders, cell offsets for every plugin (a plugin's cells found by a table built at load, as the game finds a master's), files read without the file thread and without the limit of 512 open files (about 140 plugins) or of 2 GB a file or an archive (TTW's LOD archives), no crash when running fast across cells, the game's threads safe where they share a scrap heap, the console, face generation and loaded models, V.A.T.S. chances without the 2-second wait, smaller saves (no witness lists), radio songs with their own length, a modded race's own beards (kept under its head's folder) offered only to that race in the character menu, and no hidden distant water under the Strip; each one can be set in the game's own Fallout.ini |
| ✅ | Windows preview | Released |
| 🔨 | Native 64-bit code: speed, no memory limit, every core in use | Started; the game's threads run on their own cores and signal each other without one shared lock, its drawing on a thread of its own, saves reach the disk from a thread of their own, its compressed archives unpack in native code and are read without reopening them, its textures, vertex and index buffers and sound samples are kept outside its 32-bit memory, and the first native families are on; finding what's on screen, the water's reflection included, is shared out over several cores |
| 🔨 | Built-in script extender: xNVSE: xNVSE's script commands, with nothing to install | Complete: xNVSE's variables, loops, functions, events, co-save, inventory references, string and array commands, keyboard and mouse input, all of its inventory, miscellaneous form, form list, faction and quest commands, all of its reference commands, its game commands (settings, loaded files, messages), its UI, console and print commands, its package, dialogue and script commands, mod-local data, its version and plugin checks, its script decompiler (DecompileScript, HasScriptCommand, and Assert's message naming the failed line), its run-time compiler for the old script syntax (console lines and scripts compiled in the game take Let, eval, loops, Call, lambdas and every expression argument), the function files of data/nvse/user_defined_functions (compiled at the first frame, CompileScript), its documentation dumps to nvse.log and its console help listing are in, with the 20 console commands it re-exports as copies of the console's own (654 of 654), format strings made exactly as the C runtime makes them, and its new script language (scripts that start with name: lambdas, for and match, string interpolation), which compiles in the console, in plugins' compiles and from function files as in xNVSE; its compiled-script cache file is left out, as it only saves compile time |
| 🔨 | Built-in script extender: JIP LN: JIP LN's script commands, with nothing to install | Started: JIP LN's table (its 1,150 slots at their own numbers) and co-save are in, and its commands are coming in (JIP LN: 948 of 1,118: climate, weather, body part and destruction data, ammo and its effects, classes, grass, lights, water, texture sets, armour, explosions, impact data, land textures, combat styles, globals, factions, perks, packages, worldspaces, image spaces, casinos, challenges, map markers, races, weapons' impulse, VATS and critical data, perk entries, levels and ranks, activators, weapon sounds, mods and models, quests and their objectives, recipes, the running image space modifiers, leveled lists, projectiles and fired projectiles, magic items' effects, object and unarmed effects, actors' spells, addiction and poison, active and timed effects and the spell target conditions, auxiliary variables and ref maps, the maths and distance commands, form ids as text, the load order and plugin checks, load screens, terminals and locks, cells (water, climate, lighting, flags, owners), radios, reference flags and radii, base forms, loaded forms by type, game settings, actor bases (aggro, services, templates, faction ranks, karma, body part data), equipped item data, the last hit's data, killers and kill XP, actors' factions, packages, idles and equipped slots, actor bases' spells, skeletons, death items, impact materials and sound templates, hotkeys and base containers, sound forms, the music state and volumes, the large address check, actors' processes, combat targets and allies, detection, leveling data, voice types and creature models, interface tiles by path (loaded, strings, clicks, removal, gradual floats, XML files, templates, menu XML through the built-in UI Organizer), the cursor, the top menu and the active tile, menu buttons, messages disabled and their flags and display times, item filters, barter caps, prices and offers, the recipe menu, VATS targets, font files, the level-up menu, menu item lists as inventory references, terminal models, the character creation check, and the event commands for menus, keys, controls, triggers, discovered locations and crafting, and for actors: animations, damage, weapons fired and reloaded, hits, critical hits, ragdolls, aid items used and projectile impacts, and the AI switches: combat disabled or a forced target, teammates' health resets, follow and wait orders, locked equipment, forced detection, disabled scripts, and the world switches: descriptions, reference names and model paths a script sets, items made unique for repairs, fast travel, cell change, target change, note, dialogue topic and quest stage events, references and form types the player may not activate, script events and activations disabled, teammates passing locked doors, the weather's transition time, swapped LOD blocks, scripts that wait, pushes without a ragdoll, and companions equipping their own gear or the companion inventory's selected item, and the getters of those switches, script blocks disabled and enabled, quest script delays, faked script events, the gamepad (sticks, triggers, buttons disabled, held and tapped), controls held and the mouse wheel, the CC&C companion commands (distances, factions, NCCS, encumbrance, location names, reputation, result scripts, positions as text, task packages), the equipped weapon's silencer, scope and mods, shots a second, the attack queue, and references' item check, type, teammates, enable and linked children, teleport doors, purge and persistent flags, primitives (read, set and added), crosshair water, fade and container moves, playing animation groups, and position, angles, turned offsets and editor place into script variables, and the game state: difficulty, detection and combat, scope and iron sights, kill cam, the Pip-Boy radio, time frozen, buffered and exterior cells, container respawns, idle loops, nav meshes, the moon's textures, days passed, hardcore stages, exact XP rewards, actor values by name and keywords, placing at a cell through JIP's position marker, moves to a cell, to the editor place, to a position text, to another reference's node, to the crosshair and by offsets (SetPosEx), turns (SetAngleEx, RotateAroundPoint) through JIP's own position, angle and cell moves, linked references set and restored at loads, and variables added to scripts, made again from the co-save at a load, and the blocks of a reference's model (translation, rotation, scale, flags, parents and children, collision nodes, materials and textures) read and written, renamed and removed, texture transform keys, animation sequences played and their speed, with its dimensions and centre, and the LN miscellaneous commands (form, ingestible and zone flags, water traits, biped model lists, pickup and container sounds, names, the player's regions and keys) and the first inventory commands (values, all items, base items, no-unequip marks, poison, inventory references for stacks, worn items, hotkeys and a scripted item, item health, armour DT and DR, items moved to a target, items added, equipped, unequipped and dropped, and an inventory reference's mod flags, health and hotkey set), and references' physics read and written: velocities, pushes, collision properties and layers, the no-collision flag, mass, contacts, phantoms, mobile and grabbable, the ray casts, the hit material and the crosshair pick); its game patches (changes to the game's own code, step 3.9) have their framework, first two fixes, the player's update 3D (both views, weapon and queued references), the detection patch (forced detection values and the detection fix), fired projectiles' ammo, count and split beams, music markers, the fatigue floor, hardcore needs and immortal mode (with ToggleHardcoreTracking and ToggleImmortalMode), inert until JIP answers "installed" |
| 🔨 | Built-in UI Organizer (UIO): UI mods' HUD and menu additions, with nothing to install | Started: its lists (Data\uio\supported.txt and the UI mods' Data\uio\public lists, with their conditions) put the mods' additions into the menus as UIO does, in memory, and menu files are read through its reader and its own XML parser (game setting values, user traits, its parse cache), and JIP's InjectUIComponent goes through it; its tile operators (17 new ones) and text zoom are in. Off until it is proven in the game (bUIO, NV_UIO) |
| 🔨 | Modern graphics (wgpu) | Started: the game's own shaders and frames draw on wgpu, on Vulkan (Direct3D 12 where a card has no Vulkan driver); on wgpu alone the game plays from the main menu into Doc Mitchell's house and out onto the Goodsprings street, and there, in the race menu and in the Pip-Boy its frames match Direct3D 9's to within 1% of pixels on Direct3D 12, while on Vulkan the graphics driver filters distant textures a shade differently (the main menu identical; measured on one NVIDIA card with the game at 4x antialiasing; at 8x it runs, its pictures not yet compared, about 8% slower than Direct3D 9 on the Goodsprings street; what the recorded places draw is prepared at the start behind a loading screen, elsewhere it still pauses briefly the first time something new is drawn; other vendors not yet checked); the default renderer in play, Settings.cmd's Renderer choosing the original's Direct3D 9 instead (which also draws by itself where Vulkan and Direct3D 12 cannot); F11 in the game shows a frame-rate counter (frames a second and the slowest recent frame) in the corner |
| ⬜ | More platforms, co-op, VR | Planned; texture loading already needs no Windows DLL (D3DX's, translated byte for byte) |
✅ means working, not free of bugs. The details are in docs/SYSTEMS.md and docs/MILESTONES.md.
Why it's different
- Translated from the original, not guessed. The original game's program is translated into Rust piece by piece, and every piece is checked against the original.
- Your game, your files. nv-rs reads the game's own data from your installation and never changes it.
- Modern underneath. The original's look and play are the reference; the internals are being rebuilt in 64-bit Rust, whose memory and thread safety rule out whole classes of crashes.
- Better where it doesn't change the game. Fixes and upgrades are switchable; the original stays available.
- Mods keep working. Regular
.espand.esmmods load the way they do in the original.
How it's made
To be upfront: nv-rs is built almost entirely with AI coding agents (mainly Claude). The maintainer directs the project: the plan, the priorities, playtesting and what gets merged.
What keeps it honest is the method: agents don't get to invent behaviour. Every piece of logic is translated from the original game's program, marked with where it came from, and checked by tests, by running it against the original's own code and by recordings of the original game. Everything is in the open, so judge it by how it plays.
Get involved
- Play and report: try the preview and open an issue for anything that differs from the original.
- Contribute: read CONTRIBUTING.md (and give AGENTS.md to your agent), say in an issue what you'd like to work on, then open a small pull request.
- Chat on the project's Discord.
- Support the project on Ko-fi. It goes to the AI time the work runs on, which is what limits how fast the project moves. It's a voluntary gift: it buys nothing and promises no release date, and you still need your own copy of the game.
- Build from source: see docs/PLAYTESTING.md. For how it works, start with docs/ENGINE_PORT_PLAN.md; every document is linked from docs/README.md.
Final decisions rest with the maintainer, slaterain (docs/GOVERNANCE.md).
Legal and license
Original code is licensed under the GNU GPL v3 or later. The licence covers only original work. Fallout and Fallout: New Vegas are trademarks of their respective owners. Read LEGAL.md for the full notice.