So, I was flying about fairly far afield, and started survey scanning a system. I then changed my mind and told my ship to fly to another system mid scan. Instead of aborting the scan, the crew kept surveying all the way into the next system. The survey then completed while I was in the next system (however I believe the crew successfully surveyed the original system, rather than the next one).
I then began flying around the rest of the sector. On several flights, the warp drive got stuck in an odd state, part of the way through the cycle process (the console would be stuck at some point in the animation). Restarting the console would cause it to become stuck on the first frame of trying to recharge, and the ship would then proceed to deadhead to the next system, unable to use warp. Its possible this is an unrelated issue, but it only started manifesting after the aforementioned situation.
Then, just now, the system I was in was surveyed despite no such order being present, and without any notification from the crew that they were working on a survey. The ship is now trying to deadhead to the next system while unable to warp. Typically a system transition will un-stuck the warp drive, however it appears that if the crew is allowed to begin trying to scan in this odd state then it will cause the warp drive to become stuck again.
I figured this was worth mentioning since its my general belief that this is not intended behavior.
I then began flying around the rest of the sector. On several flights, the warp drive got stuck in an odd state, part of the way through the cycle process (the console would be stuck at some point in the animation). Restarting the console would cause it to become stuck on the first frame of trying to recharge, and the ship would then proceed to deadhead to the next system, unable to use warp. Its possible this is an unrelated issue, but it only started manifesting after the aforementioned situation.
Then, just now, the system I was in was surveyed despite no such order being present, and without any notification from the crew that they were working on a survey. The ship is now trying to deadhead to the next system while unable to warp. Typically a system transition will un-stuck the warp drive, however it appears that if the crew is allowed to begin trying to scan in this odd state then it will cause the warp drive to become stuck again.
I figured this was worth mentioning since its my general belief that this is not intended behavior.