Agreed - The state of PS4 is shocking. 90 days of blue screens, followed by a Feb 5th "fix" that introduced really bad skill lag, even when you're solo-ing a resource against NPCs, far from any action.Can we get some feedback instead of babysitting this thread zos.
I hope you're wrong. I really do. I can't speak for other platforms, but on PS4 they (and we) know exactly what date the lag issues started. It was the update released for console on Feb 5th, 2020Guys... seriously. It's time to pack it in.... ...They can't fix this.
ZOS_RachelM wrote: »Hello! We've removed some posts from this thread given their baiting and off topic nature.
It’s okay to disagree and debate on the official ESO forums, but we do ask that you keep all disagreements civil, constructive, and on-topic.
Guys... seriously.
It's time to pack it in.
Zos isn't going to fix this. This is why there's no acknowledgement of these issues. They either don't know how to fix it, or they aren't being given the funds to fix it.
You can't even pre-order Greymoor for PS4 to this very day, although why would you. Some speculation I've heard is that Sony is holding it up due to all the crash reports that ESO has had.
Do you hear the bell? The bell tolls for ESO on console. Time to collectively pull your heads out of the sand and face cold hard reality....this isn't going to get fixed. Yes, we all love this game when it works, but those days are over. If you can't deal with the facts and reality, by all means keep yelling into the void. But for your own sanity, might be time to seriously consider walking away from this broken mess. Because this is how it is and will probably always be from now on.
They can't fix this.
The issue with this is that the problems did not start with the Feb 5th update. They began earlier. Another milestone was the November 5th 2019 update on console, the Dragonhold DLC patch. Dragonhold introduced the crashes (so-called bluescreens) which resulted in the tremendous increase of crash reports we sent to Sony.If I knew that code I released on a specific day introduced a specific issue like this, I would be able to go back through that code and in fairly short order identify (through a series of rollbacks) what caused it, and then I would have a starting point to make changes and tweaks to fix it. The Feb 5th update they pushed out to address the PS4 constant memory crashes was the start of the lag fest for us (weeks before the same lag was introduced to PC etc).
That's basically what happened. They traded crashes (which are super transparent to the platform holders like Sony or Microsoft) for issues that are not reported automatically like lag and other in-game annoyances. So while I'm on the fence of speculation here, it could as well be a liberate choice to have the current issues over others. Hopefully this trade is just an in-between step while they fix the real issues beneath it.I heard that Sony was looking into the mass of crash reports, I reckon that's why ZOS changed the crashes to freeze screens, to stop the reports flooding in.