16.01 Update Notes

[Marvin the Martian]

I'd imagine that carrier jump times depends on database transactions on the server infrastructure, and not on the quality of a particular client connection..

Then explain how two people connected during the same period of time have completely different outcomes?

Surely you're not suggesting that I'm just "lucky" and get "good database transactions" every single time I jump for days while he gets crap database transactions every single time he jumps during the same period of time.

If it were pot luck for both of us, crap sometimes and good others, I could buy that. It would make sense. But that's not what's happening.

 

[Marvin the Martian]

OK, looks like @Jack Winter may be right after all.

I just set a jump to Drojeae SO-U b22-1, which is on the outskirts of the bubble, roughly 4,000 LY out of Deciat where I'm heading. When I hit plot the timer said 17:45. I cancelled the jump, replotted it and it came back up as 17:20.

So it appears like the closer you get to other carriers, the longer the time goes up for the jump. We'll see the next time I jump in roughly 20 minutes or so if it goes up further or back to normal, but that's extremely odd that I do 40 jumps in a row all at 15:30 and the instant I hit the outskirts of the bubble it shoots up 2 minutes.

 

[Jack Winter]

Then explain how two people connected during the same period of time have completely different outcomes?

Surely you're not suggesting that I'm just "lucky" and get "good database transactions" every single time I jump for days while he gets crap database transactions every single time he jumps during the same period of time.

If it were pot luck for both of us, crap sometimes and good others, I could buy that. It would make sense. But that's not what's happening.

How about issues with the local Amazon infrastructure, delays in database transactions and replication between Amazon data centers, or even just a bug that occurs in some circumstances and not in others.

I think it's pretty clear that we got the long jump times as there is a limit to how fast the databases can be written to and replicated to all local data centers used by Amazon/Frontier. It's a limitation/problem on the server side and not a question of the quality of individual Internet connections.

At least that is what seems logical to me. I don't see why having a dodgy connection between a client and a server would have any impact on how fast the database servers can process transactions and replicate to all applicable data centers.

 

[Marvin the Martian]

Just plotted to Droju AR-C d26 and I'm right back to 15:45.

 

[Angus McSix]

This carrier jump discussion is fine and all,

but I still want to have the ability to plot routes with boosted FSD back.

 

[aRJay]

FWIW, I've had a very stable connection for years, but lately I've been seeing quite a lot of coloured snakes..

Until a week or so ago I would get one CTD per session while flying or hovering over a planet bio hunting, then they went away. This week they have been back and in addition one day I actually got a coloured Adder the first snake error message of any kind I have seen in months.

As to the numbers thanks to everyone who pointed out indicators other than stats showing reduced participation.

 

[GraphiteGB]

The CG user count is crap.
So that will smeg over the user count issues.
And the FC can jump into CG target systems still, showing the CG users a still way low, as the systems for the combat CG is still not full.

 

[angusmadmac1]

We some issues with FC jump in the past when we had many more people playing and also with different platforms .
The CG numbers are down the leader boards are down even losing consoles as they are now on legacy . So why the question is why is it happening with fewer participants, the "working as intended" is just " we don't know and we can't investigate because we don't have the staff" sort of answe

 

[JR250]

I believe this is an old bug, or at least not introduced with today's fix. I don't have this entirely confirmed but I've made it work if I remember to change the Nav panel tab to "Transactions" or "Contacts", instead of "Navigation". It doesn't like to be stared at ;-)

Replying to myself for posterity:
Nope, switching to a different tab of the Nab panel does not prevent having your destination target jump to a random one. I must have been lucky that after selecting my target and changing tabs to "contacts", it never had jumped. Today, however, I saw that happen twice while at the CG.

For context, the issue is that you select your target destination on the Nav panel and as soon as you FSD jump, your target destination changes on its own to a seemingly random one from the list. Super annoying as you're working a RES and need to frequently jump back to your carrier for RRR.

To reiterate, this is an old issue and not something introduced by Update 16.