Recent discussion regarding Sector Space has brought up something several people have experienced. Autopilot not quite working in many areas.
In an effort to help the Devs in some way to narrow down the issue, I'd like to collect data on where Autopilot doesn't work. Please feel free to contribute any information you can, and please be sure to include your starting point and your destination as sometimes it works going to one place, but not another. If you wish to include faction feel free.
I can't take it anymore! Could everyone just chill out for two seconds before something CRAZY happens again?!
The nut who actually ground out many packs. The resident forum voice of reason (I HAZ FORUM REP! YAY!)
normal text = me speaking as fellow formite colored text = mod mode
This program, though reasonably normal at times, seems to have a strong affinity to classes belonging to the Cat 2.0 program. Questerius 2.7 will break down on occasion, resulting in garbage and nonsense messages whenever it occurs. Usually a hard reboot or pulling the plug solves the problem when that happens.
I haven't tried it recently, but the one I've had trouble with on several occasions was the Tzenkethi Battlezone ... I believe that is Defera to TB, though it might have been DS9 to TB. I'll test it in a bit on a few characters and edit this post.
Edit: Ok, after some testing if I transwarp to Defera and then try to auto-pilot to the Tzenkethi Battlezone it doesn't work, even if I fly somewhere else in the quadrant first. Auto-pilot just sets the throttle to 50% and doesn't steer the ship at all.
If I enter the quadrant from DS9 then auto-pilot to the Tzenkethi Battlezone DOES work.
I found Sherman's Planet to Nakura to be the worst. So now I keep 'Spin the Wheel' in my Mission List and travel to Nakura from Drozanna.
I've found the greatest mess-ups if you travel in Sector Space after just Transwarpping to a location. Also, be cognizant of the direction your ship is facing after a Transwarp. Refacing towards your Sector Space destination may somewhat mitigate mess-ups. Shermans/Nakura would never benefit from this .
'But to be logical is not to be right', and 'nothing' on God's earth could ever 'make it' right!'
Judge Dan Haywood
'As l speak now, the words are forming in my head.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
DS9 to Gon'cra. If you are near sol and want to go to delta volanis the nav trigger the do you want to go to alpha quadrant dialog. still get caught inside stars too but it's rare
Starbase 39-Sierra to Haakona. Defera to Bajor (because for some reason I can always transwarp to Defera, but never to Bajor, despite having Bajor theoretically available on the transwarp list, so I'll jump to Defera then fly to Bajor when I want to get to DS9 - but autonav will send me in the opposite direction until I turn manually).
Qo'nos to Narendra. Every time I set it to go to Narendra (which is about 30 or forty degrees east of north from Qo'nos) it would instead try to head somewhere in the direction of Viranat (about the same angle but to the west instead).
It refused to head for Narendra until I flew it manually towards that destination and got within a few degrees of the correct angle, then it locked on Narendra instead of mirroring it.
Also, as Corinthalas mentioned the transwarp does tend to break any navigation lock and the ship just keeps going in the general direction but does not stop at the destination and hitting any stars along the way will throw the ship off course, and without the lock the ship does not correct course so you can end up quite a ways off from the destination. A kludge for that transwarp problem is to re-set the destination when engaging transwarp and again once it runs out and the ship returns to regular warp.
0
rattler2Member, Star Trek Online ModeratorPosts: 58,670Community Moderator
Also, as Corinthalas mentioned the transwarp does tend to break any navigation lock and the ship just keeps going in the general direction but does not stop at the destination and hitting any stars along the way will throw the ship off course, and without the lock the ship does not correct course so you can end up quite a ways off from the destination. A kludge for that transwarp problem is to re-set the destination when engaging transwarp and again once it runs out and the ship returns to regular warp.
If you're talking slipstream, its based on HOW you activate it. If you use your throttle controls then yes it will break the autopilot. However if you put the slipstream power in your power tray, then no it won't break autopilot.
I can't take it anymore! Could everyone just chill out for two seconds before something CRAZY happens again?!
The nut who actually ground out many packs. The resident forum voice of reason (I HAZ FORUM REP! YAY!)
normal text = me speaking as fellow formite colored text = mod mode
Also, as Corinthalas mentioned the transwarp does tend to break any navigation lock and the ship just keeps going in the general direction but does not stop at the destination and hitting any stars along the way will throw the ship off course, and without the lock the ship does not correct course so you can end up quite a ways off from the destination. A kludge for that transwarp problem is to re-set the destination when engaging transwarp and again once it runs out and the ship returns to regular warp.
If you're talking slipstream, its based on HOW you activate it. If you use your throttle controls then yes it will break the autopilot. However if you put the slipstream power in your power tray, then no it won't break autopilot.
Yes, I meant slipstream, I get those two names mixed up for some reason
I've noticed that the Delta quadrant portal from pretty much anywhere seems to stop few light years early from the interact point when using autopilot regardless if you use standard warp or slipstream, the Solanae gateway that is.
Also this happens regardless of faction.
Transwarping to Azure Nebula then trying to set course for New Romulus, Carrera System or the Dyson gateway almost never works while inside the Azure nebula, once outside it will then lock on.
Starbase 39-Sierra to Haakona.
Setting course for DS9 or Bajor doesn't stop when it reaches location, you just continue past until you hit the edge of the sector. The same happens when setting course for Drozana Station, you fail to stop and instead fly right on past. Does not seem to matter where you set course from. Most annoying if you set course and went for a bathroom break only to come back and find yourself at the edge of the sector again and then have to turn around and fly all the way back. If I could fire my navigator I would.
On occasion setting course for Nimbus III also goes past the planet, but not always, seems to be about a 60/40 chance of actually stopping, Slipstream may also interfere with this. Nukara seems to be about a 30% chance of flying past the planet also.
Faction does not seem to have any effect as it happens on Romulan, Klingon or Fed captains.
I should also note that these issues from playing the Xbox version, I don't play the PC version very often so I don't know if the same issues occur there as often.
Transwarp to Defera > Depart System > Auto Navigate to DS9, Bajor, Goncra, etc.
Ship will throttle up to 1/2 speed and travel straight ahead with no turns. Stopping and re-engaging auto navigate results in the same behavior. Changing elevation fixes the issue.
0
rattler2Member, Star Trek Online ModeratorPosts: 58,670Community Moderator
K-7 to Fed Fleet Starbase
Fed Fleet Starbase to K-7
I can't take it anymore! Could everyone just chill out for two seconds before something CRAZY happens again?!
The nut who actually ground out many packs. The resident forum voice of reason (I HAZ FORUM REP! YAY!)
normal text = me speaking as fellow formite colored text = mod mode
I also experience issues with the autopilot. I have noticed that many of the issues with navigation are between points close or on the same horizontal plane. Or perhaps there isn't good line-of-sight to the target. I usually plunge my ship down or up and am successful on the next autopilot attempt after moving on the Z axis. Perhaps the system has issues with navigating in a 3D environment? For me it became worse after the sector walls came down. Has anyone tried this work-around to verify?
going from defera or DS9 to the goncra battlezone, you have to go above mariah /defera sectors before it locks on. I usually go to zaria or raveh, then as i approach there, i switch to the battlezone
I cannot transwarp to any of the choices in the Alpha quadrant menu from anywhere. If I have a transwarp coil I can transwarp to any of those additional choices. The main menu choices of Defera, DS9, and the others do work just fine as well. I do have random autopilot fails that take me in the wrong direction. Second activation usually corrects the course. I will watch for any pattern to it as nothing stands out that I have noticed.
I would like to add that I cannot auto-navigate from Sherman's Planet to the Federation Starbase. Also, on some of my characters, not all, I cannot transwarp to the Alpha Quadrant. Not sure if this is a level induced restriction or another type of restriction based on episode play, though.
Autopilot not working in many cases has been around for several years. For me the usual result is, I open map, click my destination, and my ship just starts flying straight ahead in whatever direction it was pointing.
It may be less a situation of "where" it happens and more something to do with the code context your captain is in.
At any rate, one of the most common ones is depart Qo'Nos system, you're in sector space pointing roughly at KDF Fleet starbase. Autonav to Fleet Starbase, ship just starts flying straight ahead.
For me it appears to be just about anywhere I go from or to it passes the destination and refuses to stop.
In fact it has happened to me sooo much that I monitor it while its going so I stop the ship when it reaches its destination, since the computer has no clue how to stop the ship any more
From quonos, I also find from time to time the ship wont turn or even begin to alter course to target let alone stop at it when its supposed to.
Almost every time I use the slipstream drive... the ship will lose target lock on the destination and fly past. So, after any use of slipstream, I will re-target my destination or manually stop slipstream. Also, bouncing off a star seems to disrupt auto-nav as well.
Almost every time I use the slipstream drive... the ship will lose target lock on the destination and fly past. So, after any use of slipstream, I will re-target my destination or manually stop slipstream. Also, bouncing off a star seems to disrupt auto-nav as well.
I was right about to post this myself. I haven't hit the issue with the Autopilot NOT working but there are times where i set a destination and just don't go there. Slipstream is the most notable example of things that turn off the autopilot.
EVERY time, Every usage, it just says "Nope!" to the autopilot
That has always been a feature of autopilot. Any manual inputs after autopilot is engaged turns off autopilot. The thinking behind this is that the player wants control of the ship back. They decided that slipstream is a manual input and turns off autopilot, so you have to re-target your destination after slipstream is finished.
That has always been a feature of autopilot. Any manual inputs after autopilot is engaged turns off autopilot. The thinking behind this is that the player wants control of the ship back. They decided that slipstream is a manual input and turns off autopilot, so you have to re-target your destination after slipstream is finished.
I have found that you can re-target your destination right after you set your SSD, but YMMV.
Comments
Edit: Ok, after some testing if I transwarp to Defera and then try to auto-pilot to the Tzenkethi Battlezone it doesn't work, even if I fly somewhere else in the quadrant first. Auto-pilot just sets the throttle to 50% and doesn't steer the ship at all.
If I enter the quadrant from DS9 then auto-pilot to the Tzenkethi Battlezone DOES work.
I've found the greatest mess-ups if you travel in Sector Space after just Transwarpping to a location. Also, be cognizant of the direction your ship is facing after a Transwarp. Refacing towards your Sector Space destination may somewhat mitigate mess-ups. Shermans/Nakura would never benefit from this .
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
It refused to head for Narendra until I flew it manually towards that destination and got within a few degrees of the correct angle, then it locked on Narendra instead of mirroring it.
Also, as Corinthalas mentioned the transwarp does tend to break any navigation lock and the ship just keeps going in the general direction but does not stop at the destination and hitting any stars along the way will throw the ship off course, and without the lock the ship does not correct course so you can end up quite a ways off from the destination. A kludge for that transwarp problem is to re-set the destination when engaging transwarp and again once it runs out and the ship returns to regular warp.
If you're talking slipstream, its based on HOW you activate it. If you use your throttle controls then yes it will break the autopilot. However if you put the slipstream power in your power tray, then no it won't break autopilot.
normal text = me speaking as fellow formite
colored text = mod mode
Yes, I meant slipstream, I get those two names mixed up for some reason
Also this happens regardless of faction.
Transwarping to Azure Nebula then trying to set course for New Romulus, Carrera System or the Dyson gateway almost never works while inside the Azure nebula, once outside it will then lock on.
Starbase 39-Sierra to Haakona.
Setting course for DS9 or Bajor doesn't stop when it reaches location, you just continue past until you hit the edge of the sector. The same happens when setting course for Drozana Station, you fail to stop and instead fly right on past. Does not seem to matter where you set course from. Most annoying if you set course and went for a bathroom break only to come back and find yourself at the edge of the sector again and then have to turn around and fly all the way back. If I could fire my navigator I would.
On occasion setting course for Nimbus III also goes past the planet, but not always, seems to be about a 60/40 chance of actually stopping, Slipstream may also interfere with this. Nukara seems to be about a 30% chance of flying past the planet also.
Faction does not seem to have any effect as it happens on Romulan, Klingon or Fed captains.
I should also note that these issues from playing the Xbox version, I don't play the PC version very often so I don't know if the same issues occur there as often.
Ship will throttle up to 1/2 speed and travel straight ahead with no turns. Stopping and re-engaging auto navigate results in the same behavior. Changing elevation fixes the issue.
Fed Fleet Starbase to K-7
normal text = me speaking as fellow formite
colored text = mod mode
I tried to autopilot and my ship literally sat and spun 360's until I repeated the exact same actions, then it took off in the right direction.
It may be less a situation of "where" it happens and more something to do with the code context your captain is in.
At any rate, one of the most common ones is depart Qo'Nos system, you're in sector space pointing roughly at KDF Fleet starbase. Autonav to Fleet Starbase, ship just starts flying straight ahead.
In fact it has happened to me sooo much that I monitor it while its going so I stop the ship when it reaches its destination, since the computer has no clue how to stop the ship any more
From quonos, I also find from time to time the ship wont turn or even begin to alter course to target let alone stop at it when its supposed to.
I was right about to post this myself. I haven't hit the issue with the Autopilot NOT working but there are times where i set a destination and just don't go there. Slipstream is the most notable example of things that turn off the autopilot.
EVERY time, Every usage, it just says "Nope!" to the autopilot
I have found that you can re-target your destination right after you set your SSD, but YMMV.
I could use some advice from Sidney!