Pilot Archive

Message Edited by -zoe- on 12-19-2004 07:45 PM

I am certain the developers are aware this is a real issue, not a figment of our imaginations. When devs themselves are having the problem and report it, I would consider that as knowing there is a real issue here.

---

PConsole wrote:
I haven't done this mission yet, and it seems like there are a lot of people having this problem but I thought I'd throw out a possible idea anyway. Since this mission takes place over various systems, is it possible that the travel time to the various targets is what's causing the time-out? In other words, perhaps if you hyperspaced to a different sector to do the mission, maybe one that was closer to the eventual targets that appeared, there wouldn't be a time-out?

---

Absolutely not, I have done this mission enough to know the closest hyperspace points, and I do everything fast as humanly possible. Escort missions area timed survival, not kill this many ships in this amount of time.

/bump. Like I said, this is staying at the top til it's fixed.

---

-zoe- wrote:

Apparently swg devs had no idea this was happening and thought it was just us doing it too slow.

---

you're kidding, right? a ton of people suddenly shows up posting about this bug, tiggs posts a thread and they STILL didnt realize that they screwed up again? i already knew soe cosiders its customers a bunch of naive morons, but it would be nice if they showed it just a little less obviously.

---

Also they thought they had fixed this issue already

---

might be just me, but usually when i _think_ i fixed a bug i do some testing to turn _thinking_ into _knowing_ (or else they should wonder if maybe there version control system is worthless).

---

But at least it has now been recognised as a bug and not just us being too slow and will now be fixed hopefully soon.

---

sweet... so how many days did they need to figure this out? "oh no, it cant be our fault, we never screw up, it must be the players being too dumb to play the game". i guess me still paying each month and actually still dreaming about this game someday living up to its potential and not being held down by bugs and utterly unfunny "game design" is reason enough to assume just that.

seriously, we are talking about a couple capture/escort missions, how exactly would a player be "too slow" in one of those? how would a group of 5-10 players be too slow? or do they think a couple of primates somehow magically cheated their way all through tier 3.75 and now suddenly begin to fail just right after a certain "update"?

Message Edited by Trienco on 12-19-2004 12:51 AM

Some of you are experiencing missions that fail due to running out of time. For one type you must dock with a craft that is listless in space to repair, and then escort them out of the system. For the other suspected type you must chase down a ship in transit, disable to capture and then escort them out of the system.

• Is your pilot faction Rebel, Imperial or Neutral? Imperial, Black Epsilon


• Was your first trainer on Naboo, Tatooine or Corellia? Imperial Outpost, Talus


• What is the name of or Tier of the trainer that give you the impassable mission? It is the Tier 4 Mission Giver on Dantooine, Imperial Outpost (He is in the back of the cantinna)


• Which mission in the series, or duty mission, was it that failed due to the time limit being exceeded? This is the exit mission for Tier 4 Black Epsilon. Talk to mission giver. Launch in Dantooine and hyperspace to Dathomir. Wait for an AWing and his escort to spawn. Kill the AWing. Wait for a YT1300 and escorts to spawn. Disable the YT1300 and wait for it's auto-pilot to "reprogram". Destroy it's escorts. Escort the YT1300 through some waves of Velocity NPC's. After awhile it says."You have failed this mission. You took too long." (I have done this multiple times both solo and grouped, all with the same result)
  

Some of you are experiencing missions that fail due to running out of time. For one type you must dock with a craft that is listless in space to repair, and then escort them out of the system. For the other suspected type you must chase down a ship in transit, disable to capture and then escort them out of the system.

• Is your pilot faction Rebel, Imperial or Neutral? Imperial, Black Epsilon


• Was your first trainer on Naboo, Tatooine or Corellia? Imperial Outpost, Talus


• What is the name of or Tier of the trainer that give you the impassable mission? It is the Tier 4 Mission Giver on Dantooine, Imperial Outpost (He is in the back of the cantinna)


• Which mission in the series, or duty mission, was it that failed due to the time limit being exceeded? This is the exit mission for Tier 4 Black Epsilon. Talk to mission giver. Launch in Dantooine and hyperspace to Dathomir. Wait for an AWing and his escort to spawn. Kill the AWing. Wait for a YT1300 and escorts to spawn. Disable the YT1300 and wait for it's auto-pilot to "reprogram". Destroy it's escorts. Escort the YT1300 through some waves of Velocity NPC's. After awhile it says."You have failed this mission. You took too long." (I have done this multiple times both solo and grouped, all with the same result)

I can now report that it is not just a Black Epsilon exit mission issue (I know you're saying duh...) The exact same thing happen to a friend running this mission, also I was helping a nuetral pilot finish their tier 4's and they had the same problem. Basically, you go to the waypoint, disable the ship. Begin escort, make it through the whole escort and finally it says "Mission Failed, you took too long"

Seems to affect all missions of this type that I have run today of various pilot factions and tiers.