"
One of the workarounds for the 24H2 problem is to turn off auto HDR in the control panel. If rolling back to 23H2 is a no-go for you. I've removed all crashes (except for the occasional DX12 D3D issue) on my system, and they all seem to have been Microsoft Win 11 issues.
does disabling Auto HDR really help?
|
Posted byankeer#0343on Jan 17, 2025, 3:21:12 AM
|
"
Pegaea#0773 wrote:
One of the workarounds for the 24H2 problem is to turn off auto HDR in the control panel. If rolling back to 23H2 is a no-go for you. I've removed all crashes (except for the occasional DX12 D3D issue) on my system, and they all seem to have been Microsoft Win 11 issues.
does disabling Auto HDR really help?
Not on my side, it was disabled in the first place :|
Just re-downloading the game and trying to run it with windows 8 compatibility lol
|
Posted bya197622aaa#6928on Jan 17, 2025, 3:33:53 AM
|
|
I was hoping the patch fixed the issue but unfortunately the game still completely locks my PC forcing a hard reset.
The questions is will we get to page 500 before this issue is fixed?
|
Posted byWoahNoah#1801on Jan 17, 2025, 3:34:20 AM
|
"
I was hoping the patch fixed the issue but unfortunately the game still completely locks my PC forcing a hard reset.
The questions is will we get to page 500 before this issue is fixed?
I think we'll get there.
|
Posted byankeer#0343on Jan 17, 2025, 3:37:35 AM
|
|
Its not just hard reset! I cant start the game at all at the moment... Why we are paying for unplayable game?! That problem keep going and they simply ignoring it! If they keep going that way everyone will want refund and they will lost a lot of the money.
|
Posted bypresiana#5658on Jan 17, 2025, 3:58:05 AM
|
"
One of the workarounds for the 24H2 problem is to turn off auto HDR in the control panel. If rolling back to 23H2 is a no-go for you. I've removed all crashes (except for the occasional DX12 D3D issue) on my system, and they all seem to have been Microsoft Win 11 issues.
Not using hdr... 24H2.
Still lock ups.
|
Posted byDeKoedoetBoe#7312on Jan 17, 2025, 4:05:42 AM
|
"
"
One of the workarounds for the 24H2 problem is to turn off auto HDR in the control panel. If rolling back to 23H2 is a no-go for you. I've removed all crashes (except for the occasional DX12 D3D issue) on my system, and they all seem to have been Microsoft Win 11 issues.
does disabling Auto HDR really help?
Can confirm. On Vulkan with Windows 11 24h2 latest update and drivers. Haven't crashed only like once a week with Auto HDR turned off.
|
Posted byImperius_Fate#0368on Jan 17, 2025, 4:05:48 AM
|
"
"
"
One of the workarounds for the 24H2 problem is to turn off auto HDR in the control panel. If rolling back to 23H2 is a no-go for you. I've removed all crashes (except for the occasional DX12 D3D issue) on my system, and they all seem to have been Microsoft Win 11 issues.
does disabling Auto HDR really help?
Can confirm. On Vulkan with Windows 11 24h2 latest update and drivers. Haven't crashed only like once a week with Auto HDR turned off.
It's a very strange game.
|
Posted byankeer#0343on Jan 17, 2025, 4:12:11 AM
|
|
I use Process Lasso to assign 12 of my 16 threads to POE. This way, if POE freezes, I still have an opportunity to close POE via Task Manager or do a proper restart.
It's not a fix but at least it minimizes hard resets. Granted, right after I downloaded the 0.1.1 patch, the POE still forced me to hard restart. I was able to access Task Manager and my Start Menu but was unable to end POE or Restart via Start Menu. First time this happened since assigning threads to POE 2.
GGG just seems to be more focused on adding new features versus addressing a major performance issue.
Never had I heard of a game not functioning on a specific version of Windows.
|
Posted byMyzer#3123on Jan 17, 2025, 4:30:43 AM
|
"
"
do NOT let the devs fool you into thinking this issue is a windows issue. 5 of my friendgroup who play, all crash. all different cards, nvidia/amd all diff types, diff cpu's, diff versions of windows, one of us even runs on linux ffs.
this is a POE 2 issue and GGG are hiding behind the microsoft update because it sounds better than "we don't know how we fucked up and we don't know how to fix it" they got a shitload of the diags, should be easy enough to find the pattern, and an issue this severe should have all hands on deck until its fucking fixed. not put what seems to be 2 guys to try and figure this shit out, nearing on 3 months of an unplayable fucking mess and i can't refund, can't do shit. I didn't want to, but i'm going to, i'm charging back the purchase of this fucking game, you cunts at GGG can eat my fucking chargeback fee. i won't be returning if this is how you're going to be acting moving forward, and notice, zero mention of compensation to all of us effected who cannot fucking play.
thanks for stealing $40 off me GGG. FUck you, i'll be getting that back real soon, about to call the bank and tell them i was sold a scam. and when i get refunded and you're hit with that chargeback fee, i hope theres 100,000 more behind it and any money you made from this bullshit early access period, is eaten by those fuckin chargeback fees.
I wholteheartedly agree but let's not be disrespectful. That's just what they want, an excuse to censor and shut down the thread and stifle and discussion about this gamebreaking issue. I want to keep these two 4000 reply threads on the first page so everyone that comes here sees it, maybe they won't buy the game if they realize the devs don't care about people that either can't play or need to rely on some random background application POE uncrasher just to play.
Disrespectful is GGG, we've paid for an access and we don't have even more information than "We working on fix".
This is disrespectful. We've paid money to support them and they pay us back by omit this problem.
|
Posted bySkundlony#4448on Jan 17, 2025, 4:38:36 AM
|
