Forums » Bugs
Post your cloud bugs here. Hopefully the devs will look at it.
Higher ping than usual.
I am usually in the 60s- 70s, and my reg on the cloud server is 120-130. I live in New York, Brooklyn.
On the plus side, the un-station sectors run like liquid now.
I am usually in the 60s- 70s, and my reg on the cloud server is 120-130. I live in New York, Brooklyn.
On the plus side, the un-station sectors run like liquid now.
Missions aren't working properly, we are working on a fix for that right now.
And yeah, pings seem to be much higher.
And yeah, pings seem to be much higher.
Pings are higher for people further away. In San Francisco I was seeing ~50ms, another nearby person was seeing ~42ms. People on the east coast will see higher pings than usual, since they're traversing several thousand more miles. People on the west coast will see lower ping.
This cloud instance is based on Oregon, just as a lower-cost testbed. If we ran it from the east coast, then pings would be different, etc.
This cloud instance is based on Oregon, just as a lower-cost testbed. If we ran it from the east coast, then pings would be different, etc.
First bug:
I died in Bractus due to huge lad and for 10 minutes i coudn't log in anymore . The client was stuck at Entering Universe .
Second bug:
I was in Odia H-6 mining . Tried to dock . The client just logged me out . Logged back in , tried to dock again . Again i was logged out . Jumped out of the sector and moved to another sector.
I died in Bractus due to huge lad and for 10 minutes i coudn't log in anymore . The client was stuck at Entering Universe .
Second bug:
I was in Odia H-6 mining . Tried to dock . The client just logged me out . Logged back in , tried to dock again . Again i was logged out . Jumped out of the sector and moved to another sector.
Fixed the Entering Universe/warp/jump stuck problems.
Ya, I'd say the ping times are different. I went from 32ms up to 99ms.
Plus I had to cancel logging in twice cause I was stuck at Entering the Universe (loaded about half way) for 3-4 mins.
Plus I had to cancel logging in twice cause I was stuck at Entering the Universe (loaded about half way) for 3-4 mins.
vskye, we fixed the stuck problem a few minutes ago.
Ya, I noticed Ray. :)
Thanks.
Good thing to test for sure.
Thanks.
Good thing to test for sure.
missions bugs, fixed
unable to dock/login, fixed
from Brazil, ping raised today from average 180~200 to 240~260.
If you remain in cloud, let's call it a NEBULA... s space cloud...
unable to dock/login, fixed
from Brazil, ping raised today from average 180~200 to 240~260.
If you remain in cloud, let's call it a NEBULA... s space cloud...
Normal ping: 54ms
New ping: 132ms
Couple that With fighting an Aussie who is 300 plus, almost unplayable
New ping: 132ms
Couple that With fighting an Aussie who is 300 plus, almost unplayable
So I already explained the ping times above, and on General. Is anyone seeing any problems that are not directly related to the speed of light?
I was instructed to post numbers on the forum. No unfixed issues besides the connection for me.
my ping actually improved 20ms, I was trying from the tablet over wireless which explained the problems initially. Azurea lagged extremely badly but that's normal for him
Nothing unrelated to the internet backbone to report. I'd tried inventory work, pulling up info for missions, chat, guild (and various) commands, buying ships, etc which weren't related to the client only.
Knowing your chosen test region was US Pacific Coast explains a lot for me. I live in Maryland. To be honest, if you utilized the US Midwest region, you'd see similar performance to using your in house servers for hosting. Most US East/West traffic runs through the backbone router in Chicago.
http://internettrafficreport.com (to help understand how adding so many additional hops is painful - check packet responses on the backbone routers)
Knowing your chosen test region was US Pacific Coast explains a lot for me. I live in Maryland. To be honest, if you utilized the US Midwest region, you'd see similar performance to using your in house servers for hosting. Most US East/West traffic runs through the backbone router in Chicago.
http://internettrafficreport.com (to help understand how adding so many additional hops is painful - check packet responses on the backbone routers)
The player activity graph went on the blitz. I hope that means that it only calculates activity on the dev's hardware and not the cloud and it's not broken >.>
Knowing your chosen test region was US Pacific Coast explains a lot for me. I live in Maryland. To be honest, if you utilized the US Midwest region, you'd see similar performance to using your in house servers for hosting.
Yes, we know. Like I wrote above and on General, it was a cost decision. Not all locations cost the same.
Most US East/West traffic runs through the backbone router in Chicago.
No.. that is not true at all.
(to help understand how adding so many additional hops is painful - check packet responses on the backbone routers)
No. Hopcount has almost nothing to do with latency, especially in the last 15 years of layer-3 switching. Transit length is what induces latency. Distance. "C", or the speed of light.
Let's please stick to game-related reports. Thanks.
The player activity graph went on the blitz. I hope that means that it only calculates activity on the dev's hardware and not the cloud and it's not broken >.>
Thanks for pointing that out.. we'll probably not fix that for today, but will make a note of it.
Yes, we know. Like I wrote above and on General, it was a cost decision. Not all locations cost the same.
Most US East/West traffic runs through the backbone router in Chicago.
No.. that is not true at all.
(to help understand how adding so many additional hops is painful - check packet responses on the backbone routers)
No. Hopcount has almost nothing to do with latency, especially in the last 15 years of layer-3 switching. Transit length is what induces latency. Distance. "C", or the speed of light.
Let's please stick to game-related reports. Thanks.
The player activity graph went on the blitz. I hope that means that it only calculates activity on the dev's hardware and not the cloud and it's not broken >.>
Thanks for pointing that out.. we'll probably not fix that for today, but will make a note of it.
If I'm homed at the capship station and die the game complains that I'm not allowed to enter and re homes me. I can still dock with the station.
This worked fine a few days ago.
This worked fine a few days ago.
I can't take any missions in Latos M-7 but I cant take them anywhere else
Thanks TRS. (I assume you mean you can take them elsewhere)