I had the same problem of getting the ship first and calling the subcommander after. Apparently, she holds a grudge :D The GM suggestion of abort mission did not work for me (in fact, it has, to date, never worked for me), but the suggestion of starfish1701 did work. I switched back to my first ship, dismissed the new one…
It's extremely annoying. After relog, just stand and observe that area for a while and you will see that most people freeze mid-run (which would be quite comical if it weren't so sad). Also, this thread handles the same issue: http://sto-forum.perfectworld.com/showthread.php?t=324071
Which three files did you delete and has it consistently fixed your issue? :confused: Oh, and there's a similar thread (probably more): http://sto-forum.perfectworld.com/showthread.php?t=324071
I tried this and unfortunately, it did not work. Once I went up to the conference room, Disarming Diplomats should have ended and Engaging Envoys should have started. Good thought though. I issued a GM ticket (since they tend to reply to those), but the number disappeared and my chat got cleared, so sadly I did not get the…
:rolleyes: Good theory, although the Night of the Comet mission (which I am speaking of) happened *before* the Guardian of Tomorrow sent B'Vat back, which pretty much precludes that possibility. Even if you throw in temporal mechanics (they give me a headache), all the Klingons' 25th century ships were destroyed. I do…
I don't know. I have not been playing STO for that long, but I have visited Memory Alpha several times before S6 and never had a single problem (aside trying to locate the fanatically wandering Mr. O'Brien), but since S6, the crashing is such a foregone conclusion (it happens fully 100% of the time) that I have given up on…
Yes, this is a known - and highly annoying - bug and has been for a while. See one of the existing threads: http://sto-forum.perfectworld.com/showthread.php?t=272234
I have found this to be true for Alpha and for several other missions. It seems to occur when you beam out too quickly. When you beam out, make sure that the dialog box states that you have completed all mission objectives. Sometimes, it will state that if you leave now, you might lose mission progress. When I then close…
I found myself actually looking for the "Like" button when reading this :D It is quite annoying, I agree. I have tried this several times and ran into the same problem.
I have noticed the same thing. I have found that sometimes (not always) it helps when you force-move (no Star Wars pun intended) the BOFF to stand near you with a waypoint and then remove the waypoint (freeing them up to 'normal' AI behavior). This worked for me in Gre'thor.
Not sure if this had been mentioned, but it seems that Memory Alpha is bugged too. I don't remember that bug from existing before S6, but whenever I leave the transporter room and enter the corridor, I crash to desktop. I have seen it happen to many other players at the exact same location. It has happened occasionally in…
Bumping. This happens to my Federation character (had no trouble with my Klingon) and the mission progresses all through negotiations and the battle on the station to the space battle to the warp to Bajor, but the mission does not update, so when I get to Bajor, there's nothing to do. Am I missing a trigger point somehow?
It's not your system, I think. I have the same thing. It mostly (and consistently) happens when I leave the transporter room and enter the main corridor. After I relog, I am fine, unless I go back to the transporter room and then try to re-enter the corridor. I have stood and observed this part of Memory Alpha and I have…
I had hoped that this would be fixed in Season 6, but no dice. Maybe if the Federation players who own a refit Defiant class starship start complaining, they will start fixing it.