45 minute countdown

Just set a jump back to my home system after installing the new services to see the jump from my command seat and there's a 45 minute countdown.... FORTY FIVE MINUTES????
 
My carrier normally only needs 15 minutes to initiate a jump. My first jump after the update it reported jumping in 54 minutes! That's ridiculous!
 
My carrier normally only needs 15 minutes to initiate a jump. My first jump after the update it reported jumping in 54 minutes! That's ridiculous!
The server automatically queues fleet carriers to ease server load. It just never needed to activate until now, since right now everyone is jumping their carriers
 
My carrier normally only needs 15 minutes to initiate a jump. My first jump after the update it reported jumping in 54 minutes! That's ridiculous!
To anyone experiencing higher jump times that usual: this is an intentional feature designed to spread the server load with a virtual backend queue.
Your carrier will go back to normal. Right now every carrier in the galaxy is jumping because people want to see The New Thing. Wait a bit, if you can.
 
Plus side to this is, I now have plenty of time to explore a system, before getting back to the FCOC Sleeper Service, en route to the Bubble.

And the jump sequence lightning was pretty awesome, though I was 'escorted back' to my 'designated seat', instead of being able to press my face against the window...
 
Just set a jump back to my home system after installing the new services to see the jump from my command seat and there's a 45 minute countdown.... FORTY FIVE MINUTES????


Honestly, this is a great idea for situations like this. Previously your jump would just fail or worse, your game would crash or everybody's game in the system would crash.

Now it does suck that it's based on total FC jump activity game wide rather then geography, so like bubble systems would have the queue but once you got away it would taper off. But it seems even if you are in the boonies, your carrier is still going to take more time to do it's jumps. but like I said it's better than the alternative, so clever fix for this problem Fdev.
 
Was on my way back to the carrier when I noticed the ETA was 42 minutes, but decided to land again anyway, and then decide what to do. When I checked again, though, the nav screen had 'No departure planned' for the carrier, so I thought, maybe the CMDR had decided to wait out the delay.

I went back out to scan the other bodies, and on my return trip, saw that the jump time had returned, and was now just over 11 minutes.

I guess that means you can suspend a jump and resume again, without going back to square one.

Or, it's a glitch.
 
Latest...

Sat down waiting for the jump, and HUD said 4 minutes, so I thought I'd see how far I could get from the forward deck and be brought back. At the terminals, Navigation said the jump would be on 52 minutes. Went back to my seat and waited over five minutes, but nothing, even though the ship outside had been in darkness with red 'emergency' lights, the whole time.

The terminals were still giving the longer count, as was navigation on my ship. This could be a long trip.
 
Just set a jump back to my home system after installing the new services to see the jump from my command seat and there's a 45 minute countdown.... FORTY FIVE MINUTES????


Servers are busy, everyone jumping same timer, it'll cool down later.

And that's why I had my carrier jump two weeks ago to a nearby system that offers Fleet Carrier Admin Services. When I log in later, I'll add the services I want and then have it jump back to where I want it stationed.

Next time, plan ahead... ;)
 
Back
Top Bottom