[CuBes]

It seems that any time I kill Isis, Vac4, Satis, or Ma'at ships, my info becomes corrupted. I can't enter the barracks or view kills, or else the game crashes. I'm running FS2 retail V.1.20. What is this bug, and how can I fix it?

[karajorma]

This is a new one on me. Does it happen with different pilots or are you dragging out a backup of the same pilot?

Any reason you can't run FS2_Open instead?

[Jeff Vader]

Any reason you can't run FS2_Open instead?

He's sceptical. As I was a year ago. I again advise you, CuBes, to give FSO a try. But with your rig, I'd say only get the FSO executables and the Launcher. And maybe FSPort. Leave the MediaVPs alone, since they'd tear your graphics card apart.

[CuBes]

It happens with the same pilot and backups, but I encountered it with a different pilot on a different install not long ago.

About FSO, I am making a medal guide for FS2 so I want to use the original version of the game in order to use all the glitches in it, or to avoid any.

[CuBes]

Are there any known bugs that corrupt your pilot data in this manner?

[BlueFlames]

I don't know that it's the same bug, but I had a problem with pilot files being corrupted in retail FS2 to much the same effect several years back.  Since I hardly ever used the barracks anyway (selecting pilots on startup and viewing statistics at the end of each mission), I never bothered tracking down the cause or a proper solution.  When I switched computers, I did a fresh installation and started new profiles and haven't had any trouble in the intervening two years.

[CuBes]

BlueFlames says,

I did a fresh installation and started new profiles and haven't had any trouble in the intervening two years.

Did you switch FS2 versions, or install FSO?

[BlueFlames]

I have retail FS2 and FSO installed in parallel right now, but I continue to use retail FS2 primarily.

[CuBes]

I'm confused. Maybe FSO fixes the problem...

 In any case, I'll install that later. I need to finish this guide up. It only includes the main campaign.

[FUBAR-BDHR]

There is a bug in retail that causes this.  While the pilot file can record all the kill types the game can't handle much more than the ones that are actually used in the main campaign. 

[CuBes]

Damn, I thought that might be it. Are there any fixes (FSO or otherwise)?

[Jeff Vader]

Speaking of which, purely as a friendly notification, I'd recommend you applied url tags on your signature to make it look oh so much prettier. Something along the lines of

Code: [Select]

My guides at GameFAQs
[url=http://www.gamefaqs.com/computer/doswin/file/197099/20864]Descent FreeSpace - The Great War Medals FAQ[/url]
[url=http://www.gamefaqs.com/computer/doswin/file/566302/49586]FreeSpace: Silent Threat Rank and Kills Guide[/url]
FS2 Guide in progress.


[Black Wolf]

It seems that any time I kill Isis, Vac4, Satis, or Ma'at ships, my info becomes corrupted. I can't enter the barracks or view kills, or else the game crashes. I'm running FS2 retail V.1.20. What is this bug, and how can I fix it?

It's not a bug... It's a Feature! have strong morals, and oppose your murder of Vasudan civillians. Join the NTF if you want to get away with stuff like that.

[FUBAR-BDHR]

Are you saying that blowing up all those escape pods in VA2 makes me a bad person?   

[CuBes]

If its morals you are concerned about, then my crimes of high treason would be of more importance to you, or more to the point, how I got away with it 

As I hinted at before, I look for ways to take advantage of bugs without consequence to myself. I discovered the bug addressed in the topic by destroying said ships in the campaign, which apparently is not supported by the game. I need to know these sort of things so that when I write my guide, I can help others avoid the unfortunate event of losing all info.