Releases: Kapps/PoEUncrasher
v1.4.0
This release mostly tries to be a little more resilient and persistent, as well as adding completely untested support for PoE 1.
I haven't been playing much PoE 2 lately, so I can't test this very much. Would appreciate any feedback if it actually fixes any issues people have recently started having with the previous versions, as well as PoE 1 support.
- Default to 4 threads parked instead of 2. I've noticed 2 sometimes isn't enough anymore.
- Be more persistent in trying to set the priority to real-time. I've found that sometimes it seems to not apply.
- Add support for PoE 1. Note that when the tool detects a version of PoE, that is the only version it will support until restarted. If you launched the tool with PoE 2 open, and you want to play PoE 1 instead, you will need to restart the tool after closing PoE 2.
v1.3.0
- Fix the version that doesn't require .NET triggering false positives in Windows Defender. No more having to have a .NET and non-.NET version as a result, will only be adding the standalone version now.
- Fix an issue where the tool crashes when trying to change affinity on certain CPUs (such as AMD 5950X/7950X).
- Have the tool request admin so you don't have to manually rightclick -> Run as Administrator every time -- thanks @d3vdev!
- Add support for Kakao client (Korean PoE client) -- thanks @d3vdev!
- Advanced option to specify the number of cores to park as an environment variable. You shouldn't need this.
If you're using the tool without issue, there's no need to update to this version.
v1.2.1
- Attempted a fix for an issue where the program crashed when trying to set the affinity on certain AMD CPUs (_950X CPUs generally). I can't test this, so this pre-release is an attempt at testing it for those who can.
- Added a workaround to hopefully prevent false positives by Windows Defender / Chrome.
- Advanced option to specify the number of cores to park as an environment variable. You shouldn't need this.
v1.2.0
- Found a workaround that allows PoE to recover after it freezes. Previously while your computer wouldn't freeze, PoE still would. I noticed though that setting PoE to realtime priority allows the threads that are stuck to get scheduled again and resolves it. This new version sets PoE to realtime priority if it detects that it freezes, and then sets it back to normal after the loading screen.
- Note that you will need to run the program as an administrator to be able to get PoE to unfreeze.\
There's two versions below you can download. PoEUncrasher.zip requires .NET 9 to be installed, but shouldn't be flagged as a virus by Windows Defender. PoEUncrasher - Non .NET.zip may trigger false positives from virus scanners but has no dependencies.
In either case, you will get a SmartScreen warning and have to click More Info -> Run Anyways.
v1.1
-
Add support for parking cores on game startup. When PoE starts launching, cores will now be parked until you load into your first map.
-
Add support for overriding the number of cores to park. For example, if you have a 9800X3D which has 8 CPUs / 16 threads, you can type in 14 into the window and hit enter to park all but one CPU. Parking that many cores prevents the game starting for me, though loading between zones still seems to work even at 14/15, which could (poorly) simulate disabling multithreading. I don't recommend it as it feels like it makes loading screens either too long or unstable, but it's an option for those who want to play with it. If you try it, I recommend only setting the override after you launch the game, as I can't get the game to launch at all with that many cores parked.