test content
Logo
What is the Arc Client?
Install Arc
Sector Space Autopilot thread
rattler2
Member, Star Trek Online Moderator Posts: 58,669 Community Moderator
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.
So for example...
K7 to Nukara Prime
Defera to DS9
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.
So for example...
K7 to Nukara Prime
Defera to DS9
The nut who actually ground out many packs. The resident forum voice of reason (I HAZ FORUM REP! YAY!)Yang Xiao Long wrote:I can't take it anymore! Could everyone just chill out for two seconds before something CRAZY happens again?!
normal text = me speaking as fellow formite
colored text = mod mode
Post edited by baddmoonrizin on
0
This discussion has been closed.
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!