LOAD SCREENS!!!

saruhrose1

ELDER lagload screensssss offline...

UppGRAYxDD

Hutch679 wrote: »

What is happening... I have to quit out and restart after every load screen in cyrodiil....

Same here @ZOS_GinaBruno @ZOS_KaiSchober @ZOS_JessicaFolsom @ZOS_GaryA @ZOS_TristanK

Almost everytime if you travel to a keep or respawn at a keep...endless load screen.

ktdotexe

I hate to add to this and complain, but I play on the PS4 Europe server and have NEVER had any problems or experienced the lag and loading screens since this latest update. I can't even play PVP; anytime I die, if I try to respawn anywhere I get stuck with infiite loading screens. If I try to respawn from keep to keep, same problem. I had to close and restart the game over 15 times to the point I just gave up.

Like I said, never had this problem before so it's definitely not my connection or console. Cyrodil was a mess last night! Really hoping they fix it soon.

Defilted

In Cyro last night XBOX NA. I had to restart the xbox every time you blood spawned to a keep or used a transitis. There was a infinite load screen every time. After 10 to 12 restarts I just turned the xbox off on a infinite load screen. I had one attempt from a keep to the eastern gate that did not get stuck in a load screen.

I would say that PVP at this time is not playable.

You can horse travel everywhere and never die, then you would be able to play. Really do not mind running around with my horse, but I have never not died.

uzbachchi

This was happening to people I was running trials with last night, we did the new one in Clockwork City followed by Maw of Lorkhaj. Maw was by far the worst. Anyone doing the running on the final boss would get stuck in a loading screen and have to restart the game if they died. Several times people got stuck trying to go through doors and had to reload game. We finally had to give up on the final Maw boss. Not only did players have to reload on death every time, the cats doing the ritual were buggy and weren't spawning properly so we wiped every attempt. PS4 NA

Hutch679

Elder restart online

dotme

I genuinely feel bad for the devs on this one. I don't know what testing was done prior to launch, but it's odd that PC got the CWC update a couple of weeks earlier and there didn't seem to be any reports of infinite load screens in PvP etc.

I can only speak for PS4 NA but the impact this has had on PvP population appears to be catastrophic. At first I thought maybe everyone was just doing CWC instead of Cyrodiil but a quick glance through my guild rosters seems to tell a story of game abandonment instead. Such a shame.

What long term effect something like this will have I don't know, but it can't be good. PVP was already down to just one pop-locked campaign on PS4 NA, and now even that campaign feels deserted. If this is a client-side problem that can't be addressed quickly with a server patch, I'm a bit concerned that PvP on PS4 NA may not fully recover from this.

Bird298

I now can’t log in to the game at all on a Mac client. It crashes and I find myself dumped back at the Mac OS log in screen. The EOS music continues to play but nothing is visible. The game is unplayable.

NewBlacksmurf

I️ know they want to keep things set up a certain way but maybe....just maybe it’s worth considering a huge or major change to how campaigns, One Tamriel shared zones and phasing is set up as well as what can be dumped when we hit a load screen. There is also the bank, guild bank issues and phasing issues within groups for PvP and PvE.

I’m getting at their mega server design seems unable to sustain this current setup. We constantly see crashing or unplanned down time. It’s been this way for 2 years....

Maybe 2018 would be a good target for such a major change.

lazerlaz

When ZOS claims they've added performance upgrades.... What in the bloody heck are they talking about? Everytime they say they've made improvements things get worse. Seriously, what the @#$<#!?

mdylan2013

This has pretty much killed pvp on ps4 eu. GG ZOS.

Maybe now you'll start to consider beta testing on consoles.

OutLaw_Nynx

regime211 wrote: »

This is frustrating it's been going on for 3 years come on zenimax, enough is ENOUGH ALREADY! Forget the DLCS forget the crown store please fix these issues.

Apache_Kid

dotme wrote: »

I genuinely feel bad for the devs on this one. I don't know what testing was done prior to launch, but it's odd that PC got the CWC update a couple of weeks earlier and there didn't seem to be any reports of infinite load screens in PvP etc.

I can only speak for PS4 NA but the impact this has had on PvP population appears to be catastrophic. At first I thought maybe everyone was just doing CWC instead of Cyrodiil but a quick glance through my guild rosters seems to tell a story of game abandonment instead. Such a shame.

What long term effect something like this will have I don't know, but it can't be good. PVP was already down to just one pop-locked campaign on PS4 NA, and now even that campaign feels deserted. If this is a client-side problem that can't be addressed quickly with a server patch, I'm a bit concerned that PvP on PS4 NA may not fully recover from this.

I don't want to say that it's clear they didn't do any testing on consoles before the patch but I don't know how you can claim they did. I realised they was a problem when I got stuck in 3 infinite load-screens trying to start the CWC quest in Deshaan after my first 30 minutes online. This isn't just in PvP it's in PvE as well We KNOW they didn't test PvP since it would've taken them all of dying once to realize the issue.

Docmandu

At least before, they could blame addons, virus scanners, crap installed on your PC, ... pity for them they can't use that excuse anymore since consoles now have the same issues.

next up... have you rebooted your router yet?

Koolio

ZOS_GinaBruno wrote: »

Thanks all, we're actively looking into this on all platforms.

Any news yet? This is a major issue.

Ballcap

The load screens are bugged for me too. I cannot play the game.

dotme

Apache_Kid wrote: »

...I don't want to say that it's clear they didn't do any testing on consoles before the patch but I don't know how you can claim they did. I realised they was a problem when I got stuck in 3 infinite load-screens trying to start the CWC quest in Deshaan after my first 30 minutes online. This isn't just in PvP it's in PvE as well We KNOW they didn't test PvP since it would've taken them all of dying once to realize the issue

You're not wrong. But then we would have to believe that a multi-million dollar company didn't bother to load-test their console versions on a flagship product, which would be unbelievable. I'm still hoping it's a server-side fix because if it's not and this carries on for weeks, they may have done irreversible damage to their game and its revenue.

BalticBlues

PvP is unplayable.
If you do not zerg, you can only play "loading screens".

This patch has not been tested for PvP at all.

Apache_Kid

dotme wrote: »

Apache_Kid wrote: »

...I don't want to say that it's clear they didn't do any testing on consoles before the patch but I don't know how you can claim they did. I realised they was a problem when I got stuck in 3 infinite load-screens trying to start the CWC quest in Deshaan after my first 30 minutes online. This isn't just in PvP it's in PvE as well We KNOW they didn't test PvP since it would've taken them all of dying once to realize the issue

You're not wrong. But then we would have to believe that a multi-million dollar company didn't bother to load-test their console versions on a flagship product, which would be unbelievable. I'm still hoping it's a server-side fix because if it's not and this carries on for weeks, they may have done irreversible damage to their game and its revenue.

Yeah Idk I am obviously just making assumptions but that's what it seems like. I just want it to be fixed at this point. The crashes I had before this were really annoying but nothing like this.

Kuramas9tails

PVP is UNPLAYABLE!

Vaoh

BalticBlues wrote: »

PvP is unplayable.
If you do not zerg, you can only play "loading screens".

This patch has not been tested for PvP at all.

This is not PvP-specific. It's a mess in trials too (especially Maw of Lorkhaj). Something obviously went badly wrong in their console patch. It's astounding how this was not noticed through testing first.

Defilted

For all those people that say this was not tested. I can safely say you do not develop/deploy or L3 support software.

Common Software issues/practices
-Development testing and full regression testing(By Q/A) is done in a lab environment. This is standard across the board for every software company I have ever worked for.
-Once a piece of software or suite is moved onto a production environment you will always encounter a problem/s that you did not see in testing and cannot reproduce on a non-production environment.
- No lab environment no matter how hard you try will ever give you the same results as a production test. You build the best lab you can and test against it.

I think these infinite load screens are terrible, but to think that ZOS does not follow these standard practices is very hard to believe.

Apache_Kid

Defilted wrote: »

For all those people that say this was not tested. I can safely say you do not develop/deploy or L3 support software.

Common Software issues/practices
-Development testing and full regression testing(By Q/A) is done in a lab environment. This is standard across the board for every software company I have ever worked for.
-Once a piece of software or suite is moved onto a production environment you will always encounter a problem/s that you did not see in testing and cannot reproduce on a non-production environment.
- No lab environment no matter how hard you try will ever give you the same results as a production test. You build the best lab you can and test against it.

I think these infinite load screens are terrible, but to think that ZOS does not follow these standard practices is very hard to believe.

If it was tested or wasn't tested it clearly wasn't tested enough. That is the problem. You can't even argue otherwise with how widespread the issue is across both PvE and PvP content.

Defilted

Apache_Kid wrote: »

Defilted wrote: »

For all those people that say this was not tested. I can safely say you do not develop/deploy or L3 support software.

Common Software issues/practices
-Development testing and full regression testing(By Q/A) is done in a lab environment. This is standard across the board for every software company I have ever worked for.
-Once a piece of software or suite is moved onto a production environment you will always encounter a problem/s that you did not see in testing and cannot reproduce on a non-production environment.
- No lab environment no matter how hard you try will ever give you the same results as a production test. You build the best lab you can and test against it.

I think these infinite load screens are terrible, but to think that ZOS does not follow these standard practices is very hard to believe.

If it was tested or wasn't tested it clearly wasn't tested enough. That is the problem. You can't even argue otherwise with how widespread the issue is across both PvE and PvP content.

You are just wrong in your assumption. This is becasue you do not understand how software is tested and released in mass. I can certainly argue it as I have seen this exact thing play out with other software many times. Full regression testing will always miss bugs and those bugs can sometimes be catastrophic.

As I stated before a lab environment will never match production and becasue of this bugs will be missed. I see it all the time spread across many software suites that I am part of. People work very hard to minimize this kind of thing, but sometimes these bugs are not seen until production release.

This is exactly what happened here. I base this on years of software release experience.

I am not down playing this bug and how terrible it is, but to make a claim that ZOS some how does not follow standard testing and Q/A regression testing is an outrageous claim IMO.

Kronuxx

@ZOS_GinaBruno @ZOS_JessicaFolsom

To add my own report:

1) The load screens and intermittent high ping spikes have been occuring after CWC patch
2) The intermittent ping spikes I have noticed seem to be random, but also specifically after loading into a zone/instance. I will jump from 90 ms to 400+. The ping will then drop down to 90 ms again after about 60 secs. But, I should also mention that just standing in the same spot, the ping can intermittently jump back up beyond 400+ from 90 ms.

Apache_Kid

Defilted wrote: »

Apache_Kid wrote: »

Defilted wrote: »

For all those people that say this was not tested. I can safely say you do not develop/deploy or L3 support software.

Common Software issues/practices
-Development testing and full regression testing(By Q/A) is done in a lab environment. This is standard across the board for every software company I have ever worked for.
-Once a piece of software or suite is moved onto a production environment you will always encounter a problem/s that you did not see in testing and cannot reproduce on a non-production environment.
- No lab environment no matter how hard you try will ever give you the same results as a production test. You build the best lab you can and test against it.

I think these infinite load screens are terrible, but to think that ZOS does not follow these standard practices is very hard to believe.

If it was tested or wasn't tested it clearly wasn't tested enough. That is the problem. You can't even argue otherwise with how widespread the issue is across both PvE and PvP content.

You are just wrong in your assumption. This is becasue you do not understand how software is tested and released in mass. I can certainly argue it as I have seen this exact thing play out with other software many times. Full regression testing will always miss bugs and those bugs can sometimes be catastrophic.

As I stated before a lab environment will never match production and becasue of this bugs will be missed. I see it all the time spread across many software suites that I am part of. People work very hard to minimize this kind of thing, but sometimes these bugs are not seen until production release.

This is exactly what happened here. I base this on years of software release experience.

I am not down playing this bug and how terrible it is, but to make a claim that ZOS some how does not follow standard testing and Q/A regression testing is an outrageous claim IMO.

I base my claims on my experience with how performance is always substantially lower post patch since I've started playing this game on Xbox. Yeah I'm sure they have some sort of testing protocol in place but I'm saying that those protocols need to be more rigorous and stringent. I may not work in software but I work closely with the QA staff at our manufacturing plant and if something like this happened to one of our products that was literally sent out to millions of customers, QA protocol would change going forward. Yes I understand that it is much more difficult to detect issues in something such as software. However based on how widespread it is coupled with the fact that Xbox always gets stuck with buggy stuff happening post update, it should've been detected.

Why wasn't it detected? Maybe because unlike the PC, console has no version of the 'PTS' where players can go on and play the game with the patch enabled to help the devs identify bugs pre-launch. (It is not possible on the console to create a PTS) It is clear that this is an extremely useful tool for the devs as it allows so much of the leg-work to be done by the players. With so much content in the game it is difficult to test all of it. Maybe they are relying too much on the PTS for PC which leaves the QA process for Xbox lacking.

riVALry9

Dying = Load screen
Transiting (in PvP or PvE) = Load screen
Rezzing at a camp = Load screen
Using a gap closer = Load screen
Repairing a wall = Load screen
Standing in the general vicinity of a wall that’s being repaired = Load screen.

And every single one of those ^ load screens requires a reboot to get out of. There have been times in the past when I’ve called PvP “almost” unplayable due to lag and have noticed huge downward spikes in player population due to said lag, but this...this isn’t even “almost” unplayable. I’m sure that the devs are working on a solution to this issue, but the fact that this game becomes more and more unstable with every update is troubling and merits an explanation (and a more permanent solution).

jaws343

To add to the load screen issue, I have noticed that whenever I first load a character into the game and sometimes when changing zones, my character will be invisible for 10-20 seconds after coming out of the load screen. This was not something that was happening prior to the update.

Defilted

Apache_Kid wrote: »

Defilted wrote: »

Apache_Kid wrote: »

Defilted wrote: »

For all those people that say this was not tested. I can safely say you do not develop/deploy or L3 support software.

Common Software issues/practices
-Development testing and full regression testing(By Q/A) is done in a lab environment. This is standard across the board for every software company I have ever worked for.
-Once a piece of software or suite is moved onto a production environment you will always encounter a problem/s that you did not see in testing and cannot reproduce on a non-production environment.
- No lab environment no matter how hard you try will ever give you the same results as a production test. You build the best lab you can and test against it.

I think these infinite load screens are terrible, but to think that ZOS does not follow these standard practices is very hard to believe.

If it was tested or wasn't tested it clearly wasn't tested enough. That is the problem. You can't even argue otherwise with how widespread the issue is across both PvE and PvP content.

You are just wrong in your assumption. This is becasue you do not understand how software is tested and released in mass. I can certainly argue it as I have seen this exact thing play out with other software many times. Full regression testing will always miss bugs and those bugs can sometimes be catastrophic.

As I stated before a lab environment will never match production and becasue of this bugs will be missed. I see it all the time spread across many software suites that I am part of. People work very hard to minimize this kind of thing, but sometimes these bugs are not seen until production release.

This is exactly what happened here. I base this on years of software release experience.

I am not down playing this bug and how terrible it is, but to make a claim that ZOS some how does not follow standard testing and Q/A regression testing is an outrageous claim IMO.

I base my claims on my experience with how performance is always substantially lower post patch since I've started playing this game on Xbox. Yeah I'm sure they have some sort of testing protocol in place but I'm saying that those protocols need to be more rigorous and stringent. I may not work in software but I work closely with the QA staff at our manufacturing plant and if something like this happened to one of our products that was literally sent out to millions of customers, QA protocol would change going forward. Yes I understand that it is much more difficult to detect issues in something such as software. However based on how widespread it is coupled with the fact that Xbox always gets stuck with buggy stuff happening post update, it should've been detected.

Why wasn't it detected? Maybe because unlike the PC, console has no version of the 'PTS' where players can go on and play the game with the patch enabled to help the devs identify bugs pre-launch. (It is not possible on the console to create a PTS) It is clear that this is an extremely useful tool for the devs as it allows so much of the leg-work to be done by the players. With so much content in the game it is difficult to test all of it. Maybe they are relying too much on the PTS for PC which leaves the QA process for Xbox lacking.

A PTS for Xbox/PS would be a huge help. There is no denying that. Without a semi production testing system like a PTS bugs, minor or major will continue to get through testing and be discovered in production. The nature of a non- production environment will always miss software bugs. ZOS could help themselves by responding with fixes faster, but keep in mind all patches that go over the XBOX network must be screened and approved and this will delay the fix further.

Apache_Kid

Defilted wrote: »

Apache_Kid wrote: »

Defilted wrote: »

Apache_Kid wrote: »

Defilted wrote: »

For all those people that say this was not tested. I can safely say you do not develop/deploy or L3 support software.

Common Software issues/practices
-Development testing and full regression testing(By Q/A) is done in a lab environment. This is standard across the board for every software company I have ever worked for.
-Once a piece of software or suite is moved onto a production environment you will always encounter a problem/s that you did not see in testing and cannot reproduce on a non-production environment.
- No lab environment no matter how hard you try will ever give you the same results as a production test. You build the best lab you can and test against it.

I think these infinite load screens are terrible, but to think that ZOS does not follow these standard practices is very hard to believe.

If it was tested or wasn't tested it clearly wasn't tested enough. That is the problem. You can't even argue otherwise with how widespread the issue is across both PvE and PvP content.

You are just wrong in your assumption. This is becasue you do not understand how software is tested and released in mass. I can certainly argue it as I have seen this exact thing play out with other software many times. Full regression testing will always miss bugs and those bugs can sometimes be catastrophic.

As I stated before a lab environment will never match production and becasue of this bugs will be missed. I see it all the time spread across many software suites that I am part of. People work very hard to minimize this kind of thing, but sometimes these bugs are not seen until production release.

This is exactly what happened here. I base this on years of software release experience.

I am not down playing this bug and how terrible it is, but to make a claim that ZOS some how does not follow standard testing and Q/A regression testing is an outrageous claim IMO.

I base my claims on my experience with how performance is always substantially lower post patch since I've started playing this game on Xbox. Yeah I'm sure they have some sort of testing protocol in place but I'm saying that those protocols need to be more rigorous and stringent. I may not work in software but I work closely with the QA staff at our manufacturing plant and if something like this happened to one of our products that was literally sent out to millions of customers, QA protocol would change going forward. Yes I understand that it is much more difficult to detect issues in something such as software. However based on how widespread it is coupled with the fact that Xbox always gets stuck with buggy stuff happening post update, it should've been detected.

Why wasn't it detected? Maybe because unlike the PC, console has no version of the 'PTS' where players can go on and play the game with the patch enabled to help the devs identify bugs pre-launch. (It is not possible on the console to create a PTS) It is clear that this is an extremely useful tool for the devs as it allows so much of the leg-work to be done by the players. With so much content in the game it is difficult to test all of it. Maybe they are relying too much on the PTS for PC which leaves the QA process for Xbox lacking.

A PTS for Xbox/PS would be a huge help. There is no denying that. Without a semi production testing system like a PTS bugs, minor or major will continue to get through testing and be discovered in production. The nature of a non- production environment will always miss software bugs. ZOS could help themselves by responding with fixes faster, but keep in mind all patches that go over the XBOX network must be screened and approved and this will delay the fix further.

Yes that is true. Once there is a fix, we still need to wait for Microsoft to OK it. Starting to look like this won't be fixed before the weekend.