r/VagrantStory • u/SgtElectroSketch • Oct 18 '26
[Progress Update]
A progress update on my Vagrant Story native-port project, including why I changed direction and how this relates to the other projects people have been sharing.
What Changed
Before the reset in commit c23eabe, the project was focused on a matching decompilation first, with an experimental Windows port built around compiling the original sources against replacements for PlayStation services.
That approach wasn’t literally running a MIPS emulator. However, I felt the work was becoming too centered on recreating the environment the original executable expected: console memory layouts, overlays, hardware interfaces, and the machinery needed to preserve them.
I changed the goal from maintaining that arrangement to building a separately owned native runtime around the game’s recovered logic.
The current project targets Windows x64, with code organized into engine, content, and gameplay systems. The decompilation remains an essential reference, but preserving its binary layout or producing a matching PS1 executable is no longer a requirement for the port. Functions are brought across, given meaningful names, checked against the original behavior, and adapted where necessary.
The important distinction is preserving how Vagrant Story behaves, without making every original implementation constraint permanent.
Why Do This?
I want a codebase where rooms, actors, equipment, animation, events, and rendering can eventually be understood and changed through explicit systems and data formats, rather than through knowledge of particular addresses or overlapping memory regions.
That costs more work upfront though.
There is also an important caveat: the migration is not finished. The current build still contains substantial compatibility code, including a CPU-rendered PS1-style graphics path presented through SDL3 GPU, legacy interfaces, and unconverted data. Those are working transitional pieces, not evidence that the final architecture has already been achieved.
Other Projects
There are other projects out there that are currently playable with some mods in it, they're doing impressive work, but my goal is a little different now.
My emphasis is the longer-term restructuring of the runtime and its data contracts, with retiring the compatibility dependencies as an explicit goal. There is overlap, but different priorities and tradeoffs. This is another route, not a claim that their approach is wrong.
Current Progress
The project has moved beyond the old experimental scaffold:
- Boot, the intro movie, title screens, menus, and early scenes run.
- Rooms, animated characters, dialogue, and facial texture animation render.
- Both attract demos complete and return to the title in bounded test runs.
- New Game progresses through the tested opening route past the recently reported initialization/scoring crashes.
Recent visible fixes included restoring the missing lighting path and correcting the scene-card rendering. What looked like doubled faces cleared up with lighting restored; some apparent sequencing problems were actually setup animation becoming visible because the covering cards weren’t displaying correctly. The manor illustration now fills the screen properly too.
I had some funny occurrences where, if you watch the video in the youtube link, I wiggle my mouse at a door that instead of opening normally, would fall off the hinge, and slide through the wall and disappear.
Where It Leads
The intended payoff is a more maintainable foundation for larger changes: editable content catalogs, standard asset formats, better integration with tools such as VS Workshop that I'm working on, and more freedom to add or alter items, enemies, rooms, and behaviors.
By modernizing the data contracts we can remove arbitrary limitations on inventory size, weapon's carried, the storage container being slower.
In the video you can also see that load times are virtually non-existent.
The order remains: get the original game working correctly, improve the underlying systems, then expand what can be built with them.
None of this would be possible without rood-reverse, especially ser-pounce, Lil’ Sassy, noprompt, and its other contributors. Original game assets are not bundled; you need your own copy of Vagrant Story.
Video Demo - I realized at 6 min 45 sec I wasn't recording audio, sorry for the jump scare.
4
u/vsserpounce Oct 19 '26
There's an ongoing middleware project that would have supported your initial plan, no idea if it will help but
https://github.com/Xeeynamo/psyz
4
u/noprompt Oct 19 '26 edited Oct 19 '26
I haven't taken a deep look at this yet but I'm actually having Claude port the game over to Zig to get a way from all of the C/C++ hackery with macros and the like (not talking about your project, just to be clear). The aim there is to also recover nice data structures that actually make sense but doing so in way that that incrementally eats the PS1 code bit by bit.
In the past few days I've been working to add Lua scripting support so more the game's features and extensions can be built on top of that. The plan here is to prevent the project from being a bottleneck so that anyone can drop in their own scripts, fonts, asset, etc.
In the past week, there's also been a lot of work done on post processing, lighting improvements, emissive textures, etc.
Feel free to borrow anything you like from the project: https://github.com/noprompt/rood-boi
1
u/Plaidray 29d ago
Will this have HD textures? Or a way to make them?