Fleet Carrier warm up now 45 minutes?

This seems unreasonable, and I can't find it in the patch notes anywhere.
Also, if it's not a bug, shouldn't you have some sort of on-screen notification that tells people why!?
 

Attachments

  • Capture.PNG
    Capture.PNG
    405.8 KB · Views: 87
Lots of carriers in the same area trying to jump at the same time. Longer times reduce server load.
 
I'm in the middle of nowhere. I seriously doubt there is more than five people within 1000LY of my position.
Ah, ok. So player position in game doesn't play a (big) role in this.
Anyway, they've said the longer FC jump times are there to ease server load, when many carriers jumping at once.
 
Ah, ok. So player position in game doesn't play a (big) role in this.
Anyway, they've said the longer FC jump times are there to ease server load, when many carriers jumping at once.

Thank you :)

This sounds exactly like something Frontier might say, but honestly it smacks of either 1) poor / non optimisation, or 2) maybe they have a yellow i386 in a leaky shed out back doing the calculations and server updates.

They already had fifteen minutes to do the relevant changes to digital assets in digital locations for each fleet carrier...
 
Sooo... is this intentional, or a bug introduced recently, any way we can get some clarification? I can't seem to find any solid info on the subject.
 
old, been there for a while, its been said its because of congestion. like I said, stop and restart. It makes sense, there are far more stupid important bugs than this. its a feature.
 
I'm in the middle of nowhere. I seriously doubt there is more than five people within 1000LY of my position.

It's got nothing to do with how many people in your location or area, the carrier move is a database update, there's only one database, so when the number of carriers jumping exceeds the amount of time they have for updates to the database then the time extends, this applies to carriers anywhere in the galaxy! Don't see how hard this is to understand but so many people get in a tizzy about it!
 
Thank you :)

This sounds exactly like something Frontier might say, but honestly it smacks of either 1) poor / non optimisation, or 2) maybe they have a yellow i386 in a leaky shed out back doing the calculations and server updates.

They already had fifteen minutes to do the relevant changes to digital assets in digital locations for each fleet carrier...

Because it's actually what happens? They don't have 15 minutes for each carrier, they have 15 minutes for all the carriers that move at the same time, if they needed 15 minutes for each carrier then each person would get 15 minutes added to their jump.
 
Before they brought this in, what would happen if too many people tried to jump at once was that the servers would fall over, inconveniencing everyone. Having only the people actually jumping be inconvenienced with a slightly longer timer is a big improvement on that.
 
Before they brought this in, what would happen if too many people tried to jump at once was that the servers would fall over, inconveniencing everyone. Having only the people actually jumping be inconvenienced with a slightly longer timer is a big improvement on that.
Many people tried to jump at the same time when they introduced the fleet carrier interiors. I was few minutes late and my jump time was 1.5 hours.
 
Because it's actually what happens? They don't have 15 minutes for each carrier, they have 15 minutes for all the carriers that move at the same time, if they needed 15 minutes for each carrier then each person would get 15 minutes added to their jump.
Yeah, this is a big pile of proverbial.

Like Dolsvt00 mentioned, I got a 40 minute timer, cancelled and rebooked within a minute and now it's 15 minutes. Sure, if lots of people are scheduling jumps, then put me in a queue and add ten seconds for each person. Because the server can handle it right, I just demonstrated that by rebooking it.

Turns out, like a lot of things Frontier, it's just badly coded. All the fanboi's can wail I'm being unfair all they want, but if I book it and it's 40 minutes for server load, and then I rebook it a minute later and it's 15, then the system is broken in many and varied ways.
 
Back
Top Bottom