Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: JohnSheridan on April 26, 2019, 04:39:46 pm
-
In Free Space: Silent Threat, Mission#4: On The Run will not finish. I destroy all Shivan and HOL ships. The scientists are evacuated from the GTSC Ratna. The PVFR Gemini tows the Ratna for awhile then stops and just sits there. I have let it sit for at least two hours and nothing happens. Doing things like flying around and shooting stuff doesn't help. I jump out, and the debriefing tells me that I've done a good job, but after pressing Accept, I get a message that I cannot Accept because I've failed the mission and must replay it.
I heard that Silent Threat had bugs but not that it was completely unplayable.
I initially purchased a used copy of Silent Threat and then purchased a brand new unopened copy in the box still in plastic wrap. Both do the same thing. I have a Win10-Home Ed. 64Bit HP Laptop with at least recommended system specs. FS and ST were installed in Win95 compatibility mode as Administrators. Also, the FreeSpace.exe is set to run in Win95 compatibility as Administrator.
Does anyone have any ideas about what is causing this and how to get ST moving along?
-
I just checked with the files that are provided with the Freepsace Port.
The mission objective that is required for the campaign to progress is for the Ratna to have warped out, aka "Ratna Successfully Escaped".
Gemini is supposed to dock with Ratna, tow it for a while, undock, then dock again, tow again and then undock again. After the second undock the Ratna should get its engines back and warp out on its own. Gemini is supposed to warp out after it.
Considering Gemini did not warp out the Ratna probalbly was not listed a departeted, which caused the relevant mission objective to not complete.
If you are playing the original there maybe an issue with the docking orders, as I see it there are a number of events referrencing docking proccedures for multiple ships but "on paper" I cannot say if they are properly sequenced. Retail FS1 and FS2 did not support a ship being docked with the multiple objects at the same time.
ps. Would you like to hear the word of our lord and savior, Silent Threat: Reborn (https://www.hard-light.net/forums/index.php?board=140.0)? ;)
-
Well, because the original FSPort Silent Threat never got some treatment because of ST:R i fixed most of it flaws and bugs in my Nova Upgrade version of it.
On the Run was one of the missions where i have implemented some additional bugfixes to make it work. (The other one should be Secret Recovery).
-
On the Run was one of the missions where i have implemented some additional bugfixes to make it work. (The other one should be Secret Recovery).
It's no coincidence we dropped both of those missions in Reborn.
-
It's been like that since the original release, actually, and I've experienced it myself quite a few times. Unfortunately, the only thing to do is restart and hope the transport realizes it's supposed to jump out. I can't help but wonder if it's the AI being conflicted over orders and it occasionally breaks.
Or, you know, just play Silent Threat: Reborn and experience an actual crafted and not-rushed story that doesn't feel like a huge chore to play through. ;)
-
The final mission of ST didn't felt rushed at all. :D
-
Good point! I felt like it took a rather leisurely pace to get to the climax. :P
-
Rubber-band the trigger and go have a drink. :P
-
^fs2.com
^k
I remember the first (and only) time I played this mission. I thought I had broken something because nothing ever happened for 20mins, and all you ever did was calling for support as the fighters were almost unable to do any harm to an Ursa. :lol:
-
Does anyone have any ideas about what is causing this and how to get ST moving along?
My best guess is that for some reason the game didn't register the waypoint path as complete. That has happened occasionally, but the original FreeSpace seems more prone to it than FS2. I suggest rebooting your computer and playing it again.
It's no coincidence we dropped both of those missions in Reborn.
Well, technically, On the Run became He Who Rides the Tiger.
-
Does anyone have any ideas about what is causing this and how to get ST moving along?
My best guess is that for some reason the game didn't register the waypoint path as complete. That has happened occasionally, but the original FreeSpace seems more prone to it than FS2. I suggest rebooting your computer and playing it again.
The waypoints have nothing to do with it. The mission entirely depends on a number of docking procceedures:
$Name: GTSC Ratna ;! Object #1
[...]
$Departure Location: Hyperspace
$Departure Cue: ( false )
$Formula: ( when
( and
( is-destroyed-delay 5 "Rama" )
( has-undocked-delay
"PVFr Gemini"
"GTSC Ratna"
2
0
)
)
( repair-subsystem
"GTSC Ratna"
"engine"
99
)
)
+Name: Warp fixed 3
+Repeat Count: 1
+Interval: 1
$Formula: ( when
( is-event-true-delay
"Warp fixed 3"
10
)
( add-goal
"GTSC Ratna"
( ai-warp-out 89 )
)
)
+Name: warp fixed 4
+Repeat Count: 1
+Interval: 1
-
That doesn't mean there isn't a waypoints-done-delay sexp as a dependency somewhere.
Having said that, I looked at the mission and waypoints-done doesn't appear anywhere. So something else must be going on.