Pilot Archive
Thread: RotW Bug Avoidance and Workarounds
TheDarkmoons wrote:
Here is an useful insight into re-texturing issues posted by another poster. It would be nice to have this bug squashed, but it is definetly not as high priority as over issues that (god knows how) got past beta testing.
THANK YOU FOR POSTING THIS!! You know now ticked I am at this?
post script,
I'm also Thankfull for all the other workarounds so far too
Of course, I'm a day late and dollar short on the Heavy xwing bug. You know I escorted another 7 Frieghters before I realized they were duty missions? I was exhausted.
Message Edited by HuntingOhioan on 05-21-2005 04:15 AM
You said the Heavy X-wing quest was on the top of your list for things to be fixxed.
Why then is it not being fixxed in the next pub? They added new space mission for people that complete the Kashyyyk space missions but left people like me who cant advanced hanging out in the cold.
What is the problem here?
Also your work arounds are useless for most people. I for one didnt come to the pilot Forums untill I noticed I wasnt advancing in the quest. And then when i did notice it was broken I didnt come here first ..I went to the Quest and Mission forums.
All your so called work arounds fall under the " TO LITTLE TO LATE" branch of things.
The publish-specific one is that most of these fixes and changes have already been made (but not on TC, thus why they're in the notes) or were things that were in the works prior to the compilation of many of the RotW bugs. As a result, they aren't reflecting many of our recent issues, but are sort of a big bunch of catch-up fixes.
The general problem is I don't actually write the code or set the policy for SWG. My power as a correspondent is fairly limited; most of what I can do is make recommendations and discuss problems and solutions. I can talk about our problems till I'm blue in the face, then, but that doesn't necessarily mean we'll see any changes or fixes in a timely fashion. All it means is they're sure to know of the issue, and, hopefully, start in on a way to address it--because they do listen to us, and our input does have an impact. It just takes time to turn that information into a solution.
I know most of the info in this thread won't help pilots, because much like you, by the time they're aware of the issue and come along looking for help, it's already too late. But if it helps any pilots at all in either avoiding the bugs or dealing with them once they've been impacted by them, it's worth posting, and that's why I've got it here.
khany001 wrote:
Yes, when is the ARC-170 mission gonna be fixed. I managed to complete the quest, unpack and fly the ship. Now that I've packed it up to make room for my Jedi fighter I can't unpack it any more - it says I haven't done the quest
Not sure I'm correct, but after failing the imp prison part, I was able to talk to the Queen and redo the quest. I quit reb, and unpacked the deed.
khany001 wrote:
Yes, when is the ARC-170 mission gonna be fixed. I managed to complete the quest, unpack and fly the ship. Now that I've packed it up to make room for my Jedi fighter I can't unpack it any more - it says I haven't done the quest
Not sure I'm correct, but after failing the imp prison part, I was able to talk to the Queen and redo the quest. I quit reb, and unpacked the deed.
Yeah I did that to when I kept on failing the Imp Prison part - but I did manage to complete the whole quest and I got to use the ship. I packed up the ship when I went Imp to get the Jedi Fighter and now it says I can't unpack the ship because I haven't done the quest, even though I have. I think it's the same bug that affected the ARC deed when it first came out but I thought they fixed it.
When accepting this mission you need to be AT LEAST Imperial Combatiant (it dosen't tell you this)
If you're not then the ATST wanders off and fails you after the first Rebels attack.
Also, if you do not kill all attacking rebels (the ATST will assist you), the ATST will wander up a side bank, stay there a few minutes then warp back to the pick up point and, hence fail you again. It would seem once you're past the ATST part its pretty much home free appart from the rebels that spawm out of LOS/Map zone (Can't believe you guys placed a zoned map in a game that's always been almost 100% free roaming BAD BAD BAD!) anyway, work around for that is to use the /logout command and wait until Player select screen, log back in and one of two things happens; 1) You either get attacked right away by New Rebels (Sometimes the old ones are still there) or 2) You talk to imperial guy again and it starts over.