Author Topic: TF ending movement order not to a selected location.  (Read 908 times)

0 Members and 1 Guest are viewing this topic.

Offline Kaiser (OP)

  • Commander
  • *********
  • K
  • Posts: 324
  • Thanked: 41 times
TF ending movement order not to a selected location.
« on: May 17, 2020, 09:09:00 AM »
Is happening to me that my cargo TF are not ending oders at the right location as per movement order .

In the specific case, I ordered my Cargo TF to move to Earth (from an X location). When they arrive, they end the route at LP1 which I created, but not at Earth as per order.

From the screenshot you can see "Big Cargo Fleet 001, having just compleated the order (moving to Earth), however it is sitting next to LP1.

Is that WAI or what?
« Last Edit: May 17, 2020, 09:39:49 AM by Kaiser »
 

Offline consiefe

  • Lieutenant
  • *******
  • c
  • Posts: 159
  • Thanked: 17 times
Re: TF ending movement order not to a selected location.
« Reply #1 on: May 17, 2020, 10:39:20 AM »
It obviously missed the earth, as earth goes around sun's orbit. But that never happened to me and I don't think it's WAI.
 

Offline SpikeTheHobbitMage

  • Bug Moderators
  • Commodore
  • ***
  • S
  • Posts: 670
  • Thanked: 159 times
Re: TF ending movement order not to a selected location.
« Reply #2 on: May 17, 2020, 10:54:49 AM »
Looking at your second fleet, it has LP1 (Earth) as its destination.  Are you certain you selected Earth and not the LP when you gave the movement order?
 

Offline Father Tim

  • Vice Admiral
  • **********
  • Posts: 2162
  • Thanked: 531 times
Re: TF ending movement order not to a selected location.
« Reply #3 on: May 17, 2020, 04:35:02 PM »
Yeah, you sent "Big Cargo Fleet 01" to LP1 (Earth), not to Earth.
 

Offline Kaiser (OP)

  • Commander
  • *********
  • K
  • Posts: 324
  • Thanked: 41 times
Re: TF ending movement order not to a selected location.
« Reply #4 on: May 18, 2020, 03:25:02 AM »
Sorry guys, I then noticed from history that I had selected the Lagrance point Earth instead of the body, no mistake no bug at all.