This is also true... I've been getting hangs from low waking and stutters and crashes as well even in low pop. systems. Just not nearly as much as in hi pop.I'm not sure if this is directly related to Carriers. The other day I had a lot of orange sidewinder errors, but I was just jumping/cruising in low traffic systems (no carriers around at all). The same day, I was in the icebox, and had no issues.
But today, I was getting weird screen freezes jumping in and near the high selling LTD station. Sometimes it would freeze for 10-15 seconds during the jump animation..like the animation itself completely froze. But I ended up successfully jumping into the system (and I got pirated by a couple CODE pirates, so instancing was working, more or less). So maybe it's indirectly related to carriers, but it doesn't seem to be a 1-1 correlation.
I've had a lot of weird 45+ second hangs lately jumping in/out of SC
Me too. FD sould test their **** on less than ideal networking situations.
*gear
PS4 here as well, having issues in col 285 sector that everyone is at. Many Engineers spots are similar. Blaming players is not the answer if FDev is doing that.Not having problems on PS4 at the moment and was in a Tritium buy system today very infrequent lag on low wake
Yep, seen that on XB too. Not everytime but often enough to be noticeable
Not so prevalent on PC (slightly longer SC transition timers on PC, but not as insanely long as it sometimes happens on XB)
Similar experience here... I tried port forwarding a few years ago and never went back. I very rarely experience any issues anywhere in the game. only have the standard 12Mbs download and 1Mb uploadAll I can tell you is that I've had some connection issues in the past, especially after updates, but after setting up port forwarding I rarely experience them anymore.
In Carrier heavy systems I don't notice any problems.
Really?? If you have any more details on the theory of this i'd be interested.I don't use port forwarding but yet I can see human players. ED's network code requires at least one commander in any given instance who has an activate port forwarding, so his machine can act as a host to this instance. That said, especially in crowded systems, where the possibility of being instanced with such a player is much higher than in low frequency systems, such an advice won't help much.
Getting a full hand of it right now.
Started the game on XB
Started the game on PC
PC logs in, XB turning a red Cutter on the screen
PC i plot a jump from the carrier management screen, 1 minute later XB logs in finally
XB opens the galaxy map -> Orange sidewinder
XB reconnects > Open galaxy map > Mauve Adder
XB reconnects > Taupe Cobra
XB quit the game > restart > reconnect> Mauve Adder directly from the hangar screen
PC still fine, jump scheduled in 3 minutes 40 seconds.
XB reconnect (takes a long time as every other attempt above) PC carrier honks letting me know the services are suspended prior to jump.
XB still showing a red cutter on the screen (stuck but not dead) - i forsee it will eventually connect then crash with a Mauve Adder right from the hangar screen
PC carrier jumps in 5.. 4.. 3.. 2.. 1
XB still shows a stuck red Cutter on the screen
@Bruce Garrido @Tim Smith
Guys please, can you give the XB support team a sign to check the platform?
Yep, theres clearly something in the console programming or servers that we are on that isn't playing ball!
That's what users are for.LOL, they never test anything anywhere
Egad, that's one heck of a bandwidth you have there! I haven't ever seen a sub 10mS ping time outside of an intranet!It's happening on PC as well, the problem is definitely server-side:
View attachment 180516
Egad, that's one heck of a bandwidth you have there! I haven't ever seen a sub 10mS ping time outside of an intranet!
The gravitational pull of all the fleet carriers in the Icebox is causing the system to collapse in on itself like a black hole!The Fleet Carrier Event Horizon...
Instructions unclear. Router is now in space.Can't believe this, 3 pages and yet nothing.
Fine.
Did you try vacuuming your router?