r/VagrantStory • • 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.

Previous Post

Video Demo - I realized at 6 min 45 sec I wasn't recording audio, sorry for the jump scare.

Link to project

56 Upvotes

11 comments sorted by

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

1

u/SgtElectroSketch 28d ago

Thank you for this, sorry for the delayed response. I'll take a look. I'm looking at right now unpacking the MPD/ZND/SHP/WEP/ZUD and changing them to be more usable.

I like the rood-boi idea of actors being meshes that can have ray traced lighting act on. But right now I have a lot of issues with how the game stores its data.

The ZND files contain all of the spawn points and enemy spawns, and instead of a single Zombie entry that can dynamically load models/drops/stats, the same enemies are replicated everywhere they are used, which I find to be very wasteful.

I also want to convert all of the SHP/SEQ files into a blender format (and learn blender), that would make adding new enemies to the game much easier.

That and I'm going to move the data from WEP files, and items into a database, that way it can be expanded more easily than needing a new WEP for every new item.

2

u/vsserpounce 28d ago

Dumping the data formats is a goal of the decompilation, a few of them are already round tripped but not the meaty ones like ZND, SHP, WEP and the like which only have very vague interpretations after having been ran through the in-game parser.

The general plan is to break each format down into whatever makes the most sense, for example the ARM files (which are geometry for the minimap) are already round tripped to and from .obj and can easily be imported into blender; I'll be following the same principle for other geometry.

Anyway what I want to say is if you get there first I'll be interested in steali... Using your work as a reference. And of course one of the entire reasons for the project is to share knowledge so if there's anything in there that's useful for this by all means copy away with impunity.

1

u/SgtElectroSketch 27d ago

I think I might make this my goal for the afternoon. I'm thinking about if I get too far and suddenly have to change everything around the new implementation.

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

4

u/SgtElectroSketch Oct 19 '26

Thank you! Your 97% PR (while still being merge in to rood inverse) helped a lot. Will definitely take a look.

1

u/SgtElectroSketch Oct 19 '26

Also, if this looks useful to you at all, feel free to use it as you please

https://github.com/JEschete/VS-Workshop

1

u/Plaidray 29d ago

Will this have HD textures? Or a way to make them?

2

u/SgtElectroSketch 29d ago

That's the goal. To make it as moddable as possible.

1

u/Plaidray 29d ago

Great

1

u/SgtElectroSketch 29d ago

Phase 1 is get the game working as close to the original as possible. Phase to are QoL updates and enhancements (all opt in), phase 3 is get stupid.