It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Grim Dawn has options in C:\Users\YourName\Documents\My Games\Grim Dawn\Settings >> options.txt
In here there are 2 lines:
forceSingleProcessorMode = false <<this says use more cores>>
maxResourceThreads = 8 <<this says how many cores>>
While this helps very little the real trick is in forcing Grim Dawn.exe's affinity in the taskmanger. I'll quote the original creator/discoverer for this part:
Like some of you, I too found Grim Dawn weighing heavily on just one CPU core while the others are twiddling their thumbs most of the time. Then I remembered that some games in the past have had issues with Hyperthreading.

To cut to the chase, apparently so does Grim Dawn. Using the Task Manager to set CPU affinity to every other core starting with core 0 checked and core 1 unchecked lessened the clogging on core 0. Instead of at or near 100% core load in Devil's Crossing right after loading the game, I'm now at a comparatively very comfortable 60% to 80%, and that's with all game settings maxed out, including 8xAA and 16xAF. The overall effect on the game when playing is that I'm now at 60FPS more often than before, though still not always. ~ Lasse B.
Now this is a Pain In The *** to do every time you play the game, that is why Lasse B. coded a quick application to sit in the tray and wait for the game to launch on Grim Dawn.exe, again in his words:
If you want to apply this method regularly, I've written a tool that applies the changes to CPU core affinity automatically when it detects Grim Dawn. Both executable and source code are on GitHub: https://github.com/Lasse-B/GD-CPU-Affinity ~ Lasse B.
So there ya have it! A rapid fire solution to this issue. I went from 20FPS with all settings low to medium in Crucible levels and main towns to 60+ with every single option turned on high/very high, It works a treat!

Another quick fix (and a standard for all games) is to make a custom profile for Grim Dawn to apply V-sync and Triple buffering. Now if you get consitantly 60+ FPS in Grim Dawn without V-Sync you want to use FastSync. If you cant hold 60FPS Fast Sync will hurt your performance and add stuttering. >60 means old school V-Sync or G-Sync if you have it.

Anyways, happy hunting all and let me know if you have any questions or how much this helped you. Maybe a sticky sometime down the line ^_^

SOURCE
avatar
Starkrun: Grim Dawn has options in C:\Users\YourName\Documents\My Games\Grim Dawn\Settings >> options.txt
In here there are 2 lines:

forceSingleProcessorMode = false <<this says use more cores>>
maxResourceThreads = 8 <<this says how many cores>>
avatar
Starkrun: While this helps very little the real trick is in forcing Grim Dawn.exe's affinity in the taskmanger. I'll quote the original creator/discoverer for this part:

Like some of you, I too found Grim Dawn weighing heavily on just one CPU core while the others are twiddling their thumbs most of the time. Then I remembered that some games in the past have had issues with Hyperthreading.

To cut to the chase, apparently so does Grim Dawn. Using the Task Manager to set CPU affinity to every other core starting with core 0 checked and core 1 unchecked lessened the clogging on core 0. Instead of at or near 100% core load in Devil's Crossing right after loading the game, I'm now at a comparatively very comfortable 60% to 80%, and that's with all game settings maxed out, including 8xAA and 16xAF. The overall effect on the game when playing is that I'm now at 60FPS more often than before, though still not always. ~ Lasse B.
avatar
Starkrun: Now this is a Pain In The *** to do every time you play the game, that is why Lasse B. coded a quick application to sit in the tray and wait for the game to launch on Grim Dawn.exe, again in his words:

If you want to apply this method regularly, I've written a tool that applies the changes to CPU core affinity automatically when it detects Grim Dawn. Both executable and source code are on GitHub: https://github.com/Lasse-B/GD-CPU-Affinity ~ Lasse B.
avatar
Starkrun: So there ya have it! A rapid fire solution to this issue. I went from 20FPS with all settings low to medium in Crucible levels and main towns to 60+ with every single option turned on high/very high, It works a treat!

Another quick fix (and a standard for all games) is to make a custom profile for Grim Dawn to apply V-sync and Triple buffering. Now if you get consitantly 60+ FPS in Grim Dawn without V-Sync you want to use FastSync. If you cant hold 60FPS Fast Sync will hurt your performance and add stuttering. >60 means old school V-Sync or G-Sync if you have it.

Anyways, happy hunting all and let me know if you have any questions or how much this helped you. Maybe a sticky sometime down the line ^_^

SOURCE
Hey Starkrun!
Have the same issus but always get the 'Code 6' error code, when starting Grim Dawn after launching the script.
Any advice on how to change it?
avatar
Killerkarotte743: always get the 'Code 6' error code, when starting Grim Dawn after launching the script.
Any advice on how to change it?
So you launch the GD CPU Affinity.exe application and then GrimDawn and you get an error? the EXE looks from Grim Dawn executable and then applies the affinity tweaks. Can you launch Grim Dawn without the tool running?