Issues with carrier jumps

[Klearoflauge]

G' Day Commanders!
So, in the past our wing/squadron had noticed issues with some of us not getting the countdown timer before the jumps which lead to being left behind.
The answer to this seemed to be re-logging and checking to see if there was a countdown or waiting until the carrier jumped to log back in.

Lately though, (aside from that), we have been noticing there is no jump sequence at times; as well as,
no being locked out of carrier services at the beginning of when said sequence should take place.
There is no way of knowing if the carrier jumped or not and the wing icons will show some members in the current system while others seemingly made the jump.
The carrier navigation menu will usually show the system jumped to, unless it freezes b4 jump, and our individual ship navigation menus still show the system we jumped from...
unless of course you are one of the members that the wing icons show have made the jump, in which case they show the correct system. Re-logging also seems to solve this with, as of yet, no one being left 400+ LY in the distance.

Have any other carrier commanders experienced this, is there a solution, is this a reported bug?
Thanks in advance for any insight regarding this issue, o7 commanders!

 

[Bottom Hat]

G'day Sheila.

 

[Quantis Trap]

Almost too many carrier bugs to keep track of.
For instance, I've also seen a situation where I arrive at my carrier (from SC) and it notifies me it's preparing to jump. The only problem is that I didn't tell it to jump and it's not scheduled for one.

 

[Stabby_Dave]

This one has been reported many times. If you're on the carrier and don't get the countdown, relog after the jump and you're golden.

 

[CMDR Karrde Sun]

Yeah i think that happened to me the other day too. Came back and the carrier was in a perpetual travel mode. Was fine when i logged back in.

 

[varonica]

Have any other carrier commanders experienced this, is there a solution, is this a reported bug?
Thanks in advance for any insight regarding this issue, o7 commanders!

It's basically due to pushing the jump sequence to as short a time as possible due to player requests, when a carrier jumps that information has to be propagated across the entire internet and 3 platforms that essentially form separate subnets, PC, PS4 and Xbox, if the internet is being a bit slow for some players or there's unusual network activity this sometimes causes issues where a player data hasn't been updated and still thinks the FC hasn't moved. Logging off and back on forces the client to download player data to update locations, fixing the issue.

I know in one instance I was left behind by my own fleet carrier when launching, I didn't realise it hadn't updated my location, this was just after a mini patch so network traffic was probably being slowed by a lot of players updating.

I'm not sure there's any fix for this since it's caused by network traffic outside FDEV's control, except of course making FC jumps take a longer time so that the data has time to propagate across all networks, and I can't see that happening.