View Issue Details

IDProjectCategoryView StatusLast Update
0001294FSSCP---------public2007-02-22 00:15
ReporterGhaleon4 Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionno change required 
Product Version3.6.9 
Summary0001294: Silent Threat; Mission: Exodus
DescriptionThis is the second mission in a two-part series (squadron, weapons, and selected ship carry over from previous mission). The ship that you begin, along with weapons is not what was flown in the previous mission. Actually, to make matters even more insidious, you begin this mission flying an URSA loaded with nothing but two disruptor cannons, and completely empty missile bays of Stillettos.
This is a mission that requires some pretty quick anti-fighter firepower, and in my opinion short of a miracle, it is almost impossible to succeed in this mission on the squadmates alone (god only knows what their load-outs are...haven't verified yet) even if they do have any real firepower. This is such a bad mistake, it almost has to be thought of as intentional...lol. Surely, I'm not the first person to play entirely through the silent threat port, am I??
TagsNo tags attached.

Relationships

has duplicate 0001297 resolved Pilot file corruption if Cancel->Yes, accept pressed in debriefing. 

Activities

thesource2

2007-02-19 16:05

reporter   ~0007671

That's strange. I too have noticed that nothing is carried from previous mission (but it is normal since no red alert happens on it). But in Exodus I have two wings on Hercs with two Prometheuses and both full banks of Phoenix V's.

Ghaleon4

2007-02-19 23:06

reporter   ~0007673

You know what? Now that I think of it...
I think that the equipment I've started out with on this mission, just so happens to be exactly what I took with me to destroy the Lucifer in the FS Port campaign. (I know, you're supposed to let Delta Wing Destroy the Lucifer, but they suck at it).

So here's my summarized theory:
The 2nd part of the two part mission (Exodus) in Silent Threat is for some reason, pulling up the previous ship selection and load-out from my fight with the Lucifer in a completely seperate campaign.

thesource2

2007-02-19 23:46

reporter   ~0007674

And my theory is that your pilot file just got corrupted. Have you pressed cancel on debriefing or something? (It should be fixed already however).
By the way Ursa's with Harbingers do not suck - in my case I ordered everyone to attack reactor 1. When they destroyed it I wanted to order them to attack reactor 2 but all reactors except 5 were destroyed already! In 5 seconds Lucifer died.

HenrikP

2007-02-20 00:01

reporter   ~0007675

I see similar things going on with my profile.. Happend when I pressed cancel in some briefing, and when I returned all weapons except the rockeye and..hm. Might have been prometheus or something along those lines. The maxim and kayser - gone. Along with everything else.

Seems like there's some bug here. I installed..well thatever version is current. The first time I use fs2_open, so the profile was converted from original FS2..

thesource2

2007-02-20 11:46

reporter   ~0007677

Aha. So that's were it is. You see, there was a bug when you pressed cancel in debriefing and then "No, retry later", the next mission would still be planned for next session and pilot file got corrupted (same problem with weapons). This bug was partially fixed: "No, retry later" button functions properly now. But it seems that pilot fle corruption is still here (Cancel, "Yes, accept"). I'll report this at once.

Goober5000

2007-02-22 00:12

administrator   ~0007686

This has absolutely nothing to do with pilot corruption. It's a design flaw in the way red-alert missions work, because they're supposed to always follow a mission that ends in a red alert. It will be redone in 3.7.

But this can be fixed extremely easily by opening the mission in FRED and changing the Mission Specs dialog from Red Alert Mission to Scramble Mission. We purposely kept the old bug in the Port, but I think I'll fix it in the next release.

Issue History

Date Modified Username Field Change
2007-02-19 10:46 Ghaleon4 New Issue
2007-02-19 16:05 thesource2 Note Added: 0007671
2007-02-19 23:06 Ghaleon4 Note Added: 0007673
2007-02-19 23:46 thesource2 Note Added: 0007674
2007-02-20 00:01 HenrikP Note Added: 0007675
2007-02-20 11:46 thesource2 Note Added: 0007677
2007-02-22 00:12 Goober5000 Note Added: 0007686
2007-02-22 00:14 Goober5000 Relationship added has duplicate 0001297
2007-02-22 00:15 Goober5000 Status new => resolved
2007-02-22 00:15 Goober5000 Resolution open => no change required