[Narvi]

Okay, I was playing FS2_open 3.6.9, the main campaign with mediavps, and I finally reached "The King's Gambit".

Unfortunately, there seems to be some problems with my loadout. The Artemis bomber I receive comes with rockeyes and tempests, instead of cyclops, and the cyclops are not selectable in the weapon choices either. I think there's been some corruption because of the mods I installed, since a third party bomber (the Artemis D.H) is present in the fighter options. Is there any way to fix this via simple editting, or is that campaign a write-off?

[FUBAR-BDHR]

Pilot file corruption most likely.  Switching from one mod to another with the same pilot will cause this.  Best to create a separate pilot for each mod. 

If you dig there may be a campaign file that will start you off at that mission.  Several people have had the problem. 

[Jeff Vader]

a third party bomber (the Artemis D.H) is present in the fighter options.

That is actually a fully retail bomber. If I'm not completely mistaken, you will be allowed access to it if you play through the first SOC loop. Though I'm not sure. But it still is a retail ship.

Otherwise, yes. It would sound like a pilot corruption. Which gives me the idea to start finding and collecting these modified campaign files for easier distribution in these situations.

[karajorma]

I have a small set on my website. I just don't have the time to go through and make them cover every single mission in the main FS2 campaign.

King's Gambit however is a frequent complaint and I do have one for that mission.

http://homepage.ntlworld.com/karajorma/FAQ/Downloads/CampaignRestarts/SM2-04-FromTheKing%27sGambit.zip

To use this.

1) Go to the campaign room and reset the campaign to start it again. Quit FS2.
2) Extract this file to your FS2\Data\Missions folder.
3) Go to the campaign room a second time and restart again.
4) Play the game
5) Once the game is complete go to FS2\Data\Missions and delete Freespace2.fc2 or you'll never be able to play the first missions again.

[Narvi]

My thanks for the file, but there is no missions folder in FS2/Data.

Also, my tech room is acting a bit weird. No corvettes are present, and the weapons list is incomplete.

[Jeff Vader]

there is no missions folder in FS2/Data.

Screenshot or it didn't happen. Or just create the folder yourself.

Hmm. Do this: select a debug build with the Launcher and run it until you get to the main hall. Then quit, find a file called fs2_open.log from \freespace2\data and post it here as an attachment.

[Narvi]

Perhaps my installation is more than a wee bit corrupt. I inherited (and had to fix) my brother's slipshod installation, so I suppose it's possible.



[attachment stolen by Slimey Goober]

[Jeff Vader]

Then it would seem that he's been removing some retail folders under \freespace2\data. Not that those folders would or even should contain anything, but they are a good reference when one wants to do even the tiniest bit of modding.

There doesn't seem to be anything wrong with \freespace2\ and \mediavps\ in terms of the .vps that are in those folders. But,

Code: [Select]

-img2ddsremove this command-line option (the Launcher, the Features tab, untick Compress non-compressed images under Game Speed).

Code: [Select]

Intel 945GMEww. You've been doing okay with an Intel GPU? Usually they are a metaphorical pain in the arse with FreeSpace.

But the conclusion remains. Your pilot file has been corrupted and restarting the campaign is the only option. But if you follow kara's instructions, you can avoid playing the entire campaign again.

[Narvi]

The performance isn't as good as I'd like with the Intel GPU, but it basically works. I wonder what the deal with the tech room is though.

My thanks for the help. 

Does that file prevent restarting the campaign, btw? Which is why you told me to delete it?

[Jeff Vader]

Does that file prevent restarting the campaign, btw? Which is why you told me to delete it?

It's all about the order in which the game engine reads data. It will read \freespace2\data before the .vp files in \freespace2\. That's why if you have the modified campaign file in \freespace2\data\missions, it will notice it, use it and ignore the one in Root_fs2.vp. Now, in this modified campaign file the campaign begins from The King's Gambit and continues on from there. The point is that once you've played through the campaign, you should move the file away from \freespace2\data\missions. Otherwise it will always be read and if you try to restart the main FS2 campaign, you'll still start from The King's Gambit and you'll miss all the missions before it.