@Someone or whoever can poke the one to fix the infinite loading screens in Cyrodiil

Docmandu · July 2017

Un-b-F'ing-lievable .. great start today... 30 minute queue wait.. get in Cyrodiil, first teleport I try to do... infinite loading screen!

Docmandu · July 2017

Back to #32 in the queue... weren't games supposed to be fun? relaxing?

Docmandu · July 2017

And yet more evenings with endless load screens in Cyrodiil that ZOS will just ignore,

Docmandu · July 2017

Sigh... more server crashing weekends... with NO RESPONSE from ZOS whatsoever in sight

Docmandu · July 2017

Another another EU Cyrodiil crash that ZOS will ignore

Docmandu · July 2017

sigh...

Docmandu · July 2017

Thank you for waiting 30 minutes in line to play our game... now... please wait another 30 minutes

gp1680 · July 2017

Docmandu wrote: »

Thank you for waiting 30 minutes in line to play our game... now... please wait another 30 minutes

I've got your back bud. Keep up the pressure. Sometime before I die, I'd like to play a session in Cyrodiil without a crash or loading screen.

Docmandu · July 2017

And there's the 2nd infinite loading screen ... time to go do something else... isn't Albion Online about to release?! hmm

Docmandu · July 2017

More days staring at a loading screen.... @ZOS_BrianWheeler ain't it time to at least COMMUNICATE with your playerbase?!

Docmandu · July 2017

And yet more.. get into Cyro after long queue.. first teleport you do, infinite loading screen and back in a #100 queue... and still after 3 months nothing from ZOS

Docmandu · July 2017

O.M.F***.God... 189 queue... get in.. first port... loading screen of death... F you ZOS!

Docmandu · July 2017

And again...

Docmandu · July 2017

Weekends or weekdays.. no matter... at least the game is consistent... showing infinite loading screens for more than 3 months with ZOS ignoring it completely.

Thank you @ZOS_GinaBruno @ZOS_BrianWheeler

ZOS_JessicaFolsom · July 2017

Hi @Docmandu - responding here based on what you and a few others posted in this thread. We shared your concerns and frustrations with the team and provided some examples (thanks again for the detail and links.) They're digging into loading screen logs going as far back as the beginning of May. Are you able to say if the crashes you've been experiencing are consistently tied to loading screen time-outs? Or are they separate?

Docmandu · July 2017

@ZOS_JessicaFolsom

Just FYI... currently stuck in a loading screen after getting killed and releasing (ie. game trying to put me in a different grid in cyrodiil from where I died).

My client is currently connected to 2 IP's while the loading screen is still showing:
- 159.100.232.160 port 24505
- 159.100.232.135 port 24102

both IP's can also be pinged without problems:

C:\> ping 159.100.232.160

Pinging 159.100.232.160 with 32 bytes of data:
Reply from 159.100.232.160: bytes=32 time=16ms TTL=55
Reply from 159.100.232.160: bytes=32 time=18ms TTL=55
Reply from 159.100.232.160: bytes=32 time=18ms TTL=55

Ping statistics for 159.100.232.160:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 18ms, Average = 17ms
Control-C
^C
C:\>ping 159.100.232.135

Pinging 159.100.232.135 with 32 bytes of data:
Reply from 159.100.232.135: bytes=32 time=21ms TTL=55
Reply from 159.100.232.135: bytes=32 time=16ms TTL=55
Reply from 159.100.232.135: bytes=32 time=20ms TTL=55
Reply from 159.100.232.135: bytes=32 time=20ms TTL=55

Ping statistics for 159.100.232.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 21ms, Average = 19ms

As for the link between crashes and loading screen time-outs.. it's 2 different issues:

- when Cyrodiil crashes (like yesterday on PC/EU Vive), everybody is kicked to the character selection screen. You can usually login again if you wait a few seconds. Most of the time you log back into Cyrodiil, with the entire map in a calm state (ie no fight markers).. and people in zone chat asking if they were alone in getting kicked.. or people that already know the drill asking if the server crashed yet again (which is usually the case.. as it also involves rollbacks.. ie if you are somewhere in the middle of nowhere in Cyrodiil, when you log back in, you will be in the spot you were couple of minutes before the crash).

- then there's the other issue, which is the infamous infinite loading screen bug.. this one happens if you teleport via wayshrines, when you release after death or when a keep upgrades and you get a loading screen due to this. In other words, whenever you get a loading screen in Cyrodiil, the chance is high that it will never go away again.

Useful to know.. the TCP/IP connections towards the server remain, and pinging the server IP's you're currently connected to also works fine, in other words.. the server machines themselves are still reachable.. so it's not a routing / network issue.

I get the impression that the server crashes have been a bit less since the last patch.. but that might just be sheer luck. AFAIK the zone has only crashed once since the last incremental patch (ie. yesterday evening PC/EU Vivec)

NOTE: started typing when the loading screen first showed.. and now when I'm done typing this entire post, it's still showing the loading screen.. probably 5-8 minutes have passed. Doesn't appear the client even has a timeout. I'll keep it running to see if it ever times out.

Docmandu · July 2017

Should add.. I've never had issues in PvE lands.. then again.. I don't spend much time in the PvE zones.

BTW: loading screen is still showing. Just to help debug this.. checked with wireshark if there was still data going back and forth between my PC and the server.. which appears to be the case:

0.000000 159.100.232.160 -> 192.168.2.16 TCP 24505 > 58497 [PSH, ACK] Seq=1 Ack=1 Win=126 Len=128 TSval=817866870 TSecr=19470686
0.050867 192.168.2.16 -> 159.100.232.160 TCP 58497 > 24505 [ACK] Seq=1 Ack=129 Win=16652 Len=0 TSval=19472462 TSecr=817866870
0.390783 159.100.232.160 -> 192.168.2.16 TCP 24505 > 58497 [PSH, ACK] Seq=129 Ack=1 Win=126 Len=70 TSval=817867261 TSecr=19472462
0.440721 192.168.2.16 -> 159.100.232.160 TCP 58497 > 24505 [ACK] Seq=1 Ack=199 Win=16634 Len=0 TSval=19472852 TSecr=817867261
3.149184 159.100.232.160 -> 192.168.2.16 TCP 24505 > 58497 [PSH, ACK] Seq=199 Ack=1 Win=126 Len=27 TSval=817870018 TSecr=19472852
3.178260 192.168.2.16 -> 159.100.232.160 TCP 58497 > 24505 [PSH, ACK] Seq=1 Ack=226 Win=16627 Len=35 TSval=19475590 TSecr=817870018
3.237456 159.100.232.160 -> 192.168.2.16 TCP 24505 > 58497 [ACK] Seq=226 Ack=36 Win=126 Len=0 TSval=817870108 TSecr=19475590
5.020513 159.100.232.160 -> 192.168.2.16 TCP 24505 > 58497 [PSH, ACK] Seq=226 Ack=36 Win=126 Len=498 TSval=817871890 TSecr=19475590
5.071159 192.168.2.16 -> 159.100.232.160 TCP 58497 > 24505 [ACK] Seq=36 Ack=724 Win=16503 Len=0 TSval=19477483 TSecr=817871890
8.151654 159.100.232.160 -> 192.168.2.16 TCP 24505 > 58497 [PSH, ACK] Seq=724 Ack=36 Win=126 Len=27 TSval=817875022 TSecr=19477483
8.171632 192.168.2.16 -> 159.100.232.160 TCP 58497 > 24505 [PSH, ACK] Seq=36 Ack=751 Win=16496 Len=35 TSval=19480583 TSecr=817875022
8.190439 159.100.232.160 -> 192.168.2.16 TCP 24505 > 58497 [ACK] Seq=751 Ack=71 Win=126 Len=0 TSval=817875061 TSecr=19480583
8.242958 159.100.232.160 -> 192.168.2.16 TCP 24505 > 58497 [PSH, ACK] Seq=751 Ack=71 Win=126 Len=63 TSval=817875113 TSecr=19480583
8.293737 192.168.2.16 -> 159.100.232.160 TCP 58497 > 24505 [ACK] Seq=71 Ack=814 Win=16480 Len=0 TSval=19480705 TSecr=817875113

0.000000 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=1 Win=16429 Len=0 TSval=19488694 TSecr=817883052
0.065969 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=1 Ack=1 Win=44 Len=42 TSval=817883169 TSecr=19488694
0.117564 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=43 Win=16418 Len=0 TSval=19488812 TSecr=817883169
0.124558 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=43 Ack=1 Win=44 Len=34 TSval=817883227 TSecr=19488694
0.174628 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=77 Win=16410 Len=0 TSval=19488869 TSecr=817883227
0.202628 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=77 Ack=1 Win=44 Len=29 TSval=817883306 TSecr=19488869
0.252718 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=106 Win=16403 Len=0 TSval=19488947 TSecr=817883306
0.261492 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=106 Ack=1 Win=44 Len=34 TSval=817883364 TSecr=19488869
0.311758 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=140 Win=16394 Len=0 TSval=19489006 TSecr=817883364
0.320335 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=140 Ack=1 Win=44 Len=34 TSval=817883423 TSecr=19488947
0.370265 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=174 Win=16386 Len=0 TSval=19489065 TSecr=817883423
0.398678 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=174 Ack=1 Win=44 Len=20 TSval=817883502 TSecr=19489065
0.449011 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=194 Win=16381 Len=0 TSval=19489143 TSecr=817883502
0.457176 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=194 Ack=1 Win=44 Len=34 TSval=817883560 TSecr=19489065
0.508431 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=228 Win=16372 Len=0 TSval=19489203 TSecr=817883560
1.375376 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=228 Ack=1 Win=44 Len=58 TSval=817884478 TSecr=19489203
1.414084 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=286 Ack=1 Win=44 Len=343 TSval=817884517 TSecr=19489203
1.414470 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=629 Win=16652 Len=0 TSval=19490109 TSecr=817884478
1.550890 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=629 Ack=1 Win=44 Len=31 TSval=817884654 TSecr=19490109
1.601964 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=1 Ack=660 Win=16644 Len=0 TSval=19490296 TSecr=817884654
1.614924 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [PSH, ACK] Seq=1 Ack=660 Win=16644 Len=32 TSval=19490309 TSecr=817884654
1.633481 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [ACK] Seq=660 Ack=33 Win=44 Len=0 TSval=817884736 TSecr=19490309
1.708175 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=660 Ack=33 Win=44 Len=24 TSval=817884811 TSecr=19490309
1.758630 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=33 Ack=684 Win=16638 Len=0 TSval=19490453 TSecr=817884811
1.864706 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=684 Ack=33 Win=44 Len=85 TSval=817884968 TSecr=19490453
1.914273 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=33 Ack=769 Win=16617 Len=0 TSval=19490609 TSecr=817884968
2.001423 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=769 Ack=33 Win=44 Len=29 TSval=817885104 TSecr=19490609
2.052419 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=33 Ack=798 Win=16609 Len=0 TSval=19490747 TSecr=817885104
^C 2.059859 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=798 Ack=33 Win=44 Len=31 TSval=817885163 TSecr=19490609
2.079652 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=829 Ack=33 Win=44 Len=255 TSval=817885182 TSecr=19490747
2.080078 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=33 Ack=1084 Win=16538 Len=0 TSval=19490774 TSecr=817885163
2.157882 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=1084 Ack=33 Win=44 Len=29 TSval=817885261 TSecr=19490774
2.208619 192.168.2.16 -> 159.100.232.135 TCP 58577 > 24102 [ACK] Seq=33 Ack=1113 Win=16531 Len=0 TSval=19490903 TSecr=817885261
2.508199 159.100.232.135 -> 192.168.2.16 TCP 24102 > 58577 [PSH, ACK] Seq=1113 Ack=33 Win=44 Len=42 TSval=817885611 TSecr=19490903

Which explains why at least the server isn't killing the connection. So if I'd have to wager a guess.. I'd say this is likely to be a bug in the client.

Docmandu · July 2017

15 minutes later.. the loading screen is still showing... so it's safe to say it's indeed infinite

and neither the server nor the client will terminate the connection. Time to kill the process myself.

Berenhir · July 2017

@ZOS_JessicaFolsom
Important to note that you are already visible at the point where you ported to when you get an infinite loading screen. It's just as if the game would forget to close the loading screen and fire up the ui.
The loading screen issue is definitely tied to playing in a group - I cannot remember ever getting it solo. The bigger the group the higher the probability for ILS.
Only thing that really helps is killing the game via task manager and restarting. But that is no guarantee it won't happen again. Maybe it's tied to the invisible group member bug?

Server crashes are indeed a different thing. They usually happen when factions stack in one keep and clash. Everybody on the server gets a freeze, loading screen and is directly boited character login screen. It's rng if you pop out in Cyrodiil or not afterwards.

Sometimes one of the scrolls is reset after server crash, even if the rollback is only 10 minutes and you didn't have the scroll for hours.

Docmandu · July 2017

Berenhir wrote: »

The loading screen issue is definitely tied to playing in a group - I cannot remember ever getting it solo.

As I mentioned in the other thread... I NEVER group in Cyrodiil, so it's definitely also happening if you are not grouped.

mook-eb16_ESO · July 2017

I can tell you this is group related bug only. never get this anymore since I stopped playing with groups.

Docmandu · July 2017

mook-eb16_ESO wrote: »

I can tell you this is group related bug only. never get this anymore since I stopped playing with groups.

Sigh.. what is it with people... like I said the post before your post.. I NEVER am grouped in Cyrodiil, ever... this is NOT a group (only) issue.

Berenhir · July 2017

Docmandu wrote: »

mook-eb16_ESO wrote: »

I can tell you this is group related bug only. never get this anymore since I stopped playing with groups.

Sigh.. what is it with people... like I said the post before your post.. I NEVER am grouped in Cyrodiil, ever... this is NOT a group (only) issue.

Maybe only the frequency/probability rises with groupsize? Or there are several issues with the same symptoms...

Docmandu · July 2017

Berenhir wrote: »

Docmandu wrote: »

mook-eb16_ESO wrote: »

I can tell you this is group related bug only. never get this anymore since I stopped playing with groups.

Sigh.. what is it with people... like I said the post before your post.. I NEVER am grouped in Cyrodiil, ever... this is NOT a group (only) issue.

Maybe only the frequency/probability rises with groupsize? Or there are several issues with the same symptoms...

That I can't say. Happens frequently enough when solo... all my posts in this thread are evidence of that

Zaldan · July 2017

Docmandu wrote: »

Berenhir wrote: »

The loading screen issue is definitely tied to playing in a group - I cannot remember ever getting it solo.

As I mentioned in the other thread... I NEVER group in Cyrodiil, so it's definitely also happening if you are not grouped.

same, always solo these days and plenty of loading screens that last until I pull the plug after 5mins

TazESO · July 2017

Omg, haven't been in Cyrodiil in months. I was hoping this was fixed before the Midyear Mayhem event starts. There going to be some frustrated peeps....

gp1680 · July 2017

Berenhir wrote: »

@ZOS_JessicaFolsom
Important to note that you are already visible at the point where you ported to when you get an infinite loading screen. It's just as if the game would forget to close the loading screen and fire up the ui.
The loading screen issue is definitely tied to playing in a group - I cannot remember ever getting it solo. The bigger the group the higher the probability for ILS.
Only thing that really helps is killing the game via task manager and restarting. But that is no guarantee it won't happen again. Maybe it's tied to the invisible group member bug?

Server crashes are indeed a different thing. They usually happen when factions stack in one keep and clash. Everybody on the server gets a freeze, loading screen and is directly boited character login screen. It's rng if you pop out in Cyrodiil or not afterwards.

Sometimes one of the scrolls is reset after server crash, even if the rollback is only 10 minutes and you didn't have the scroll for hours.

If it helps troubleshoot, sometimes if another player sends me a trade request or whisper, it brings me out of loading screen.

Yngol · July 2017

ZOS_JessicaFolsom wrote: »

Hi @Docmandu - responding here based on what you and a few others posted in this thread. We shared your concerns and frustrations with the team and provided some examples (thanks again for the detail and links.) They're digging into loading screen logs going as far back as the beginning of May. Are you able to say if the crashes you've been experiencing are consistently tied to loading screen time-outs? Or are they separate?

Could you take a look at infinite loading screens in battle grounds as well? They kill quite a few games, and give us deserters penalties

RMerlin · July 2017

Docmandu wrote: »

Useful to know.. the TCP/IP connections towards the server remain, and pinging the server IP's you're currently connected to also works fine, in other words.. the server machines themselves are still reachable.. so it's not a routing / network issue.

When I took a closer look at it myself, I noticed that there were some very low-bandwidth traffic still occuring, a few packets every few seconds. Might be connection attempts or some kind of keep-alive packet.

Also, these tend to happen more often when Cyrodiil is being laggy due to high population/intense zerging happening.

Docmandu · July 2017

rmerlb16_ESO wrote: »

Might be connection attempts

It's all the same stream.. if it were connection attempts, the port numbers would change (and you would see SYN packets)