Two players jumped to Bractus C-5, and I was one of them. We were grouped, and I was the group leader. My capital ship was sent a considerable distance away for a while. I jumped to E-2 and ordered the ship to follow, but nothing happened. I realised I was still part of the group and assumed the ship would return to my original jump position. I ordered it to park, left the group, and commanded the ship to follow again. Still, nothing happened. I jumped back to check on my ship, which was flying somewhere. I ordered it to stop, then follow, and jumped out again. Usually, this results in an instant jump of the capital ship, but not this time. After waiting for more than 10 minutes, my ship was still flying in C-5 while I waited in E-2.

I asked the second player and learned that the original group still existed. Only he and his capital ship were in the group. The capital ship was in the space, and he was docked with it. I asked him to disband the group, of which he had become the owner after I left. I ordered the ship to park/follow again. Although nothing happened immediately, the ship finally arrived within a minute. I'm unsure if disbanding the group I was no longer in helped or if the ship just reached the desired jump point after all that time.

Yesterday, a similar situation occurred with a very similar or identical group setup. However, this time I took an escort mission. The convoy travelled about 70 km away from the station before jumping out.

Recently, I've been experiencing more issues with ships not following me promptly. For example, out from the unrats sector.

Okay, we'll take a look. A couple of notes:

- It's super helpful to have date/time for these kinds of incidents.

- "Follow" is often slower if the sector containing the capship is still running, because the ship has to actually do the behaviour that is expected for the situation, and there may be asteroids within 3km or some other factor. In a non-running sector, they tend to jump more quickly.

All that said, what you're reporting is pretty unusual and undesirable, especially on the order of 10 minutes. We'll see what we can do.

- Sorry: GMT is Tue, 22 Oct 2024, 04:53:43. Please search between 04:50:23, when I entered E-2 for the first time, and 05:06:22, when I finally docked with the ship in E-2. During this period, I returned to C-5 to check the situation (04:52:51 - 04:53:25).

- The ship was definitely ready to jump. Full battery and "a considerable distance away" (several tens of thousands metres). I initially wrote "was sent a considerable distance," but I likely flew there and left the ship in a jumpable position.

So, if a capship is in a group, there is a concept of a "group jump point", such that the group can all find one another and tactically move as a whole. This was also important for things like convoys, to keep the convoy together instead of spreading apart and being easily "picked off" by attackers.

Anyway, we're changing capship behaviour in this next patch to where, on receiving a "follow" command, it will immediately head for the nearest viable jump-out point, and not the "group jump point", which may have been considerably further away (or behind asteroids that required flying around, etc).

I was aware of this behaviour, which is why I left the group. It is mentioned in the opening post. Although it appeared to be related to the "group jump point," I was not in a group after the first attempt. If it was related to the "GJP," this change will probably resolve the issue anyway. Thank you for taking care.

Yes, we saw what you wrote. But whether you left the group may not have mattered. I'm not sure if the capship re-assesses its chosen jump-point based on changes in group dynamics, within a single sector runtime.

In any event, as you say, this should be the proper solve for this particular issue.

Unfortunately, it still does not work. Bractus C-5. I was in a group. The capital ship was about 70 km away in an instantly jumpable position. I jumped to B-14 and ordered the ship to follow. The ship began moving somewhere within the sector but didn't jump. I am 100% certain it was parked in a jumpable position. I disbanded the group, park, follow, nothing worked. I literally had to go back to C-5 for my ship or wait about 10 minutes. So, I jumped back to C-5 (with the group disbanded), ordered follow and jumped back. The ship jumped with me immediately. Recreated the group ...

/time
GMT is: Sun Oct 27 09:55:03 2024

Additionally, when I was grouped in C-5 and plotted my route, the jump point was about 70 km away, likely due to the deep spaced capital ship.

Pelatus

/time
GMT is: Tue Oct 29 04:37:09 2024

We're lagged behind due to an unrelated project, but we'll examine this again soon.

Thank you. It's almost impossible to be in a group and work with capital ships at the moment. I always have to disband the group to call a capital ship in. If I accidentally forget, the situation worsens, and I also have to travel to the sector. Once the ship becomes "bugged" by being called while in a group, it won't arrive promptly, even if the group is disbanded.

This has hopefully been more thoroughly fixed as-of Vendetta 1.8.716, this past Thursday.

Ironically, there were some odd choices in the way the previous fix was implemented, which resulted in a case-sensitivity problem ("Follow" vs "follow") which was pretty silly. But, that's why we didn't catch the problem initially.

And, that also illustrates how helpful it is for us to get these kinds of hyper-specific date/time reports, to narrow down unexpected differences in usage.

LOL, that was a nice one. It works perfectly now. Thank you very much.