I don’t mention specifically to create custom resolutions (because I don’t know a single thing about your monitor and I don’t want to look it up if you told me), but if you do create a custom display through GPU driver, you can try this (I just don’t advocate it if the driver just seems to not include it as a default template).
Also, make sure Grim Dawn’s internal v-sync is off. There’s a conflict going I would think.
You also don’t need Anisotropic Filtering either. Turn that off.
If your nVidia’s CP is default, then you’ll notice the Negative LOD Bias is “Allow”. If you really need AF for some reason (which you don’t in Grim Dawn), you would “Clamp” it.
Just tested this.
In Arkovian Foothills, there are places there I can pull about 30 enemies.
Wait for it…
No Slowdown. No drop frames. High Settings (although Very High Shaders will cause quite a few problems - overheating my GPU being one of them - and it’s just too much by just a few percent; enough to tip it over in cycling the GPU’s clock frequency right down- which in of itself, is a whole other thread).
(I must be getting popular with the underground here).
*update, I’ve tried the Royal Hive; If anything, it’s the lesser of Arkovian Foothills.
Something else is going on. You’d have to be pretty specific to what’s happening - like temperature, possible over-heating… a dead rat in the PC.
Valve’s source engine absolutely refuses point blank any GPU driver’s V-sync model to control frames.
So let’s use Diablo 3 as an example.
It’s the same thing, with the exception that Diablo 3’s own internal V-sync must be switched ON.
I went over to a friends house playing Diablo 3 and seeing their screen tearing and the horrific stuttering was enough to make me push them aside and sort it out.
You should see people’s faces when Diablo 3 doesn’t just move nicely, it slides like silk in all directions… unless you’ve got a DH in the group that doesn’t know what “cooldown” means;
Then there’s only the serial API to blame.
Doesn’t happen on the PS4… But don’t get me started on that.
*just noticed the Portuguese bit; Just a plain old Brexit non-voter.
This will be the most important and last post in this thread.
Anyone still having problems with hz settings for their monitor, will just have to continue to figure out how to get their monitor drivers to show hz dependencies (50, 59, 60: particularly the former two) so that you then can choose 59hz inside of Grim Dawn so that nVidia’s Adaptive V-sync works near flawlessly.
It’s important that the GPU driver (nVidia’s CP) and your screen refresh, is not 59hz; it must be 60hz.
It won’t work any other way.
Very helps (near +10 FPS) set core affinity for grimdawn.exe when game is started - if you have 4 core CPU you must turn off 1 core (first one which is commonly used in OS with all the processes) in Task Manager, left other three for game. In options.txt i had set:
it helps me to set the background fps to max
no hard fps drops (30) anymore on bigger groups
just really rarely drops down to 50 fps
most time game runs smooth now with vsync (59.9/60.0)
Yes, there is. I’ve edited it like yesterday. And yes, now I can see two cores being used.
I’ve also noticed ridiculous CPU usage just when moving around your starting location (e.g. Crossing or Fort Ikon).
Edit: mine is under c:\Users<Username>\Documents\My Games\Grim Dawn\Settings\
I will write my ultimate verdict on this topic below;
Even this game is not well optimized, stutter and freeze issues probably are caused by win 10 au update and graphic card drivers. I was able to reduce my stutter and freezes to minimum extent by doing these (I DO NOT TAKE ANY RESPONSIBILITY, however i was able to decrease ram usage to 880 mb ram of windows by doing some stuff below.);
-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.
-Disable steam-overlay and steam-cloud for this game
-For nvidia users, for global settings choose single monitor performance, for the power management choose max performance for texture quality choose max performance and for v-sync choose adaptive.
-Disable in game v-sync
Recommended
-Download health check programs such as memtest, cputest, 3d mark to see if your hardware is working fine. Especially check mouse(and driver)!!. Even mouse can cause these stutters.
-Buy ssd
-Disable superfetch if u have ssd ( in windows 10 and 8, windows does it automatically)
-Keep using windows 7 till windows 10 is fixed
Not sure
-Download windows system timer tool and set ms to 1 or 5
-Disable pagefile
-Enable XMP in bios
-Disable indexing in windows if you have SSD
What i wrote above u, fix not just this game but others also.
Title is still valid because it is true. Games with better graphics, better psychics or better whatever have better and stable framerates ( shadow of mordor, battlefield). However in my updated post i was able to rule out some problems.
Editing that txt file helps but still there’s sometimes a stuter when you enter a new area, I don’t have an ssd but I think that it would help a lot with one.
