[CaptJosh]

I was playing the FS Port because I'm kinda going through all the campaigns I have with a single pilot seeing just how big a kill count I can rack up and maybe some promotions and such, when I discovered that my Valk had shields in the mission and I know damn well it shouldn't. Playing with an FS2 Open SSE2 build from Nov. 19th.

[Jeff Vader]

Uh... are you allowed to choose a Valk in that mission? I know you had to use it in the McCarthy mission previously, but I have this feeling you could only use an Apollo on this particular mission.

In addition, you might have ****ed up your pilot, if you've played carelessly through all the mods you've played.

Furthermore, does this happen always or did it occur only now? Testing it with the Mission Simulator and/or restarting the campaign wouldn't probably hurt.

[CaptJosh]

I haven't started any campaigns without completing the one I was already on. So I'd hardly say I've been careless. As for that mission, yes, you could always select to fly a Valk. In fact, two were available to choose, even in retail, so you could split your wing between Apollos and Valks.

EDIT: Tested with a fresh pilot. Behavior is the same. The Valk has shields in this mission. Tested with Apollo. It has no shields. This is not a pilot file error.

[CaptJosh]

Sorry for the double post. However, I have additional data. The next mission after that, the Valk also has shields. This is very strange, as I don't recall this behavior on older builds. It would seem that for some reason, the campaign is set up incorrectly and gives the Valkyrie shielding from "Out of the Darkness, Into the Night" onward.

EDIT: The error does not appear in the first mission from the Bastion. It's possibly a mission error since in the two prior missions, Valks are NOT the default fighter.

[Goober5000]

I believe this is a SCP bug -- if you change your fighter from the default, you suddenly get shields.  Try it with the latest nightly build.

[CaptJosh]

I did that. The error remains. Also ran into an odd bug where it insisted I had failed a mission five times when I'd only played it once. When I told to it skip, the next mission was a red alert and it was broken and badly. I had a HUD, but it was mostly out of place, and I couldn't move unless I changed my POV, at which point I couldn't see to fight. Very strange. But when I went back and replayed the previous mission through to completion, the odd behavior stopped.

[Galemp]

I know about the shield issue. This must be a bug, though, as the player ships definitely have "no shields" set in their flags.

[CaptJosh]

So how does that work for later in the game when shields get acquired?

[Galemp]

Should be fine.

[CaptJosh]

No, what I mean is how do the ships with no shields flagged get the shields in the first place. Do they get replaced with new entries later in the game, or...?

[Stormkeeper]

The ships with the shields flag probably have a table name like Valk#Shields or something, seeing as how anything after the '#' will be invisible in FS.

[Galemp]

No, actually, it's set on a per-mission, per-ship basis using the "No shields" property. This must not be carrying over when the ship class is changed.

It may have something to do with this bug that I submitted while testing SWTC. Can we verify this still occurs in the nightly 3.6.10 builds?

[Goober5000]

Ugh.  That has to be it.  Reopening the bug.

[chief1983]

Oops, just noticed this post too.  Consider this fixed as of rev 5007, should be in the next nightly build and the next Wanderer build I'm posting.