0.1.1 Patch Notes

"

Bluecheetoseatsbutts#4055 wrote:

"

Cajual#4575 wrote:

"

deadamaranth#4371 wrote:

Pretty much, yeah. I don't develop but I do enough work adjacent to several different dev teams to know that it's ALWAYS more complicated than the user assumes at first glance. Especially when any legacy software (engine in this case) is involved.

Heck, sometimes the people who could more easily bring you some answers are no longer part of that team, or have moved on from the company entirely. Often, dev work is like translating an ancient language that you've just seen for the first time :P

Uh, it's not really that. They can easily do integration and regression testing in-house (by easily, mean the frameworks exist), but accounting for every edge case of end user hardware/software combinations isn't as easy. They have to pore over millions of logs to try and identify a pattern which could be something as simple as a bad address call.

Software development work is pretty easy until you give it to a customer.

Tell me you don't understand software development without saying you dont understand software development.

"

mmotti#9037 wrote:

"

FuelMYGamE#8145 wrote:

Windows 24h2 the problem is not fix
Loading screen, crash PC
why has this pretty big problem not been fixed?

There is a "fudge" to resolve this but it really is a fudge. The "ready made" solution is available at: https://github.com/Kapps/PoEUncrasher/releases/latest

I've made my own variation of this taking inspiration from the above. But I can tell you with confidence that it "resolves" the issue. I couldn't load into the game the majority of the time, let alone get past character creation. Would be guaranteed to crash after x portals (if not the first one) and the system would be unrecoverable.

This is me loading into POE a fresh and spamming portals etc without issue:



The only "fix" for this seems to be setting the PoE process to "Realtime" priority when you're entering a loading screen or the game engine is initialising (when you first boot up the game). I've tried other priorities and none of them seem to work as effectively. Alongside this you need to reduce the CPU affinity (mostly to reduce the possibility of the entire system locking up if/when the CPU usage skyrockets.

I also tried a different approach of only restricting the process after the CPU usage started to creep above a threshold but by that point it's usually too late to recover.

I'd recommend giving the GitHub link a go. As someone who was crashing every 10 minutes or less if I could even get into the game... it worked for me.

"

auspexa#1404 wrote:

"

Bluecheetoseatsbutts#4055 wrote:

You need to chill bro. Read a random comment and were like, "Is this about me?! You're trash and I just spent 30 minutes researching your account to tell you how wrong you are." Save it for your manifesto.

A comment that's next to mine, and directly addresses my concern with an insult is not "a random comment". Maybe this is too complicated for you?

"

Cajual#4575 wrote:

"

Bluecheetoseatsbutts#4055 wrote:

"

Cajual#4575 wrote:

Uh, it's not really that. They can easily do integration and regression testing in-house (by easily, mean the frameworks exist), but accounting for every edge case of end user hardware/software combinations isn't as easy. They have to pore over millions of logs to try and identify a pattern which could be something as simple as a bad address call.

Software development work is pretty easy until you give it to a customer.

Tell me you don't understand software development without saying you dont understand software development.

I am a VP of software development at Capital One. I don't really need your affirmation.