"
So, I found a sure way to avoid the problem, but it's very convoluted. It's a combination of methods. This is when using Windows 11, should work for Windows 10 but not Linux.
1) Use https://github.com/valleyofdoom/ReservedCpuSets to create a CPUSet. I created one with 12 of my 16 cores on a Ryzen processor.
2) Reboot (unfortunately the cpu set changes only take after a reboot)
3) Now, if you check your core usage, you should have only the non-cpu-set cores being used. In my case, I had no usage on the first 12 cores and all usage was on the last 4 ones.
4) Use Process Lasso or the `cmd` batch file posted on this thread somewhere to set the PathOfExile executable file (.exe) CPU affinity to the same cores as the cpuset. This is important, setting affinities across cpu sets makes everything worse.
Now you hve your game running on the 12 cores, and the OS/rest of the things running on the last 4 cores. There are still some stuff that can jump around the CPUset but I played six hours yesterday without a single lockup or crash.
Unfortunately, when you want to do anything else on the computer you will have to undo the Reserved CPU Sets config again (basically deselect all cores on the ReservedCPUSets program) and reboot.
For reference, I found the CPUSet stuff while looking at this https://www.reddit.com/r/pcmasterrace/comments/17pq1qp/setting_cpu_cores_exclusive_for_games_and_windows/
Edit: added that the information is for Windows. Funnily enough I started looking for CPUSets because I use Linux a lot and that's a function on linux kernels. Turns out windows also implemented a less practical version of it :D
Also, Process Lasso seems to have support for CPU Sets but I haven't tried to see if it works the same or not.
Yeah, umm... no lol. I don't remember having to jump through that many hoops to play a game since the late 80s when maximizing the amount of free (640k) memory was a thing.
PoE2: A good, giving game Last edited by interbeing#5112 on Dec 11, 2024, 1:45:30 PM
|
Posted byinterbeing#5112on Dec 11, 2024, 1:44:57 PM
|
|
Someone saw GGG talking about it ? Or we are like alone ?
|
Posted byPesticydeFr#3742on Dec 11, 2024, 1:51:07 PM
|
|
Hopefully fixing this also finally fixes the now long standing multithreading bug in this engine, where CPU usage spikes constantly creating stutters on certain hardware setups. I didn't crash in my brief play time before refunding, but got hit with the stutter variation hard.
Both issues seem highly related to how this game utilizes threads/cores, but the issue I'm talking about the game doesn't seem to work them enough which causes them to transition to inactive/low power states and back to active constantly creating constant CPU spikes and unplayable stuttering during gameplay, while the issue with the crashing seems to be from working other setups and CPUs too hard.
With both of these massive flaws, the only solution in the game itself is exactly the same - disable the Engine Multithreading option, and that's not a good solution considering how much it drops performance. There are some workarounds for both issues outside of the game, but that's always gonna be a hassle.
Hope it doesn't take too long for them to tackle this, but I don't have a lot of hope here. The CPU spike / stutter issue w/ engine multithreading has been reported and known of for at least four years now in the old engine version and PoE1 and they haven't done anything about it.
|
Posted bypyide#1088on Dec 11, 2024, 1:51:38 PM
|
"
I don't remember having to jump through that many hoops to play a game since the late 80s when maximizing the amount of free (640k) memory was a thing.
Because that problem not just related to the game but it is buried much deeper and related to the operating system / drivers / uefi / hardware.
Last edited by cursorTarget#1174 on Dec 11, 2024, 1:53:16 PM
|
Posted bycursorTarget#1174on Dec 11, 2024, 1:52:50 PM
|
"
"
"
Hi everyone, whilst we have already been investigating this issue already, it would be massively helpful if you could provide your dxdiag output by doing the following on windows:
run > dxdiag > save all information
and sending me that file or it's contents in a private message.
Thanks!
I think we would appreciate it if this was put back up on the known issues post as well. I know not every issue is listed there but this is literally game breaking, in some cases PC breaking.
It's there?
Second on the list:
https://www.pathofexile.com/forum/view-thread/3594260
|
Posted byOonue#2226on Dec 11, 2024, 1:53:04 PM
|
"
"
I don't remember having to jump through that many hoops to play a game since the late 80s when maximizing the amount of free (640k) memory was a thing.
Because that problem not just related to the game but it is buried much deeper and related to the operating system / drivers / uefi / hardware.
The game is doing stuff the operating system / drivers / uefi / hardware doesn't like.
It should stop doing that stuff.
Blame 24H2 as much as you'd like, Ubisoft was able to work with Microsoft to hold back the update from people playing their games until a fix was figured out and implemented.
Currently POE and POE2 stand out as the only major games locking up the PC like this, and POE was having the issue prior to 24H2 launch.
|
Posted byOonue#2226on Dec 11, 2024, 1:57:30 PM
|
"
"
"
Hi everyone, whilst we have already been investigating this issue already, it would be massively helpful if you could provide your dxdiag output by doing the following on windows:
run > dxdiag > save all information
and sending me that file or it's contents in a private message.
Thanks!
I think we would appreciate it if this was put back up on the known issues post as well. I know not every issue is listed there but this is literally game breaking, in some cases PC breaking.
It is. It never left. I don't understand why people keep claiming this.
"- Investigating cases where some players experience crashes and have to restart their PCs."
You're right I'm blind my bad.
|
Posted bysmeppe#2506on Dec 11, 2024, 1:57:46 PM
|
"
Bit of a p*** take tbh... With how many people are having these issues, this should have been caught ages ago, the 24h2 windows update also came out like 2 months and regardless... these issues have been present and ignored in POE1.
Check reddit. There are posts as far back as August. Either GGG can't fix it or they haven't given a shit until right now when thousands of people are experiencing it.
|
Posted byLilith#3312on Dec 11, 2024, 2:06:05 PM
|
"
"
Bit of a p*** take tbh... With how many people are having these issues, this should have been caught ages ago, the 24h2 windows update also came out like 2 months and regardless... these issues have been present and ignored in POE1.
Check reddit. There are posts as far back as August. Either GGG can't fix it or they haven't given a shit until right now when thousands of people are experiencing it.
Posts actually go back several years for the issue in POE1. They addressed it once and claimed to fix it and then ignored all threads where it continued to happen. So yeah, either they just don't know how to properly fix it or just didn't care to put enough resources to doing so.
Last edited by GPython#5980 on Dec 11, 2024, 2:20:39 PM
|
Posted byGPython#5980on Dec 11, 2024, 2:19:31 PM
|
|
it has something to do with shader cash, or at least partially. Today my game refused to boot in town multiple times in a row. I ave cleared dx12 and minimaps in user C:\Users\%username%\AppData\Roaming\Path of Exile 2
and wuala - it worked
|
Posted bynikoleagle#5373on Dec 11, 2024, 2:19:59 PM
|
