Heist Mechanic - wierd workaround

So i want to say the Heist mechanic is incredibly fun and rewarding - when it works. ive taken to running one heist, closing the app and restarting. ive now run 40+ heists and a few grand heists in a row without even the feeling of "its about to crash". its an incredibly tedious and time consuming "workaround" but it feels really nice to actually be able to play the league. does anyone have any ideas as to why the first heist runs without a problem, but subsequent ones tend to crash?
-PS4-

It essentially *has* to be a resource cleanup issue.

Something (memory, open files, threads, DB queries, etc) is not being closed/cleaned up when finished.

It *may* be something that was intentionally done to try to improve performance by preventing it from having to load that data again soon.

Unfortunately, it's not working. It's passing some limit on the resource, and crashing.

Suggestion for GGG: Whenever an openable area type (Map Device, Heist, Delve zone, etc) is opened, purge all existing resources from that zone type before opening it up. There's literally no way for us to reenter those instances after we open a new one, so there's zero need to keep any resources from them.

so ive done like 100 at this point resetting between each, without an incident. i like his idea of purging old resources. is there any way to do this? like a soft reset between instances? i wouldnt mind a little bit longer load screen if it meant far less crashes

you close the game and start it again ? Isn't the nonstop loading iritating ?

"

Dc-sewer wrote:

you close the game and start it again ? Isn't the nonstop loading iritating ?

yes. it definitely is. but its better than just crashing every other heist and losing all your loot and exp for you and the rogue.

usually watching youtube or something else anyways while i play

jut tried to do a second heist in a row, as soon as i grabbed the target item, hard crash, to a black screen with the top left quadrant flashing white. had to force turn off the ps4 and it had to check system files.... guess its back to doing one in a row with a reset in between. i cant imagine very many people are still playing this league.....

"

cammoflauge5 wrote:

jut tried to do a second heist in a row, as soon as i grabbed the target item, hard crash, to a black screen with the top left quadrant flashing white. had to force turn off the ps4 and it had to check system files.... guess its back to doing one in a row with a reset in between. i cant imagine very many people are still playing this league.....

I've been testing out some variations on this stuff.

The crash seems to be more related to the time spent in Heist, or distance traveled or something, because if you run very low level Heists (30-40), you can run 3 or 4 back to back with no crashing.

High level ones are 1-2, no more.

My rate on Grand Heists so far is that 2 wings is safe, a 3rd is likely to crash (note: I've only run a half dozen grand heists, so the sample size is very small).

I also tried simply logging out between Heists instead of doing the full app restart. That's a no go -- you need the full app restart to keep the crashes at bay.

"

QQPQ wrote:

It essentially *has* to be a resource cleanup issue.

Something (memory, open files, threads, DB queries, etc) is not being closed/cleaned up when finished.

It *may* be something that was intentionally done to try to improve performance by preventing it from having to load that data again soon.

Unfortunately, it's not working. It's passing some limit on the resource, and crashing.
...

The issues with repeated crashing seem to be focused entirely on Playstation platforms. IOW - It's not an intrinsic issue with the game's architecture.

That doesn't mean, however, that it's not having issues in PS4's environment - It most certainly is. At least, according to reports. (I play on XBox. I've got a PS4, but have never tried PoE on it.)

Xbox now uses Win10's core, while PS4 uses a variation of OpenBSD and highly tuned other stuffs. Arguably, the PS4 is more finally tuned to get more out of what it has than XBox. Aaand, that means it's "different." :)

https://en.wikipedia.org/wiki/Xbox_One_system_software

https://en.wikipedia.org/wiki/PlayStation_4_system_software

My sympathies go out to my PS4 brethren... GGG hasn't ever been able to avoid problems with PS4 releases, AFAIK.

Has Vulkan been implemented for console ports, yet? AFAIK, it's supported by XBox, not sure about PS4.

A question for PS4'ers - How do you have your audio I/O set up? Are you using headphones? TV Out? Other sound device? Also - You are running hardwired straight to the modem/router, right? Right? :)

"

Morkonan wrote:

The issues with repeated crashing seem to be focused entirely on Playstation platforms. IOW - It's not an intrinsic issue with the game's architecture.

This is intrinsically false.

Two different platforms *can't* use an identical codebase.

There are tons of differences in the XBox code and the PS4 code, just like there are tons of differences between the XBox code and the PC code.

Clearly, the issue lies either within those differences, OR it means that something they've done which is within the parameters of the XBox platform is outside the parameters of the PS4 platform. This does not mean the PS4 is responsible for the crashing. It's a flaw in GGG's coding.

If it were a flaw in the platform, *far* more games would crash. I, personally, have only had ever had crashes in PoE and D3. Every other game I played on PS4 never crashed (for me), and D3 crashes were VERY rare compared to PoE crashes.

To use a car analogy:

If GGG designed a car, and you drove that car around town and it worked fine for you, but then I drove it on the country roads and it fell apart around me, would you say that's a problem with the country road, or with the car?

"If GGG designed a car, and you drove that car around town and it worked fine for you, but then I drove it on the country roads and it fell apart around me, would you say that's a problem with the country road, or with the car?"

Both lol