Still having micro-stutter issues after latest update 1.0.0.5 CRUCIBLE HOTFIX 2.
AMD Phenom II 6-core CPU
8 GB RAM
AMD Radeon 6850
Windows 10 fully patched.
Tried everything. Options.txt, CPU affinity, windowed, boderless windowed, 640x480 with all graphics settings either “off” or “low” … still get micro stuttering throughout game. It ran fan before last update.
Pissed that I spent money on a game that looks great standing still, but that’s about it.
1035 T, but this CPU runs Diablo III on 1920x1080, high settings, AA, vsync, etc. … with zero stuttering and a very rare fps drop, mostly due to internet lag.
I realize my box isn’t “new” by any standards, but neither is the TQ engine that GD uses. Just frustrates me that a game using an “older” graphics engine, running on an “older” PC like mine stutters and hiccups like mad, where latest build of Diablo III is smooth as silk on same hardware.
Stuttering also happens on same rig when booting to Windows 7.
I realize it’s “not Crate’s problem” but still. Very disappointing.
If this is true, then maybe it will be fine again after next update. I had a laptop that was giving me all sorts of issues, and I swear some builds worked fine and with others, the laptop chugged more than usual. But I have nothing factual to provide, just hope that when 1.0.0.6 hits, you might find things are back to as they were again.
The AMD 7970m was the main culprit as it was replaced and then died again. Game runs fine on low settings with the integrated GPU now.
try windows 10 and bios tweaks if you know what you are doing. Even it does not fix the game, it will fix others or prevent future ones.
-Disable c-state in bios
-Disable EIST ( intel speedstep technology) in bios
-Disable intel thermal monitor and c1e in bios ( if u trust your fans!! dont do otherwise)
-Disable HPET(both in windows and bios) or Enable both of them. To enable it in windows right click cmd as admin bcdedit /set useplatformclock true , to disable it bcdedit /deletevalue useplatformclock ( if disabling gives error, it means it was never enabled in first place so it is fine ). Many argue disabling hpet increases performance some otherwise. Important point is their situation must be same in bios and windows. Try and see
-Disable auto-fragmentation schedules.
-Download windows tweaker tool 4 and disable everything under privacy and turn off track user data. That tool can not completely disable telemetry so google for it
-Disable cortona in windows 10 ( google )
-Disable “Get to know me” in windows 10 so click “stop getting to know me” ( google)
-Disable unnecessary services such as sync driver and onenote sync driver. There are tons of unnecessary services so google them.
-Right click taskbar click task manager and go to startup and disable many unneeded programs there.
-Go to control panel, click power options, click high performance and click advanced power options then find processer management one check they are %100 for both minimum and maximum
-Disable steam-overlay and steam-cloud for this game
-Disable in game v-sync, enable your card driver v-sync or rivaturner afterburner one
Turn down shadows, off if you can do without them and lighting. Always having troubles with amd when it comes to shadows. Maybe set up a frame limiter in radeon settings too, just below the refresh rate.
Are we talking micro-stuttering here, or “hey boss just wait while I figure this out” .5 - 1 second of freezing?
Thanks for all suggestions, but already tried all VSYNC options … vsync in-app on, vsync in-app off, vsync in Catalyst CC on, vsync in Catalyst off … shadows on, shadows off, shadows low, shadows, high. Windowed. Windowed borderless. Different resoutions, etc.
Still having micro-stutter. As in: every few seconds, when walk . ing . around, the game stut - ters andthencatches up.
Pretty consistent. Worse during battles, but it _was_working before latest build.
I have an AMD 1100T 6 core and the HD6970 card with 8GB of ram and no issues with this. I run win7 though not 10 so this may or may not be the issue. My setup is similar enough that I would think the problem is not with the hardware but something else in software.
You can add it to a regular shortcut. What it does is change how Grim Dawn saves the game (which it does regularly) to trade off some protection against save corruption due to crashing, for faster saving. Some system configurations seem to cause stuttering due to very slow disk writes.
It may or may not be your issue, but it might be worth a try.