Ps5 client constantly crashes within 5 mins
Ps5 version has been working so well until today.
Currently the game completely freezes shortly after logging in as any character. Can be replicated. Have tried removing MTx. Disabling all sound. Specifying servers. No other games are behaving this way Re downloaded ps4 client. It loads (slowly) but appears stable. But still suffers from missing textures, efffects and many assets don’t make it into a map before it’s cleared (strong boxes, kalguur ore, etc) Diablo 4 (ugh) stays connected thru any activity/amount of time. Ps5 1GBps fibre central North America If anyone has solved this issue please share! Last edited by press_start73#9139 on Oct 30, 2024, 2:33:22 AM Last bumped on Oct 31, 2024, 1:51:40 PM
|
|
This won't really help you, but just for reference, I am not experiencing this. Successfully playing for hours at a time with no issues aside from occasionally dropping a few frames.
| |
It makes no sence on a console as to why some people can't go more than 1 minute without crashing (myself included) and some have no issue. This ain't PC. And not a single comment on the matter from GGG for about a month is shockingly incompetent and disgraceful if i'm honest.
If you critique this game and its problems your post will be removed.
In a news thread about sound i asked "Why did it take multiple leagues to fix the sound on console?". Then got put on probation by Kane the sound guy! This is who GGG are! |
|
Yes.. after around 2 minutes on map games crashes. Got it now 3 times
|
|
Did a reinstall on Sunday to finally restore my custom filters. (see fog of war and filter bug posts)
Was able to do a few maps on Sunday early afternoon. Screen locked in Kingsmarch for at least 5 minutes before I closed PoE. Opening PoE to get to the title screen but unable to get to character select. I am able to bring up the options and presumably make changes. The above happens about half the time after a crash occurs. When able to get through character selection one of two things happen, every time: Long to infinite load screens in my first 3 area changes resulting in dropping to a "locked" title screen OR Freezing during various activities, in each major town, Kingsmarch, hideout, and maps - only resolved by force closing the game. I have not been able to have the game open and functional for more than a few minutes since Sunday evening. Have attempted to clear cache and tried another reinstall, but still having the same issues as described above. |
|
" Careful now, while the team may not have much interest in fixing issues for the console users, as you know they do lurk to "admin" these threads. At this rate that is the only interaction we receive in these forums. I am well aware of the code of conduct in these forums. I will continue to argue that this is not NEEDLESS or NEGATIVE because it is fact and proven at this point. Nor is this hateful or even a personal attack with any ill intention. GGG, I challenge you to also follow your own code of conduct: Antagonize in an obnoxious manner: through inaction, nonresponse, and censoring anyone who voices concern about the aforementioned Disrupt Forum or Chat use for others Deleting posts calling for action. What are these forums here for if there is no engagement, acknowledgement, and worst of all no follow through for months after an issue has been identified? My favorite Impersonating GGG Staff It's easy to see the title on your name in these threads, the account messages, or the emails - otherwise the continued handling of events make me wonder if any of you actually work at GGG or if the community interactions have been outsourced to a 3rd party company. For reference: https://www.pathofexile.com/forum/view-thread/1457463 Last edited by pandaman1012#9718 on Oct 30, 2024, 3:16:17 PM
|
|
Without making any additional changes, the game has worked enough for me to get some gold to my town.
Was able to blast 5 or 6 maps pretty quick without a freeze or crash. The intermittent nature of this experience leads me to believe that it is caused by the backend migration. As such, if you experience this bug, it seems the proper fix is: "please try again later" Last edited by pandaman1012#9718 on Oct 31, 2024, 1:52:17 PM
|
|