Strider__Roshin wrote: »Correct me if I'm wrong, but wasn't this suppose to be fixed on the 16th? How long has this been an issue on PS4?
ZOS_SarahHecker wrote: »Hey all, just to give a quick update here: The most recent memory management changes brought to PC showed promising results and we are currently aiming to bring them to consoles next week, exact date TBD. This should reduce the issues with crashing you have seen so far. Thank you all again for your patience here.
ZOS_SarahHecker wrote: »Hey everyone, just a quick update on the date for the incremental. It's currently planned for next week on February 5th.
This event has been a disaster when everyone bluescreens nonstop. We all know it’s caused by ulti being dropped. Especially the necro Ultis. Been broken since November btwZOS_SarahHecker wrote: »Hey everyone, just a quick update on the date for the incremental. It's currently planned for next week on February 5th.
I don’t think they know how to fix the problem, why does it blue screen non stop on ps4 for everyone in the game, but not on pc.
I don’t think they know how to fix the problem, why does it blue screen non stop on ps4 for everyone in the game, but not on pc.
xbox is not bad either.
honestly, it would be nice if sony got involved. They have a broken product on their system and they should be allowing everyone to get refunds for the products and all crowns purchased and charge it back to zos.
I think I recall sony or ms allowing refunds before well after the product was bought due to it being faulty. that would send a message. Sony would, i expect, have contracts in place with Zos that might even mention things like this. So everyone on ps4 should contact sony and try to force their hand
AgaTheGreat wrote: »I don’t think they know how to fix the problem, why does it blue screen non stop on ps4 for everyone in the game, but not on pc.
xbox is not bad either.
honestly, it would be nice if sony got involved. They have a broken product on their system and they should be allowing everyone to get refunds for the products and all crowns purchased and charge it back to zos.
I think I recall sony or ms allowing refunds before well after the product was bought due to it being faulty. that would send a message. Sony would, i expect, have contracts in place with Zos that might even mention things like this. So everyone on ps4 should contact sony and try to force their hand
I wish it was that easy. Unfortunately until press or some serious YouTuber covers it, Sony won't do a thing. And neither will zos, as money keeps pouring in from PlayStation players nonetheless.
ZOS_SarahHecker wrote: »Hey everyone, just a quick update on the date for the incremental. It's currently planned for next week on February 5th.
Sony is certainly not to blame for this. I have played countless other games on PS4 and in most I don't ever see a bluescreen. Even if a game crashes, it's a rare accident. That's not true for this game sadly.
On the other hand, there is ESO with a crash each hour of playtime in Cyrodiil. And this whole Dragonhold fiasco makes us almost forget that the game did not run well before the update that increased the amount of crashes. Even before Dragonhold, ESO crashed more often than the average PS4 game. And when it did not crash, it had other issues (you guys certainly remember endless loading screens). I have no understanding why there's no business interest into fixing that once and for all in a more timely manner. I mean players unable to play are bad business. Regardless of the game.
What we can do about it is fill out the crash report formula we see each time we bluescreen. I don't know how Sony handles those reports but there's hope that they will act when they see enough crash reports pour in from the very same game.
DaveMoeDee wrote: »The blue screens are just crashes, right?
I was only on a few minutes per day during this past even, but during the previous event, I feel like PC was crashing a lot too. Game feels really brittle at the moment. Hopefully the next performance patch delivers. It is possible with a major change like that in the pipeline that they will not assign developers to debug the old code causing that instability.