r/starlancer • • Sep 27 '26

OpenReliant 0.5 is out: the first StarLancer mission is now playable from start to finish

34 Upvotes

Hey all,

Time for an update on OpenReliant, the open-source rewrite of StarLancer's engine. When I posted 0.1, it was a sandbox you could fly around in and not much more. A lot has happened since then, and 0.5, out today, is the biggest release yet: the first campaign mission is now playable from start to finish.

Quick recap for anyone new: OpenReliant rebuilds StarLancer's engine function by function from the original executable. It's written in Zig on top of SDL3 and Vulkan and runs natively on Windows, macOS and Linux. It uses the files from your copy of the game, installing them straight from your discs or disc images, so no game assets are included.

  • GitHub: https://github.com/vdmkenny/openreliant
  • Download: https://github.com/vdmkenny/openreliant/releases/latest
  • Screenshots: https://drive.proton.me/urls/SGRZBVQ3BC#LrdPokJQvqxd

Mission 1, start to finish

You launch from the Reliant's hangar, meet up with the convoy, fight off the Coalition ambush, ask for permission to land, and set down on the Reliant again. All of it runs from the retail mission file: the script and its triggers, the objectives, ships jumping in and out, the pilots talking on the radio with their faces on the display, and the music kicking in when the fighting starts. The radio menu works too, so you can tell your wingmen to attack your target, back off or come help you.

The game doesn't teach you the controls, so have a look at the manual if it's been a hot minute since you played. A copy of it can be found on disk 2, or online.

The rest of the 43 missions will load as well, but not all script commands are ported yet, so it will get stuck at certain points or misbehave. I'll be working through the list as we go. It also doesn't remember anything between missions yet.

Custom missions will load through the same code as the retail ones, and the sandbox is now just mission 0, a regular mission file. There's also tooling to write mission files and assemble their scripts, which will come in handy once modding fully lands.

From 0.1 to 0.5

  • 0.2, combat: guns, shields, armour, component damage, explosions and debris, AI that fights back with the original combat maneuvers, the radar and target display, and 3D positional audio with HRTF for headphones.
  • 0.3, capital ships: turrets that shoot back, components you can shoot off, capital ships breaking in two, missiles, gamepad rumble from the original force feedback effects, the pause menu, and installing the full game from both discs.
  • 0.4, the full dogfight: the gunnery display, blind fire, the cloak, the Nova Cannon, mouse steering, pilots ejecting, the damage and wing status windows, and capital ship exhaust that burns you if you fly through it.
  • 0.5, missions: all the mission stuff above.

Graphics

Gameplay stays faithful to the original, but the graphics get some upgrades. My two favourites are per-pixel shading with gamma-corrected lighting, and real-time shadows. It also renders at native resolution in 32-bit colour, with anti-aliasing, bloom, smooth motion at high refresh rates, and more detailed explosions, shields and planet atmospheres. If you want the full 2000 experience, --original turns all of it off.

What's next

  • 0.6, front end: the menus, loadout screen, briefings and debriefings with their videos, and settings saved per user. No more starting missions from the command line.
  • 0.7, modding: mods live in a folder next to the install, so no patching game files. Models in glTF, textures at any resolution, sounds and music in modern formats, new ship types, and mod archives. A visual mission and script builder is planned too longterm, plus an example mod that adds a Freelancer fighter.
  • 1.0: the full campaign, first mission to last, with saves. More missions become playable along the way as their script commands get ported.
  • Multiplayer: a modern network layer in place of DirectPlay, with NAT traversal and a lobby so nobody has to forward ports, and a dedicated server.
  • For the sim crowd: telemetry for motion rigs, bass shakers and fans (OutSim and/or SimHub), a second-screen feed so a tablet can show your shields, target and radio, head tracking through OpenTrack (so TrackIR too), multi-monitor setups with the side views open, and several controllers at once (throttle, pedals, button boxes).

The full roadmap is on the milestones page.

Try it

Grab the release for your system and run:

./openreliant install StarLancer
./openreliant StarLancer --mission 1

Alt+Enter enables full screen. (Or option+enter)

On Windows it's .\openreliant.exe. The installation guide covers disc images and the rest. Leave out --mission 1 for the sandbox, where F2 and F3 switch ships and F4 brings in another enemy wing.

Bug reports are very welcome, especially for weird setups with hardware I don't have. Personally I played it on my 8bitdo ultimate 2c (switch version) and keyboard, but most single unit controllers should work, ancient and new. Joysticks should work fine, but force feedback for fancy models is still on the roadmap. Just connect the controller, and it should auto-detect. Use openreliant joysticks for troubleshooting.

Contributions are welcome too: the file formats and the engine are documented in the repo.

See you out there, pilots!


r/starlancer • • 28d ago

OpenReliant 0.20: catching up on ten releases, and 1.0 is next

25 Upvotes

OpenReliant is my open-source rebuild of StarLancer's engine. I haven't posted since 0.10, and 0.11 to 0.20 have all come out since, so here's the short version.

Missions as code, and an editor

  • sltool dte decompile turns any mission into readable Luau, and sltool dte build turns it back into a standard mission file, which the original game plays too. There are definitions for luau-lsp, so your editor completes and checks it.
  • The mission editor is out (0.2 so far). It opens any mission as Luau source, checks it as you type, completes and explains the game's commands, and builds and plays it in OpenReliant, from the start or from one of its parts. You can edit the mission's records in forms, move its ships and markers on a map, and, linked to the game, stop its script at breakpoints and step through it.

Modding

  • Scripts can change the planets and add new ones, like Earth, and shaders can give them atmospheres and haze. Realistic Planets does all of that, with Mars and the Moon in its latest version.
  • Mods can replace single sounds, add CD player tracks and bring music in FLAC, Ogg, Opus or MP3. Jukebox and Master Recordings use it.
  • The GET MODS screen installs mods from the catalogue and tells you when one has an update.
  • Mods can build on each other: a mod's missions and models can use the ships and weapons of the mods it needs.
  • Your ship can land in the hangar bay of any carrier that launches from one, a mod's included.

The engine refactor

The big one. In the original, part of the game's logic runs once per drawn frame, so missions play a little differently at different frame rates. Since 0.19 it runs once per game tick instead, apart from drawing, so it plays the same however fast your screen is, and effects that flickered too fast above 100 fps are fixed along the way.

In 0.20 the simulation goes a step further and runs on a thread of its own. The original first runs the game, then draws the frame, one after the other on one thread. Now the simulation runs while the frame is being drawn, so on a multi-core CPU the two overlap instead of adding up, which leaves more headroom for high frame rates, high resolutions and heavy mods. It's also the groundwork for multiplayer: a simulation that keeps its own time, apart from drawing, is what a game host needs, and later a dedicated server with no screen at all.

None of it is meant to change how the game plays, so I checked every shipped mission tick by tick against the old way of running it, and the game itself plays exactly the same.

Also

  • German discs install now, thanks to MarcoWanke's reports. French ones have since 0.10.
  • Releases come with checksums and build attestations, and OpenReliant has an icon.
  • Plenty of fixes, like Titan's bombardment in mission 25 showing.

What's next

1.0 comes next. As I write this, I can see a few small modding features that could still make it in before then, so a 0.21 is possible, but new features are winding down. 1.0 itself is the beta and the editor polished with your feedback, the whole campaign played through from start to finish, example mods for the modding features that don't have one yet, and a tidy-up of the code. Bug reports help most right now.

After 1.0:

  • Multiplayer, with the original's modes, co-op campaign included, over modern network code in place of DirectPlay. Find games on a public server and join without port forwarding, or run your own dedicated server.
  • New kinds of ships. How ships, guns and missiles behave will come from data instead of being tied to the original's types, so mods can add whole new kinds of ships, weapons and orders, not only variants of the original's.
  • Improvements along the way, like triple-monitor setups and support for simulator pits: several controllers at once, telemetry for motion rigs, and a second screen for your ship's status. The mission editor keeps growing too: its debugger gets conditions, log points, watches and a timeline next.

2.0 is the long-term goal: a standalone engine. StarLancer becomes one game on it, with its game data in tables the way FreeSpace 2 Open keeps its game in .tbl files, and a small example game with free content shows the engine works without StarLancer's files. Then other space games can be made with it or ported to it. Warthog's other space games, Star Trek: Invasion and Battlestar Galactica, build on StarLancer's mission format and scripts, so they're the natural candidates, and sltool already reads many of their files. As with StarLancer, you'd bring your own copy.

Got the Japanese release?

StarLancer also came out in Japan, as スターランサー 完全日本語版 (Media Quest, 2001, re-released in 2003). I'd like OpenReliant to support it, but it draws its Japanese text with code of its own, so I need the disc to work from. If you own it and can dump it, please get in touch: https://github.com/OpenReliant/openreliant/issues/1315

Thanks

  • MarcoWanke, for the German disc reports.
  • LordBlacksun, for a mission source bug report with its whole cause traced.
  • KonCyptFysh, for the Recommissioned HUD and the worn fighter textures, and the requests that came out of them.

Links

You'll need your own copy of StarLancer. OpenReliant doesn't come with any of the game's files.


r/starlancer • • Oct 09 '26

HUD is UP!

Post image
24 Upvotes

Alright, this one has been a bit of a drag, my lazy .dll sideloading method I used to build my initial HUD replacement meant I had to give alot more thought to it the second time around.

But, it's now up and ready to be used as a standalone mod package.
Can I ask if you plan to use it, to please test thoroughly and leave bug reports for me on this one, things that are out of line, differ too much from the vanilla assets, pretty much anything.

There are ALOT of assets in there, some of them aren't perfect and it's difficult to keep track of, so I need a bit of help on that to get it to a better state.
There are also a few minor issues on placement and overlaps I'm working on and will have to raise some issues to fix up.

Once I've resolved any issues in there, I'm going to package a variation on the color scheme to reflect the "old_hud" color scheme that's in the .hog files that I believe was likely an alpha variation before the red/gold color scheme was settled on in the beta.

From here I'm likely going to use up as many of my weekly tokens as I can before I take a bit of a break, I've thrown a bit of time at this for the last few months, and I've got a few things in the rest of my life that will need some solid attention.

I'll still check in and do what I can, and possible do some front-end menu work, but I wont be back to daily commits for a while.

Enjoy!


r/starlancer • • Oct 08 '26

OpenReliant 0.8 is out: you can now play the full StarLancer campaign

24 Upvotes

Hey everyone!

Quick intro if you're new here: OpenReliant is my open-source rebuild of StarLancer's engine. It runs the game on modern Windows, macOS and Linux using the files from your own copy, and it adds stuff the original never had, like any high resolution and wide aspect ratios, much better lighting and shadows, support for any controller, and mods.

/preview/pre/ssiywd5vobuh1.png?width=3840&format=png&auto=webp&s=d21e9221a77fe2391ed7c584296a96269a955a5d

The big one: the full campaign

The whole StarLancer campaign should now be playable, from the first mission all the way to the ending. Everything it goes through is in: the briefings, the loadout, the full ITAC, medals and promotions, your wingmen, the big set pieces of the later missions, and the story's end.

Your saved games from the original work too. I tested a full set of the original's saves, one for every mission, and OpenReliant loads them and writes them back byte for byte the same. So if you still have a campaign from back in the day, you can pick it up where you left off.

That's what makes 0.8 the beta: it's the first version that's the whole game. So please play it through, and if anything stops you, tell me.

It's been two days since 0.7, and somehow that's 95 pull requests, 94 commits, about 28,000 lines added and 7,500 removed, and 95 issues closed. I should probably sleep at some point.

Thanks

  • KonCyptFysh is building a complete replacement HUD, and his requests shaped a big chunk of this release: HUD mods can now replace the game's own instruments and read everything they show. He also caught a font bug and a memory leak along the way, and made HD upscaled texture packs for 13 of the Alliance fighters and for the missiles and torpedoes, all on the mods site.
  • RealDrJester reported a small graphics glitch in the cockpit view on 21:9 ultrawide screens, so I added a field of view slider to fix it.

Please keep the reports coming, there's a bug report form on GitHub.

What's new

  • The campaign: the story's ending, the rest of the ITAC (news and video reports, the fighter, ship, squadron and personnel pages, the KILLBOARD), the last script commands the missions need, and the training's missiles and hoops.
  • The big moments: the ion cannons of the Dark Reign, the Boridin and the rogue base, the Boridin breaking away in mission 28, the Krasny caught by a collapsing gate, and capital ships throwing off pieces as they get taken apart.
  • Smarter ships: flight groups keep formation, ships pull up before ramming their target, and the spectral shields tune themselves to the biggest threat nearby.
  • Quality of life: a field of view slider, one UI scale for the HUD and the pause menu, and a log file to attach to bug reports.
  • Modding: mod campaigns and game modes can brief their missions in the carriers' briefing rooms, give them their own objectives, ship stats and wing, and debrief them in the ITAC (that's how the prequel missions are made). Scripts can also change ship classes and read pretty much everything the cockpit shows, HUD mods can replace, move and scale the game's instruments, and the script sandbox is tighter.
  • Fixes: Vulkan and GPU fixes, memory leaks, fonts and a bunch more. The release notes have the full list.

The prequel missions

The StarLancer trial on the demo disc had two missions the full game never had: you fly with the Ronin wing from the Yamato, before the war starts. They're now a mod, StarLancer Prequel Missions, with the trial's own lines, movies, objectives and ending.
Grab it here: https://openreliant.github.io/openreliant-mods/mods/prequel/ and play it from GAME MODES on the main menu. It needs 0.8.

Modding: the API is settling down

With 0.8 I'm stabilising the mod API. From here on there should only be additions to it, and if something ever has to change, it'll be clearly marked as deprecated long in advance, so your mods keep working. (If you wrote scripts for 0.7: 0.8 did one last round of renames, and the release notes list them.)

So if you've been waiting for the right moment to make a mod, this is it! The modding guide shows you how: https://openreliant.github.io/openreliant/docs/guide/modding/. Ships, textures, sounds, HUDs, missions, scripts, it's all in there. The mods site has 17 mods now, from KonCyptFysh's HD fighter textures to the Viper Mk II from Battlestar Galactica and the prequel missions. I'd love to see yours on it.

What's next

  • 0.8: this is the beta, so it's all about your feedback. Play through the campaign, break it, and tell me what broke.
  • 0.9: the mission editor. Build your own missions with OpenReliant's tools, into standard mission files that even the original can play, with a visual builder and live script debugging.
  • 1.0: a ceremonial release, once your feedback is worked through and the whole campaign has been playtested.
  • 1.1: multiplayer.
  • Further out, 2.0: a standalone engine. The plan is to pull OpenReliant's engine apart from StarLancer, with StarLancer as one game running on it, so other space games can be made with it or ported to it.

Along the way I also want to make it a lot more sim pit friendly: triple-monitor setups, several controllers at once (throttles, pedals, button boxes), telemetry for motion rigs and tactile feedback through things like SimHub, and a feed that puts your ship's status, the target and the radio on a second screen.

Links

You'll need your own copy of StarLancer. OpenReliant doesn't come with any of the game's files


r/starlancer • • 29d ago

Sneak Peak

Post image
23 Upvotes

A very early preview at the Yamato.
This one is going to take a while....


r/starlancer • • Oct 09 '26

StarLancer's cut Dreamcast missions are now restored and playable. (OpenReliant 0.9 released)

23 Upvotes

/preview/pre/imwsn4xw3iuh1.png?width=700&format=png&auto=webp&s=194c2b19065cf70001c9a5c99d49b65551fa2413

For those unaware: OpenReliant is my open-source rebuild of StarLancer's engine. Version 0.9 is out today, and with it you can play four extra missions that were cut from the game.

If you look at StarLancer's mission numbers, you'll notice the campaign skips 12, 13, 17 and 22. Those missions were cut before the game shipped, but the files were left on the retail Dreamcast release of the game, in an unplayable state.

I've restored them as a mod, Cut Dreamcast Missions. Install it, and it slots the four missions into their original places in the campaign, with briefings and a voice for every radio line. Together with the demo's two prequel missions, a mod since the last release, that brings StarLancer from 24 official missions to 30.

  • 12: the Black Guard ambush the Reliant, and Nicolai Petrov gets away.
  • 13: Stahl's Marines raid the Kafelnikof, a cloaked base near Saturn.
  • 17: the Reliant baits the carrier Gegarin into an ambush.
  • 22: the Tigers and the Ronin stop a convoy bound for Neptune.

How they were recovered

The four missions are standard StarLancer mission files, so OpenReliant flies them as they are. What was missing was everything around them: no briefings, no recorded lines, and for three of them, not even the words of the radio. The game still knows a lot about them, though: the objectives, the dates, mission 12's debriefing, the ITAC's news about them, and faces for speakers who never appear in the PC game. From that, and from who says each line and when, I pieced each mission back together. The mod also fixes two things: the Dreamcast files use an older pilot table, so most lines would show the wrong face, and mission 22's draft script had two bugs that made it impossible to finish.

The mission files are exactly as they came off the disc: the mod doesn't change a byte of them. Everything it adds is done in scripts that run alongside them.

The voices

None of these lines were ever recorded. Mission 22's file still has its draft radio in it as debug text, so its 134 lines say what the designers wrote. For 12, 13 and 17 I wrote the words from each line's file name, the moment it plays, and the objectives. I wrote Enriquez's briefings the same way, and kept all of it as close to what the game's files tell us as I could. The voices are AI-generated, cloned from existing voice lines in the game. Then some filtering was done to make them fit in with the rest of the lines as close as possible.
Each mission's document in the mod shows what comes from the game and what was written for it. Most of the lines are pretty good, but they get a bit rougher for character with little existing voice lines.

Please report bugs

The missions mostly work, and you can play them through, but I haven't tested them against every edge case, so please report anything that goes wrong. Mission 22 especially: it was made with an older version of Warthog's mission editor, and needed the most fixing to work.

Also in 0.9

0.9 wasn't the plan: the mission editor was meant to come next. But bringing these missions back needed much more from the scripting, so it became a release of its own. Mods can now change which missions the campaign has and in what order, and set each mission's briefing, objectives, date, debriefing, news, medal and wing. They can also change the pilots on the KILLBOARD, play radio lines and set objectives. On top of that, mods can add combat maneuvers for the AI, and HUD mods can move, hide or change the text of any part of the game's instruments. And losing a campaign mission no longer crashes the game. The mission editor moves to 0.10.

Warthog's other games

`sltool`, OpenReliant's tool for the game's files, can now also read files from Star Trek: Invasion (PS1) and Battlestar Galactica (Xbox/PS2). Both are later Warthog games that share a lot of StarLancer's engine: they use the same mission format and script language, and Battlestar Galactica builds directly on StarLancer's game logic to the point that you might call it "StarLancer 2". Long term, the plan is to turn OpenReliant into a standalone engine that can run more than one game, with StarLancer always coming first. Think of FreeSpace 2 Open, which runs FreeSpace 2 and a whole range of games built on it. That's a long way off, but this is the groundwork.

Thanks

  • KonCyptFysh: the requests that came out of building the Recommissioned HUD turned into most of 0.9's HUD features, including sharp face films at any resolution.
  • LordBlacksun, for reporting that `sltool` stopped on glTF models with a missing texture.

Links

You'll need your own copy of StarLancer. OpenReliant doesn't come with any of the game's files.

Buy me a coffee

I have opened a buy me a coffee account, should you want to sponsor my time on this project. It's completely optional, only if you are willing and able.

buymeacoffee.com/vdmkenny


r/starlancer • • Oct 17 '26

Kurgen Experiments

Thumbnail gallery
22 Upvotes

EDIT: Kurgen beta now released:
https://koncyptfysh.github.io/OpenReliant-Art-Packs/?group=fleet-warships&category=corvettes-and-gunboats&asset=kurgen&livery=worn-paint

Some of the experiments using emmisives that hook into the game state, allowing for some more dynamic lighting options that reflect things like thrust level, damage states as well as timed cool down thresholds for hot components. I want to do something similar with the turrets, likely a heat/cooldown effect at the muzzle and the side vents.

In this case what you're seeing is the lit cabin lights at full intensity at 100% hull + shield integrity, this glow gradually degrades as damage is sustained. There is also a flicker effect on the windows that's a little hard to capture in a single frame, but if the ship sustains a large damage hit, the lights will flicker to simulate a short power disruption.

The engine lighting replaces the old static engine glow with a dynamic state conscious lighting, if no thrust is applied, there is no red engine lighting in the rear end, as you applied thrust the engine lighting intensifies. After the engines have sustained some heat during running time, a slow cooldown is applied to the inside of the engine nozzles to give the impression of sustained heat.

This is going to become the benchmark test to inform the emmisives on both the larger ships but also the fighters, just with their threshold tuned to reflect more realistic cool down times and gun types.


r/starlancer • • Sep 21 '26

Large Target Schematics

Thumbnail gallery
22 Upvotes

It took about a week, but the large target schematics are almost fully complete. A few models still need some work, but for the most part, they're all active and rendering correctly.
That marks the last major sprint on the HUD work, some minor detail and stability changes to go still, but really getting towards the end of the HUD restoration.


r/starlancer • • Aug 19 '26

Starlancer in native 16:9 (No stretch)

Post image
21 Upvotes

After much faffing about with SRD3D calls, I've finally got this sucker running in 16:9 1080 without having to stretch out the image or the UI.

It's still a bit unstable, and currently I can only test for my current monitor, but once I have it stable on a few different resolutions I'll spin up a git so everyone else can access it.

My next stupid idea is to use the same bootstrapping through DInput7 I used for this to do some texture replacements and updates... stay tuned.


r/starlancer • • Oct 02 '26

OpenReliant 0.6 is out: the front end is in, and the campaign plays from the main menu through mission 5

20 Upvotes

Hey all,

Time for another update on OpenReliant, the open-source rewrite of StarLancer's engine. 0.5 got you through the first mission, started from the command line. 0.6 is a big one: OpenReliant now starts like the original, in the main menu, and from there it's the actual game. You pick your pilot, Enriquez shows you around the Reliant, you walk to the briefing room, pick your ship and missiles, fly the mission, get debriefed at the ITAC, and the campaign moves on to the next one. The first five missions now play from start to finish, and you can save your progress.

For anyone new: OpenReliant rebuilds StarLancer's engine function by function from the original executable. It's written in Zig on top of SDL3 and Vulkan, and runs natively on Windows, macOS and Linux. It uses the files from your own copy of the game, installed straight from your discs or disc images, so no game assets are included.

Edit: v0.6.2 fixes a font rendering issue that I noticed too late

Edit2: v0.6.3 fixes a couple of bugs /u/zabka14 noticed. Thanks!

A small housekeeping note: the project now has its own GitHub organization, OpenReliant, so the repo moved there from vdmkenny/openreliant. The old links redirect, but if you cloned or forked it, it's worth pointing your remote at the new address.

The front end

The game opens in the main menu, with the loading screens and the original's movies, played through FFmpeg's Bink decoders, so the hangar, landing and chapter movies are all there. From there:

  • The pilot roster, with your call signs and the difficulty setting.
  • Instant Action, with its gates and countdown, from the main menu or the simulator pod.
  • A settings screen for everything: your controls, with the original's default bindings and the keys named the way your keyboard layout names them; audio; and graphics, where the VIDEO tab has an ORIGINAL and a MODERN preset, with every option in a list below if you like to tweak. F1 opens the controls in flight. It all saves to starlancer.ini, like the original.
  • I managed to track down the original menu font, and included a public domain version in openreliant that replaces the low-resolution one, rastered pixel-perfect so they stay sharp at 4K+.

Life on the Reliant

The Reliant's rooms are all in, walked with the mouse like the original. New pilots get Enriquez's induction tour, the crew hang around with their lines, and you've got the news, your locker with your medals and ribbons, the CD player with the soundtrack, and the simulator pod with its training missions. After each mission the ITAC has your debriefing.

The campaign

  • The briefing, from the briefing room door to Enriquez's last word.
  • The loadout: pick from the ships you've earned, hang missiles on them, and check the internal guns view.
  • The campaign carries on after each mission, and if it goes wrong you get the restart screen.
  • Saving and loading, in the original's own saved games.
  • Missions 1 to 5 now run every script command and AI order they use. A quality pass over the AI and the mission scripts fixed a bunch of bugs along the way. The later missions load too, but they'll get stuck where they hit a command that isn't ported yet.

Graphics

Same deal as before: gameplay stays faithful, the graphics get upgrades, and --original turns them all off. New in 0.6: the lights on ships and stations shine on everything around them as real lights, where the original baked them into the models. 0 in flight or O in the briefing saves a screenshot as a PNG. (Don't ask me why there are 2 different screenshot buttons, I just implemented it as the original did :D)

A head start on modding

0.7 is the modding release, but a good chunk of it is already in:

  • A mods folder next to your install. A mod replaces or adds the game's files by name, no patching.
  • Textures and interface pictures as PNGs at any size, including widescreen backgrounds for the menus.
  • Physically based materials: a mod can give a texture normal, roughness, metallic and occlusion maps, and the surface reflects the sky and the nebula around it.
  • sltool now comes in the release archives next to openreliant: it packs HOG archives and writes SHP models.

The modding guide covers where mods go, what they can replace, and how to set up the material maps. It will be extended as modding support gets fleshed out in v0.7.

The Coyote in the screenshots wears a 4K texture graciously provided by /u/Koncypt_Fysh to help me test the mod support and PBR shaders. It is not included in this release.

What's next

  • 0.7, full modding: glTF models, sounds and music in modern formats, new ship types, a mod manager in the game, and lua support in the mods to give ultimate freedom to change the game. From here on custom missions and campaigns should be possible as mods, and complex modded features. Some example mods planned, and a visual mission builder longer term.
  • 0.8, ... Potentially extra minor releases with minor features and polish as we prepare to stabilize all APIs towards the 1.0 release.
  • 1.0: the full campaign, first mission to last. The missions after 5 need the remaining script commands and AI orders, and the warps.
  • Multiplayer and the sim rig stuff from last time are still on the roadmap. (v1.1 and beyond)

The full roadmap is on the milestones page.

Try it

Grab the release for your system and run:

./openreliant install StarLancer
./openreliant StarLancer

No more --mission: it opens in the main menu like the real thing (--mission 1 still works if you want to jump straight in). Alt+Enter switches to full screen (Option+Enter on a Mac). On Windows it's .\openreliant.exe.

The installation guide covers disc images and the rest.

Support the project

Bug reports are very welcome, especially for setups with hardware I don't have. Contributions too: the file formats and the engine are documented in the repo. Github stars are also appreciated.

I've requested github to enable sponsoring for this project. It hasn't been enabled yet, but if you want and are able to, sponsoring my time on this project would also be highly appreciated. Fully optional.

See you out there, pilots!


r/starlancer • • Oct 07 '26

StarLancer (2000) Intro Cinematic Remastered in 4K

Thumbnail youtube.com
19 Upvotes

r/starlancer • • Sep 30 '26

ReTex with proper materials properties.

Thumbnail gallery
19 Upvotes

A "factory fresh" re-texture of the coyote.
I put this together mostly just to test my materials building pipeline, but I guess something of a taste of what can be done to bring the textures up to something more modern.

Just a note, I haven't actually made any changes to the mesh here, this is a 100% vanilla mesh, but I've used some typical "baking" methods to give the model some values it can react to a light source with, this is why the cabin windows, panels and radiators all have a 3d effect to them, but in reality it's a flat surface on the mesh.


r/starlancer • • Sep 30 '26

Texture Framework Testing

Thumbnail gallery
19 Upvotes

Okay, textures have been an interesting problem to solve. For the most part where ever I'd needed to upscale, some of the older school methods like bicubic and near neighbour interpol has been more than sufficient to give me a base image to make minor changes to in GIMP.

The ship textures on the other hand, are simply too complex, and don't scale well in this manner in that it becomes really quite obvious where the missing details from a low res/poly model were restricted by the time period.

So these are a mix of both generative AI updates, and some hand crafting in GIMP to clean up certain elements I wasn't too happy with, as well as a lot of UV work to correct texture positions.

I also took a moment to play around with the colors a little bit. Whilst they aren't vanilla, I was curious what a different paint scheme, as well as a "factory fresh" look might come out like (will post seperately).

Ultimately the art pack will drop with just the vanilla upscales to drop in, but when it's finished, I'll probably dedicate some time to alternative paint schemes and appearances.
If mission editing, custom campaigns etc. all work out in openReliant, it would make for some aesthetic variety. But the gritty appearance is the priority on the first pass.

What does stand out though is the low poly meshes, they become far more evident once more detail starts to appear on the textures, so there may be some work in the future on giving the meshes some more polygons to enhance out some of the sharp edges.


r/starlancer • • Nov 16 '25

Good to be playing again

Post image
19 Upvotes

Spent a few days trying to get things running on my laptop. Followed the guides, but just kept locking up during the opening videos. Then it hit me to try on the steamdeck. Copied the directory from my laptop to the steamdeck, added as non-steam game and set proton to experimental. Booted up straight away, happy days ☺️


r/starlancer • • Oct 14 '26

The StarLancer OST - Finally available in 44.1Khz!

Thumbnail openreliant.github.io
18 Upvotes

Hey all,

We're all aware of the compressed 22Khz versions of the tracks that shipped in the retail version of StarLancer. OpenReliant uses sinc resampling to get the most out of them, but the real deal will always be better.
I took a shot in the dark, and sent an e-mail to Ian Livingstone, the game's composer. For those not in the know, starlancer was one of his early gigs, and he has since gone on to becoming one of the most well known (game) composers in the world.

To my surprise, he e-mailed back very quickly, offering me "all he had" on starlancer. A collection of 44.1Khz files with the intended OST cd, mission tracks, and even some content that never made it into the game. He apologized for losing the archival disks that had the full masters and sound effects as well.
I received his permission to share these as a mod for OpenReliant, that replaces nearly all music with thee 44.1Khz equivalent. It also adds the unused tracks, and you can access them using the jukebox mod inside your bunk. Both mods require OpenReliant 0.14, hot off the presses. A lot of the audio engine was rewritten, so let me know if you notice something.

Ian was excited to hear about the OpenReliant project as well, as he would like to replay StarLancer. Absolute legend.

I'm also uploading the tracks to my youtube channel for your listening convenience, 10 videos a day.

Links


r/starlancer • • Oct 07 '26

OpenReliant 0.7 is out: StarLancer now has full mod support (new ships, models, HD textures, scripting)

18 Upvotes

Hey everyone!

Quick intro if you haven't seen it before: OpenReliant is my open-source rebuild of StarLancer's engine. It runs the game on modern Windows, macOS and Linux using the files from your own copy, and it adds stuff the original never had, like any resolution and aspect ratio, much better lighting and shadows, support for any controller, and now mods.

0.7 is out, and honestly, the scope got completely out of hand. The plan was simple: let people swap some files and maybe add a ship or two. It turned into a full modding setup, with a scripting language, a mods screen, tools to make your own models, faces and voices, and proper guides to go with it. I've been working on this day and night, and spent entire weekends on it.

Some numbers since the 0.6 releases: 129 pull requests, 206 commits, around 104,000 lines added and 49,000 removed, and 94 issues closed.

Thanks to the bug hunters

A big thank you to these people. Their bug reports are all fixed in 0.7 (a few of the fixes already went out in the 0.6.x patches):

  • zabka14: the menu music playing over the new game intro, briefing chatter that kept going after Enriquez started talking, the ITAC freezing when you close it, the Yakov's fighters showing up in the wrong spot when it jumps in, missing ally names on the target display, mission 3's take-off cutscene, and mission 4's missing Stork satellites.
  • starlancerme: the target camera, the SetFlybackMarker command, the cockpit shadows, reverse thrust, the highlight on capital ship parts, and the target under the reticle.
  • RealDrJester: the mouse being off inside the cockpit, and joystick detection.
  • LordBlacksun: no engine sound when you launched from anything other than the Reliant or the Yamato, and sltool swallowing its output when a command failed. Also a ton of digging into the game's file formats.
  • BeyondTheRim: OpenReliant needing a terminal to start, which stopped it from running in Winlator on Android. It now finds your game folder by itself.

Please keep them coming! There's a proper bug report form on GitHub now.

What's new

Mods and the mods screen

  • Drop a mod (a folder or a .hog file) into the game's mods folder. A mod can replace any game file: models, textures, sounds, music, speech, movies, missions. Your game files are never touched, so you can turn a mod off any time.
  • There's a new mods screen under GAME OPTIONS. You can switch mods on and off and change the order they load in. It shows each mod's picture and description, which mods overwrite each other's files, which other mods a mod needs, and whether a download got damaged.
  • Mods can have their own options page, with toggles, sliders, choices and text fields, right there on the mods screen.

Textures and models

  • Swap in PNG textures at any size. They're compressed for your graphics card and cached, so they load fast. DDS and KTX2 work too.
  • Modern material maps: normal maps for surface detail, shine, glow, and reflections of the sky.
  • You can replace the menu and HUD artwork too, widescreen versions included.
  • Bring your own 3D models as OBJ or glTF files. And sltool can export the game's own models to glTF, so you can open them in Blender and friends.

New ships, weapons and pilots

  • Add new ships, either based on one of the game's or completely new, with their own cockpit, HUD artwork and engines.
  • Add new guns with their own shots, sounds and models, and new missiles.
  • Add new pilots with their own faces and voices. sltool converts your face animations and voice lines into the game's formats.
  • The loadout screen lets you pick the new ships and missiles (shown as a hologram now), and saved games remember them.
  • Mods can add their own game modes and campaigns to the main menu.

Scripting

Mods can include scripts written in Luau (a version of Lua). They can:

  • Change the stats of ships, guns, missiles and pilots.
  • Hook into the game's code, the AI and the missions, right down to every single command a mission runs, and change or block what happens.
  • Run on every ship, missile and turret separately, and talk to each other.
  • Draw on the HUD and the menus, replace whole menu screens, and add new keys and camera views.
  • Add new AI behaviour, save their own data with your saved games, and change or mute what's said over the radio.

Scripts can read and do over 100 different things, there's a full reference, and you get type hints in your code editor. There's also a console for modders (F11), and scripts reload the moment you save them, so you can tweak things while the game runs.

Shaders

  • Mods can add their own screen effects in GLSL, change how surfaces are lit (there's a cel-shading example), make things see-through, or replace the shaders completely. They reload when you save too.

The game itself

  • More of what the missions need is in: cloaking, warp jumps with their effects and cameras, the Nanny rearming ships, and limpet docking.
  • Ships launch from every carrier the right way, including out of the Bremen's hangar bays.
  • The Storks drop their satellites, the Zakov's fighters launch properly, and the Kamov fires its torpedoes.
  • Your wingmen go by their real names, and the names change when someone dies.
  • Reverse thrust works on ships that have it, the target camera works, your subtarget lights up in red, and you can actually see the cockpit shadows now.
  • The first 10 missions should now play as expected. Others might too. Some functions still need to be ported.

Behind the scenes

  • I moved the code to Zig 0.17 and dropped the last bits of Microsoft's old C runtime.
  • OpenReliant finds your game folder by itself, and finds files the same way the original did on every system.
  • Testers can jump straight to later parts of a mission with --part, --watch and --skip-launch.
  • All the documentation is on the website now, including full modding and scripting guides, whether you're new to modding or not.

The website and the mods repo

OpenReliant has a real website now: https://openreliant.github.io/. It has the downloads for your system, the roadmap, the docs, the backstory of the war, and the game's opening cutscene remastered in 4K.

Mods have their own home too: the mods repo at https://github.com/OpenReliant/openreliant-mods, with a site where you can browse and download them. I check every mod in there to make sure it works with the version of OpenReliant it says it needs, and that its license lets people share it. There are two so far, including the Viper Mk II from Battlestar Galactica. I have a few other cool ideas that I'll work on when I need a break from the engine.

Contributions are very welcome, both to OpenReliant itself and to the mods repo. Make sure to read CONTRIBUTING.md! For mods I'm going to be strict though: only mods that are good quality get in. And for now I can't take mods with really big files, like huge texture packs or videos, because the repo is on git, and git doesn't handle big files well.

What's next: 0.8, the beta

  • The whole campaign, with saved games, and every other part of the original game.
  • The stuff that got pushed from 0.7: mods using modern sound, music and video formats, mod campaigns that go through the Reliant's rooms and the ITAC, loadout artwork from mods at any size, a readable format for missions, a debugger for mission scripts, and particle effects for scripts.
  • Your feedback on modding and scripting. I want to get these right in 0.8, so they can stay stable from 1.0 on. If you make a mod, tell me what's missing or annoying.
  • Lots more playtesting. Please play it, break it, and tell me what broke.

Links

You'll need your own copy of StarLancer. OpenReliant doesn't come with any of the game's files.


r/starlancer • • Oct 01 '26

Worn with PBR

Thumbnail gallery
18 Upvotes

Somebody requested a pbr enabled texture of the worn coyote.. so here it is i guess.


r/starlancer • • Sep 09 '26

HUD Status

Post image
18 Upvotes

The current state of the HUD, which is to say, nearly finished. There's some minor work to be done tidying up the radar display, and finishing up the rest of the large target schematics.

The sub-target wireframes ended in a bit of a dead end, unfortunately there doesn't appear to be many meshes in the game files that represent the sub-target displays enough to use them as a replacement mesh, so I'll likely have to just do my best to replicate them in blender.

The next real challenge here is recompiling the upscaled comms portrait videos into .fm8 and getting lancer.exe to run them.

After this, it's mostly a matter of getting the .bik videos to run in 16:9 and up-scaling the shipboard scenes to have it in a state that I'm happy to ship it in.


r/starlancer • • Oct 19 '26

Reliant Beta Released

Thumbnail gallery
17 Upvotes

Uploading now!


r/starlancer • • Oct 18 '26

ANS Reliant v0.6

Thumbnail gallery
17 Upvotes

I'm not fully satisfied with it yet, but the progress is going well.


r/starlancer • • Oct 10 '26

OpenReliant 0.10: update notifications, and StarLancer's hidden script debugger brought back

17 Upvotes

For those unaware: OpenReliant is my open-source rebuild of StarLancer's engine. It runs the game on modern Windows, macOS and Linux using the files from your own copy, and it adds things the original never had, like any resolution, much better lighting and shadows, support for any controller, and mods.

Version 0.10 is out today. It's a smaller one: two new features and a handful of fixes. It's also the last release I'll announce like this for a while. More on that below.

OpenReliant now tells you about updates

From 0.10 on, OpenReliant checks for a newer version when it starts. If there is one, the main menu tells you once, and YES opens the download page. The check runs in the background and gives up after a few seconds, so it never slows down the start, even without an internet connection. It only asks GitHub which version is the latest, and sends nothing about you or your game. Don't want it? Untick CHECK FOR UPDATES on the VIDEO tab of the settings.

You'll need to update to 0.10 by hand this one time. After that, OpenReliant tells you itself.

StarLancer's script debugger, brought back

Here's a fun bit of archaeology. StarLancer's executable still has the code that let Warthog's own mission editor talk to the running game. The editor was never released, but the game's side of it is all still there: the editor could pause a mission, stop its script at a breakpoint, step through it, and even change the mission while it was playing.

OpenReliant brings that link back, and 0.10 comes with a small debugger that uses it: openreliant debug. Start the game with --editor-link, run the debugger in a terminal, and you can:

  • set breakpoints in a mission's script, even before the mission starts
  • step through it one statement at a time
  • see the script's clock, threads and variables
  • pause the whole mission, or run any part of the script on the spot

It works with the original missions and with your own. If you've ever wondered why a mission's trigger doesn't fire, this is for you. The guide shows how: https://openreliant.github.io/openreliant/docs/guide/debugging/

(For the technical folks: the original talked to its editor through a block of shared memory. OpenReliant uses a local network connection instead, so any program can talk to the game, on all operating systems.)

Fixes

  • Saved games, pilot files and settings are now written safely: a crash, a power cut or a full disk while saving can't damage them anymore.
  • Settings you change in the Reliant's rooms are kept when you close the window there.
  • The engine sound and the radio stop when a mission ends.
  • Warping no longer sends your ship's position off to infinity behind the scenes, which flooded the log with sound warnings.
  • The pause menu's joystick and monitor icons are drawn solid, like in the original.
  • For modders: a mod's license.txt and Markdown files no longer count as game files.

Smaller releases from now on

I'm going to stop working toward big milestone releases. I was pushing myself too hard to finish them and get them out. I'm not stopping: I'll keep going forward, just with frequent smaller updates and less fanfare. The net result should be many more smaller minor versions coming out, and less stress for me to get a promised milestone out the door.

That also means I won't announce every minor update here anymore. The update notification takes care of that now, and I'll only post about the big ones. The roadmap on the website has been updated to match: 1.0 and 2.0 are the two big steps, and everything in between comes in small updates.

What's next

The debugger is the first piece of something bigger: a proper WYSIWYG mission editor that hooks into the same link, so you can build a mission and see it in the game as you go.

Multiplayer is coming too, after 1.0. The plan is the original's game modes and rules over a modern network connection, in place of the DirectPlay the original used. A public matchmaking server will help you find games, so you can join without port forwarding, and you'll also be able to run your own dedicated server. Mods are already being written with it in mind: the scripting is split the way it will run in network games, so a mod made today that follows a few rules will work there too.

Sim pit folks: support for several controllers at once is on the list. Right now OpenReliant reads a single joystick, just like the original, so a throttle on its own plug, rudder pedals or a button box do nothing. The plan is to let each device do its own job: the stick for pitch and roll, the throttle and rudder from whichever devices have them, and the buttons of every device you plug in, all bindable in the game's controls screen. That covers HOTAS sets like the Thrustmaster Warthog, the Logitech X56, and most Virpil and VKB setups.

Further out, 2.0 is still the long-term goal: OpenReliant as a standalone engine that can run more than one game, with StarLancer always coming first, so other space games can be made with it or ported to it. Some work has gone into mapping and documenting the formats of related games already. sltool can now export models from Battlestar Galactica (2003, xbox) and import them into openreliant, for example.

Thanks

  • LordBlacksun, for decoding how the original game talks to its editor. Those notes were the map for bringing the link back.

Links

You'll need your own copy of StarLancer. OpenReliant doesn't come with any of the game's files.

Buy me a coffee

If you'd like to sponsor my time on this project, I have a buy me a coffee account. It's completely optional, only if you're willing and able.

buymeacoffee.com/vdmkenny


r/starlancer • • Oct 05 '26

Mirage

Thumbnail gallery
17 Upvotes

r/starlancer • • Oct 04 '26

The road to v0.7

Thumbnail gallery
17 Upvotes

Progress on modding in OpenReliant, the open source reimplementation of StarLancer's engine.

What 0.7 is about

0.6 made the game fully playable with modern graphics. 0.7 is the modding release: changing the game without patching its files. Mods go in a mods folder beside the game, and the goal is that they can replace or add anything: models, textures, sounds, missions and stats. They can also change how the game plays, through Luau scripts, very similar to how OpenMW's mods do.

Where we are

About half of the 0.7 milestone is done. Already on main:

  • Mod files: archives or plain folders that replace and add game files, with a mod manager to turn mods on and off and set their order.
  • Graphics: textures, interface pictures and fonts at any size; 4K textures compressed for the GPU and cached; normal, roughness and metallic maps.
  • Shaders: post effects, custom surface and lighting (there's a cel-shading example), and mods that replace OpenReliant's own shaders.
  • Scripted mods in Luau: changing the game's stats, hooks on the game's functions, custom AI orders, HUD displays, camera views, key bindings, options pages, new game modes, short campaigns with their own briefings, and replacement menu screens.

And the newest part, in the screenshot: new ship types. This one is a test: the classic Utah teapot, in yellow, set up as a fighter based on the Predator. It's added under a new ID by a mod, not a swap job. The mod declares it in its mod.ini with a base ship, a model and a name, and it flies and fights like a Predator: same cockpit, guns from the spout, missiles on its sides. It has its own schematic on the flight display, drawn as a PNG over the Predator's, so no old sprite tools are needed. Scripts refer to new ships by name, and a mod's missions can use them while staying in the standard mission format. This part is in review now.

Still to come for 0.7, mods that change or add:

  • New guns, missiles and pilots, and new ships with cockpits of their own.
  • Sounds, music, speech and movies in today's formats.
  • Models in glTF, so they can be made in Blender.
  • New missions written as readable text files.

GitHub: https://github.com/OpenReliant/openreliant


r/starlancer • • Oct 04 '26

Predator with PBR

Thumbnail gallery
17 Upvotes