It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
Star Wars™: TIE Fighter Special EditionCapture Harvok Problems/Glitch? (1998)(3 posts)(3 posts)
(3 posts)
Pages:
1
This is my favourite topic
Posted November 19, 2014
I'm having trouble with the mission 5-5, Capture Harkov. The trouble is: None of the ships I'm supposed to disable ever leave the platform, and if any of them are so much as tapped, they blow up. Missile, dead. Laser, kaboom. Ion Canon: fireball. (Technically: they take the usual damage, but then enter their death animations and die anyway.) I ignore them in hopes that they take off and they get blown up by crossfire. Any thoughts?

EDIT: Restarting the game seems to have resolved it, sorry about that. What an odd problem, though.
Post edited November 19, 2014 by Blackdrazon
Posted November 23, 2014
from my old mission editing days, I remember that if you were to do something to a craft that an event was keyed to... say destroy a craft that wasn't meant to be, another craft who's command list depended on that ship to complete it's mission before starting wouldn't start... and it would just sit there.

All craft are given a priority target list for each task 'wait until X has done Y' or 'search for X craft to attack'

So when you break those dependencies weird stuff can start to happen. Sometimes it isn't even you that broke it, it's possible a freak occurrence in the mission cause something (like a collision) to be destroyed which shouldn't have been.
Posted November 24, 2014
avatar
lurkingknight: from my old mission editing days, I remember that if you were to do something to a craft that an event was keyed to... say destroy a craft that wasn't meant to be, another craft who's command list depended on that ship to complete it's mission before starting wouldn't start... and it would just sit there.

All craft are given a priority target list for each task 'wait until X has done Y' or 'search for X craft to attack'

So when you break those dependencies weird stuff can start to happen. Sometimes it isn't even you that broke it, it's possible a freak occurrence in the mission cause something (like a collision) to be destroyed which shouldn't have been.
That makes a lot of sense, though I wonder what was going wrong that made it... keep going wrong? Maybe some flag got triggered before the mission even started.

Thanks for the insight, that's really interesting!
Pages:
1
This is my favourite topic
Community
Star Wars™: TIE Fighter Special EditionCapture Harvok Problems/Glitch? (1998)(3 posts)(3 posts)
(3 posts)