redlink1979 wrote: »""Error CE-34878-0" is a common error on the PlayStation 4 that can occur due to corrupt data or system software."
https://help.elderscrollsonline.com/app/answers/detail/a_id/37022/~/what-do-i-do-if-i-get-error-code-ce-34878-0-when-trying-to-play-the-elder
Suggested fixing does nothing, as I stated before on ps4's support subforum, because the problem isn't at our end...
PS - I can also upload my PS4's error log, the list is entirely filled with ESO's crashing errors ONLY.
redlink1979 wrote: »""Error CE-34878-0" is a common error on the PlayStation 4 that can occur due to corrupt data or system software."
https://help.elderscrollsonline.com/app/answers/detail/a_id/37022/~/what-do-i-do-if-i-get-error-code-ce-34878-0-when-trying-to-play-the-elder
Suggested fixing does nothing, as I stated before on ps4's support subforum, because the problem isn't at our end...
PS - I can also upload my PS4's error log, the list is entirely filled with ESO's crashing errors ONLY.
Yeah the log only does the last 100 reports and my log of crashes only goes to the middle of last week because I’ve crashed over 230+ times since then
Spartabunny08 wrote: »I've been thinking about this blue screening issue and I had a specific thought. What if this blue screening can't be stopped based upon the server side receiving so many changes and it's just really making the client/server incompatible. In theory if this is the case when we redownload the game it will be a new client and will better sync with the server thus eliminating the memory leak. Would be nice to hear Zos... if so we're patient, hell it would be better than guessing right?
Since November of last yearStrider__Roshin wrote: »How months has this been going on?
@ZOS_SarahHecker @ZOS_GinaBruno
Seems reasonable to have a follow up comment post-patch. Spent a good amount of time last night in Kaal - 3 hours or so - and no bluescreen/crash to dashboard despite some heavy fighting. Again, just my personal experience but I felt like this latest change made a difference.
But... there was a simply massive increase in lag. I'm talking 4 seconds between pulling the trigger and a siege weapon actually firing, being unable to bar-swap in fights, abilities taking 3+ seconds to fire (with your character stuck in that animated position while you're waiting) etc. It was really bad.
Maybe it was just a rough night for the servers, but if it wasn't, then it feels like the crash/bluescreen frequency may have been reduced at the cost of a significant performance hit.
I wonder what others here experienced last night.
@ZOS_SarahHecker @ZOS_GinaBruno
Seems reasonable to have a follow up comment post-patch. Spent a good amount of time last night in Kaal - 3 hours or so - and no bluescreen/crash to dashboard despite some heavy fighting. Again, just my personal experience but I felt like this latest change made a difference.
But... there was a simply massive increase in lag. I'm talking 4 seconds between pulling the trigger and a siege weapon actually firing, being unable to bar-swap in fights, abilities taking 3+ seconds to fire (with your character stuck in that animated position while you're waiting) etc. It was really bad.
Maybe it was just a rough night for the servers, but if it wasn't, then it feels like the crash/bluescreen frequency may have been reduced at the cost of a significant performance hit.
I wonder what others here experienced last night.
@ZOS_SarahHecker @ZOS_GinaBruno
Seems reasonable to have a follow up comment post-patch. Spent a good amount of time last night in Kaal - 3 hours or so - and no bluescreen/crash to dashboard despite some heavy fighting. Again, just my personal experience but I felt like this latest change made a difference.
But... there was a simply massive increase in lag.
@ZOS_SarahHecker @ZOS_GinaBruno
Seems reasonable to have a follow up comment post-patch. Spent a good amount of time last night in Kaal - 3 hours or so - and no bluescreen/crash to dashboard despite some heavy fighting. Again, just my personal experience but I felt like this latest change made a difference.
But... there was a simply massive increase in lag. I'm talking 4 seconds between pulling the trigger and a siege weapon actually firing, being unable to bar-swap in fights, abilities taking 3+ seconds to fire (with your character stuck in that animated position while you're waiting) etc. It was really bad.
Maybe it was just a rough night for the servers, but if it wasn't, then it feels like the crash/bluescreen frequency may have been reduced at the cost of a significant performance hit.
I wonder what others here experienced last night.
LeeTemplar wrote: »No more blue screens after the update for me.
ZOS_SarahHecker wrote: »Hey all, for those of you who are reporting lag on PS4 after the recent patch, can you submit a ticket detailing what you are experiencing? Getting more info from those of you experiencing this would greatly help us identify commonalities between players and help identify the issue.