[MOD] Unoffical Patch : V1.3.19 : 2025-05-10

[Cycrow]

Looks like the script is using the wrong value when trying to apply the loadout, this should be fixed in the next patch

[fireanddream]

Thanks Cycrow, good to know.

May I make a suggestion regarding carrier repair/replace at HQ, if you are in the process of fixing/improving it for the patch or GUILDS.

Can we have "use HQ = yes/no" instead of "use shipyard = yes/no". At this point, credits is a much cheaper resource than the carrier clogging up HQ production/repair queue. Producing M3s is the one of the least efficient thing the HQ can do; tt also drains resources we stock up for things like TOAs.

[fireanddream]

Hi Cycrow, the fusion beam cannon forge in Saturn gamma is owned by ATF, is this intended? The one in Jupiter gamma is normal.

I found this when I aggro'ed the station but found no option to hack it in diplomacy menu.

[Syacelion]

Hi Cycrow,
first off, huge fan of all the amazing work you've put in! Kudos and thanks for that!

I've finally gotten around to playing X3:FL, absolutely loving it, but I keep having this one recurring bug where the game crashes to desktop usually just when combat gets really exciting, when I'm a good bit of the way into taking on Xenon K or Q or several M6 with turrets or again just now a Darkspace Aegir in my Hyperion, at some point I will fly by the enemy ship and past it and very shortly after clearing it, looking away from the enemy, presumably just as its turrets rotate to catch up (?), the game freezes a brief moment and then just crashes to desktop.

The siituation is always similar, akin to what was described by user delray just above my post here
viewtopic.php?p=5275295#p5275295

This time I've managed to save the game shortly before it happened, reloaded the same save, and 5 times out of 8 attempts I have a similar crash to desktop, and managed to record a brief video trying to replicate it (hence piloting badly and not destroying the enemy, trying to replicate the crash on purpose, don't judge my flying! )
Video
https://drive.google.com/file/d/1CS295R ... drive_link
Savegame and crash dumps
https://drive.google.com/drive/folders/ ... sp=sharing

I had this issue in X3:FL latest Steam version vanilla a few times, and since patching the game to the latest unofficial patch it happens quite a lot (but then I wasn't fighting as much in that weight class before patching, but it happened then too).
I have completely reinstalled the game from scratch, (and X3:TC and X3:AP, steam folders removed and downloaded and verified the games anew, to make sure nothing was modified.
I don't remember having this issue in X3:AP or X3:TC, on this same PC. Graphics settings, playing in fullscreen or borderless windowed, turning various settings on or off, ignoring settings and playing with standard settings, none of those seem to influence it, seems to me to be a bug in the game (or in my game (despite reinstalling)) to do with turrets on capital ships and doing close flybies in my Hyperion, with or without turbo booster?
I'm 90% certain it happened twice in vanilla, just after getting the Hub, while I was piloting a Nemesis, trying to capture a Hyperion. And it's also happened once, just now, out of combat, while just flying through a sector at full speed, rather closely past a Teladi Phoenix that was turning hard (its) right on my left, just as its rear left my field of view. (same error - The exception "Unknown exception" (0xc0000095) was caused at address 0023:001c9e34 )
Almost all if not all of my crashes involved a Hyperion, which is the ship I pilot almost all the time, with my own turrets set to missile defence only. Trying to replicate the crash from that same savegame in a Nova or TP Natter (Ocelot?) didn't crash but then I got fewer passes on those as by the time I'd swapped, other ships were engaging the damaged enemy so I didn't get too much experimentation in trying to replicate.

Would you (or anyone else here) have any ideas what else to try to fix these recurring crashes?

The X3Crash.log just says a crash event occurred in X3FL.exe "The exception "Unknown exception" (0xc0000095) was caused at address 0023:001c9e34" (same address each time)

Thanks for any ideas on what to try, I really really want to keep enjoying this amazing version of the game!

[updated]
Feels like those situations occur more often since I got several more engine tuning upgrades on my Hyperion, or maybe that just changes my piloting style to doing more dogfighting swoops. A dozen more crashes today, almost every time when I'm moving and having a capital ship fall out of sight behind me, mostly in combat, but sometimes just flying past a sector patrol too.

[Cycrow]

I will take a look at the save and see if I can find anything

[Syacelion]

I will take a look at the save and see if I can find anything

Very highly appreciated, thank you!
I keep having so many crashes I'm on the verge of giving up. I tried reinstalling X3:TC, X3:AP and X3:FL, in that order, from scratch again, trying to make sure everything was fresh, except my latest savegame.
https://drive.google.com/drive/folders/ ... sp=sharing
In this savegame, dodging and weaving between two Xenon Q, my game crashes out almost without fail in the time it takes me to take down one of them. And it's always just after I've turned my back on one or both of them that the game freezes for a moment and then crashes. Always the same error in the log.

[update]
Confirmed, I just got the same crash when swooping excessively around a Q in an M6 Nemesis, so it's not just the Hyperion. But still the same situation, flying close by and across and out the other side, shortly after the enemy is behind me, the same crash, flying past an enemy and turning away from or back towards them while they're outside my field of view.
Here the log and dmp/mdmp, if those are useful
https://drive.google.com/drive/folders/ ... sp=sharing

[update]
20+ crashes in this situation, can definitely replicate on demand even without meaning to!
https://drive.google.com/drive/folders/ ... drive_link

[Cycrow]

I've tried both the save games, but ive been unable to make the game crash, not sure if im not doing it right, or if maybe there is something specific to your pc.

i've created an update just to test some fixes
http://xpluginmanager.co.uk/x3_test_dev.zip

just unzip it to the game directory, this will put a file called x3story_dev.obj in the addon2/L folder.

then when you run the game, add the commandline arguments "-load x3story_dev" and see if it changes anything.
alternatively you could rename the file to x3story.obj and it will be loaded automatically.

DO NOT save your game while running this file, it will make the save games incompatible with any future patches. So make sure to delete the file again before you start playing again

[Syacelion]

Thank you VERY, very much for trying!

With the test_dev update running, using Savegame x09 from my last updated google link, I still get my game to crash every 4th or 5th pass I take at that Xenon K. Whether coming at it from the front or the side, above or below, I shoot at it until its flak starts hitting me then accelerate past it out of flak range (sometimes with turbobooster sometimes without) and bank more or less hard to come back at it, at variable ranges of 1500 to 4000m, and either shortly after putting the enemy behind me while already turning, or just as I turn the ship back towards (but each time with the enemy always out of sight), the game crashes, every so many-eth time, as I hit a certain relative position to each other that may or may not involve turret angles.
Same crash log file, I don't see any additional debug information besides "The exception "Unknown exception" (0xc0000095) was caused at address 0023:00ae9e34" and the .mdmp file that I cannot make sense of.
Sometimes I manage to somehow avoid getting into the crash position and keep swooping around and chewing it apart but the longer the fight goes on the surer I am to crash eventually, the only real way out of that particular fight for me is to basically savescum, save every 30 seconds and if I crash after that, try to remember what I last did and fly at it from another angle. But I can't narrow it down further than that it seems to involve some combination of relative positions and angles, and probably turrets on ships M6 or bigger, the bigger and more turrets the more frequent it feels like. (although that may just be extended combat duration)
After half a dozen crashes, some quite quick some taking a minute or four, I tried using your debug menu to overcharge my engine and maybe flying at 700m/s changes my behaviour or the relative angles and positions enough that it seemed to happen less, but the game still crashed the same way in a similar situation after a while, so that may be purely anecdotal.
I think I have eliminated the possibility of a corrupt game file on my end? Does that make it come down to maybe some combination of gpu and drivers or the like? It only happens in X3FL for me though, not in X3AP or X3TC or any other game I've played a lot on this 7-year-old pc.
I've sent a message to Forum user Delray who seemed to have the same issue, 2 years ago, but they may not be seeing that message for some time. Short of comparing specs with that person I wouldn't know what else to try to find the cause, if you can't replicate it.

Not sure what to do next. This crash happens a LOT when I play the game normally. I've managed to go most of a game session with only a handful crashes by basically staying away from combat against anything larger than a Xenon P/PX and focussing on trade and stations almost exclusively, but playing the game almost completely without dogfights is definitely a lot less enjoyable, and I still get the occasional crash during exploration or transport missions just by flying past a random Split Panther or other sector patrol that happens to be along my route.

[UPDATE]
I've borrowed a laptop which had never run that game before, installed X3AP and then X3FL via Steam (which transferred at least some of the files via my network from my PC so that complicates it), updated the game from vanilla 1.3 to 1.3.18 with the plugin manager to be able to load my savegame, loaded my above savegame 9, fought the Xenon K for a few minutes until I bumped into it, reloaded, fought it again for 2 minutes and got the usual crash at some point when flying away from the enemy and turning.
Same crash, log shows error message of unknown exception 0xc0000095 at addres 0023:00ff9e34 . I don't suppose the small change of address is of any help in identifying something that may be triggering it?
Going to completely purge the game and any associated directories and download afresh from Steam, X3TC + X3AP + X3FL + Pluginmanager + unofficial patch 1.3.18 in that order, with the network machine unavailable, just in case it's copied some hypothetical corrupt game file that verify game files doesn't catch.

[UPDATE 2]
I've completely reinstalled the games from scratch on both machines, fresh Steam download, no peer-to-peer transfer of game files.
I've got a savegame from a backup from 2 weeks ago where I had just taken over the Hub and boarded my Hyperion with the Nemesis from the plot. This is 1.3 vanilla X3FL with a 1.3 vanilla savegame.
- On my main rig, after a fresh install, I jump into Xenon sector 101 and fly around between 2 K, 1 J, a Q, and a small fleet, dodging and weaving like crazy for several minutes until I get the familiar crash. It took perhaps longer than I expected it to happen with that many capital ships rotating in and out of sight, but by the time I've taken out a bunch of Ls and a PX and am halfway through a Q, I get the familiar game crash just as I fly past it for the 6th time.
So it's definitely not just in 1.3.18. This time I couldn't replicate it in the Nemesis because it's too frail and sluggish to survive that Xenon fleet long enough for statistically valid data.
- On the laptop, fresh install number 2 after a second complete purge, 1.3 vanilla, same old vanilla savegame transferred over just after getting the Hub, I jump into Xenon sector 101 and dodge and weave between the same Xenon fleet. On the first attempt, I keep going long enough to get shot down after several minutes. On the second attempt, I dodge and weave for 45 seconds until I get the exact same familiar random crash.

So completely different machine (Windows 10 PC with a GeForce GTX + Windows 11 laptop with an Intel graphics chip), both completely fresh install from the internet via Steam, 1.3 , not even applied the unofficial patches this time which both crashed on both before; I still get the same crash, only shared file between them is the 1.3 vanilla savegame with just enough game time to get my hands on a Hyperion, but I've had the same crash with other ships too when flying past random capital ships in both 1.3 and 1.3.18.

I've also tried different language versions, just in case, and get the same outcome. I don't get the same crash in X3:TC or X3:AP, though I've only tried for an hour each. But I've now really taken to all the awesome improvements in X3:FL and don't want to go back to the others anymore.

If if hate myself enough I may reinstall again tomorrow, start a fresh game on the borrowed laptop and rush through the plot to get the M6 and take that to a Xenon sector and try to stay alive long enough to replicate, but I'm pretty confident I'll manage to replicate the same crash eventually and then have it at increasing frequency again the more I play and the faster my ships and the bigger my opponents get.

Kind of at my wit's end what else to investigate at this point, spent my whole week off trying to figure this out.

[Syacelion]

I've tried both the save games, but ive been unable to make the game crash, not sure if im not doing it right, or if maybe there is something specific to your pc.

i've created an update just to test some fixes
http://xpluginmanager.co.uk/x3_test_dev.zip

just unzip it to the game directory, this will put a file called x3story_dev.obj in the addon2/L folder.

then when you run the game, add the commandline arguments "-load x3story_dev" and see if it changes anything.
alternatively you could rename the file to x3story.obj and it will be loaded automatically.

DO NOT save your game while running this file, it will make the save games incompatible with any future patches. So make sure to delete the file again before you start playing again

Hey, so I removed the file, uninstalled the game, deleted the game folders, downloaded a fresh copy of X3TC then X3AP then X3FL from Steam onto a different hard drive, installed the plugin manager, installed patch 1.3.18, and any and all of my previous savegames are now listed as possibly corrupt and unable to be loaded. When I try to start a new campaign, I get a message that my game is modified, and that "x3files verification failed - file: addon2\L\x3story.obj" even though there's no such file anymore nor any such folder; and how does a supposedly clean fresh install remember that one?
I've since removed the command line launch parameter from Steam game settings, so now my savegames load again (and combat still crashes the same way in several that I've tried), but I still get the modified message and that your temporary x3story.obj from two reinstalls ago failed verification, when loading a save or when starting a new game.
Where else besides the Steam folders and the savegame folder are there files I need to purge to really do a clean reinstall on the same windows PC?
Or does the savegame remember having been loaded with that temporary addon once, despite NOT having been saved in that version? I'm confused...

[Syacelion]

I've tried both the save games, but ive been unable to make the game crash, not sure if im not doing it right, or if maybe there is something specific to your pc.

When you were trying to replicate my crash, did you have any cheats turned on?
It's finally occurred to me to install your cheat package, to give myself a testing sandbox with a similar ship and equipment in a completely new game. And after fiddling with that for a good while, to experiment with turning collision off for my ship.
If I load any one of my saves, turn collision off, jump into Xenon sector 101 and fly circles around 4 capital ships for 25 minutes, nothing happens! I reload, turn off collision, fly circles around the same Xenon ships for 10 minutes. Once or twice the game very briefly stuttered in the same circumstance, but no crash. I reload the same savegame, this time I don't turn on that cheat, I jump into the same sector, and my game crashes within a minute and a half. Reload, repeat, crash after 3 minutes; reload, crash after 20 seconds.

I guess maybe I can try that for a bit next longer play session, play as I have been, then when the game crashes, reload, turn collision off for a while until I'm out of that situation, then resume, see if that can cut the amount of time I spend restarting the game and reloading saves!

[update]
Nope, reloading my current game of 120 hours in and turning collision off still makes me crash in the Xenon sector. Dang!

[alexalsp]

DO NOT save your game while running this file, it will make the save games incompatible with any future patches. So make sure to delete the file again before you start playing again

It's important to know how you run the game. Did you install NoSteam.exe after downloading the game from Steam?
Did you install patch 1.3.18 and run the game with NoSteam.exe or did you download the game, install 1.3.18 and run the game with Steam?

[Syacelion]

I did not save any game with that test dev patch running.
But I had edited the command line in Steam to load the file when I tested if it made a difference and I produced the crashes at a similar frequency, so that's where the game looking for the file after a fresh install came from, I booted up the fresh game from Steam and it had kept that command line parameter. Since remedied, the error was it looking for a non-existant file on startup, showing up as a message once I entered a game.

I am not using the no-steam .exe.

I uninstall the games in reverse sequence, delete the game folder. I install X3:TC from scratch via Steam. I fire it up, start a new game, fly around a bit, exit. I install X3:AP via Steam, fire it up, fly around a bit. I install X3:FL from Steam, fire it up to make sure all working fine.
And then on successive iterations, I have
- (copied into my save folder and) loaded a vanilla 1.3 savegame from a two-week-old backup, and reproduced the crash in 1.3 vanilla
- installed the plugin manager and patched to 1.3.18, reloaded a week-old 1.3.18 savegame, and reproduced the crash
- reinstalled, patched straight to 1.3.18, loaded a different 1.3.18 savegame, reproduced the crash.
Installed the game on a different machine, same sequence, started it up in 1.3, loaded the same vanilla 1.3 savegame, and reproduced the crash.
Patched to 1.3.18, loaded the same 1.3.18 savegames each and reproduced the crash.

I have during several reinstalls loaded up old savegames in X3:TC and X3:AP and put myself into as closely equivalent positions as possible and flowing around for a solid 15 minutes each doing loops around Xenon capital ships, not crashing.

In any version of X3:FL, and apparently on two machines with different windows versions and different graphics systems, I sooner or later, and somehow with increasing frequency, end up with this result:
https://drive.google.com/file/d/1l48qSD ... sp=sharing
1.5 second freeze while turning away from or towards a capital ship out of my field of view, usually in combat but also occasionally while not, and immediate crash to desktop.
Error log showing "The exception "Unknown exception" (0xc0000095) was caused at address 0023:00bb9e34".
Most often in a Hyperion because it's my favourite allrounder, but also in a Split TP+ or M6 Nemesis, but also in the M5 Discoverer the plot starts out with.

[alexalsp]

1) Install a clean game from Steam
2) Copy the game to another directory or disk
2) Download Nosteam.exe
https://www.egosoft.com/download/x3fl/b ... wnload=607
3) Copy it to the game folder
4) Install Unofficial patch
5) Run the game with Nosteam.exe, not through Steam.

Start a new game. as all your save files will no longer work.

[Bandenere]

Sorry, i jump in the discussion since it happens that i just put the non steam exe on an already 1.3.18 patched game...is that a problem? I don't have to reload any old saves i will start new games....but 1.3.18 was in place when i put non steam exe in game folder. Problem in sight? I played yesterday and all was working fine.

[Syacelion]

1) Install a clean game from Steam
2) Copy the game to another directory or disk
2) Download Nosteam.exe
https://www.egosoft.com/download/x3fl/b ... wnload=607
3) Copy it to the game folder
4) Install Unofficial patch
5) Run the game with Nosteam.exe, not through Steam.

Start a new game. as all your save files will no longer work.

Done all that, properly uninstalled everything including the plugin manager, deleted the folders, then installed what I thought was a clean copy from Steam, copied it all to a new drive, copied in the nosteam.exe, installed plugin manager, installed unofficial patch, started the x3fl.exe (from the nosteam download) in that new folder, started a new game, still got the message that my game is modified but also that "x3files verification failed - fire: addon2\L\x3story.obj" and I cannot for the life of me figure out where that comes from by now.

Also played a bit as a new game start Paranid, upgraded my Hyperion, went into a Xenon sector to get into a proper dogfight, crashed within a minute.

Stumped as to what I'm doing wrong by now.

- Also no idea why vanilla Steam savegames wouldn't work after nosteam?

[Tharrg]

You could try

1) Unistall X3Fl, X3AP and X3TC.
2) Delete the X3TC directory in Steam. For example, "F:\SteamLibrary\steamapps\common\X3 Terran Conflict".
3) Install X3TC, X3AP and X3FL.
4) Install whatever mods you want.
5) Run the game to check it works.
6) Copy the "...\steamapps\common\X3" Terran Conflict" directory to another location say Z:\My New X3FL directory.
7) Delete or move the "Z:\My New X3FL directory\X3FL.exe" file.
Copy the no-steam X3FL.exe file to "Z:\My New X3FL directory\X3FL.exe"
9) Confirm that the game runs OK from "Z:\My New X3FL directory\X3FL.exe".

Kind of what I did.

[Syacelion]

Done that. Step by step. Several times. On two machines. Absolutely no difference to my game crashing issue.

[alexalsp]

On Win 11, I've seen reports on various forums that a number of games do not work properly, on win 10, everything is normal.

But if the problem was massive, then for a long time of existence of 1.3.18 forum would be red.

Another option, I don't take a computer with win11, but win10.

Try different versions of video drivers from the latest to a couple of versions down.

Also try installing the libraries

Microsoft Visual C++
Microsoft .NET
and DirecX 9.

If it doesn't help, then it's probably something very special, as the author said....
It is possible that something really is wrong with the xenon model, if the problem is on one model, but again, there would be many messages about this....

Give me a save file from the last installations with nostem before the crash and how to reproduce it again, I can try it myself, who knows...

[Terraformer33]

Localization Uranus beta - the southern gate is located in the eastern

[Terraformer33]

Unfocussed jump - don't work