intel 285k insane spikes since 3.26 patch update caused by engine multithreading

idk, i got over 9k hours in poe1&2, longtime supporter, never had issues like this. both my old pc's dont have that issue, 6700k and 10700k.

and since everything else works fine on the pc and theres a clear timeline which indicated that it is the game/software itself i guess i'll stop playing since this is too much to bother around.
if it would have started out of nowhere in both games at the same time id understand that this might be a personal pc issue but the timeline is:

3.25 fine
0.1 fine

into

3.25 fine
0.2 issues

into

3.26 issues
0.2 issues


there being a month long period where the game that got patched first isnt fine and the non patched game is fine clearly shows that whatever engine change they made fucked it up, esp. when the next patch for the older game (which clearly has copied poe2 things) caused the same issues.

having to spend more money on either a replacement board+cpu or having to play with those issues just because ggg doesnt test their game properly is just non acceptable

last thing ill try is bazzite (linux) but i doubt this will change or solve anything

if at least ggg would say anything about it, i mean ive been reporting this since it started with 0.2 like 2 months ago. if they would at least say yea they can see those issues themselfs with the newest intel gen and some 14th gen cpus or if they cant detect any of those issues with a 285k on their test machine. then at least we and i would know if that is another issue and if going for a 9800x3d switch is worth it per se
but nothing but silence about it, i even contacted ggg support directly, but just the standard answer with "please put it on the forums"
yea guess what ive been doing ever since it started...

another update, disabling engine multithreading in the game settings solves it completely, but gives shit performance obviously
the cpu spikes go away the second i disabled it


could this be because the ultra series doesnt hyperthread anymore? so 1 core 1 thread instead of the previous 1 core up to 2 threads?
and the game forces the 2 threads onto cores so it kinda conflictes with the cpu architecture?

but since it was fine before the 0.2 and 3.26 update, whatever you guys changed really doesnt work well with multithreading on the ultra series cpus

Its not only on ultra series problem, i have older processor and have same bad performance and cpu spikes. Disabling multithreading in game removes spikes but gives bad fps. And its started with 3.26 update. 3.25 was perfectly fine, same for 0.1 poe2 and shit happened after 0.2

i remember jonathan talking about how they tackled the nvidia issues and also the intel 14th gen instabilities and that they went crazy over it trying to fix it.
this was after the 0.2 reveal in an interview shortly before 0.2 released.
so it has to be this change they made while trying to fix the issues. ironically they literally created issues with that fix

So I might have a solution (possibly a fluke). I downloaded Process Lasso (you don't need the paid version). It comes with a power plan (Control Panel -> Choose a Power Plan) called "Bitsum Highest Performance". It apparently prevents the CPU from putting cores into sleep mode during high-demand tasks. I'm using it for a few hours now and no more CPU spikes so far (I hope I'm not jinxing myself, though haha).
Maybe it helps you guys too.

This is my graph using mentioned power plan:


I will report back if it stays that way or if the problem returns after a while.

nope, didnt help, used the mentioned power plan, also tried manually setting threads and cores before with that program but never used the power plan til right now, but yea, didnt change anything sadly
only disabling engine multithreading fixes it rn

"

Artluxd#5219 wrote:

nope, didnt help, used the mentioned power plan, also tried manually setting threads and cores before with that program but never used the power plan til right now, but yea, didnt change anything sadly
only disabling engine multithreading fixes it rn

Out of curiosity, do you use G-Sync?

yes, but how could that correlate to each other?
if i put the game into windowed (no gsync active in non fullscreen windowed) it stays the same

i also updated the bios today since there was a microcode update but also didnt change anything

"

Artluxd#5219 wrote:

yes, but how could that correlate to each other?
if i put the game into windowed (no gsync active in non fullscreen windowed) it stays the same

i also updated the bios today since there was a microcode update but also didnt change anything

I was just curious - I also use G-Sync and, weirdly, when disabling it the issue went away before returning after a few hours.
I hope you find a solution for your problem - maybe there are different causes for this issue.

i went ahead and completely disabled all e-cores again in the bios, i am running on 8 normal cores and 8 threads AND IT IS STILL HAPPENING.
theres now a 0% chance that this has anything to do with core scheduling or anything OS related. the game can utilize 8 cores and there are only 8 cores instead of 24.

paired with it working flawlessly in both games before the patches, its 100% on ggg's side and something in their engine changes. having it fixed when disabling engine multithreading is just more evidence for that. they just need to actually acknowledge that and fix it...