A lot of people with similar hardware are playing the game fine, so telling us to optimize solves nothing, since we have already optimized the game in numerous ways. Our testers and us play the game on a variety of hardware just fine with the correct settings.I have discovered the cause of my stuttering as the process which tells zombies to attack a block or swing at a player.
Each and everytime a zombie attacks a block, microstutter.
Each and everytime a zombie takes a swing at me, microstutter
When i enter a PoI and there are many awake zombies and some come out to fight me, often i cannot aim for s### because all the zombies in the building are creating constant stutters.
I just dont understand these fps issues anymore, for example:
I have a Ryzen 7 1800x 8x3.6ghz and a GTX 1060 6gb and between the microstuttering ruining the gameplay i usually have around 60fps.
My friend who has a slightly weaker computer; AMD FX 6350 6x3.5ghz and a Nvidia GTX 1060 6gb...(still a very good rig) who was next to me on the occasions we tested, reported that his fps dropped from 25-40 down to 5-10 when in encounters with zombies, becoming unplayable.
The AMD FX 6350 is still a great processor and he normally has great FPS...yet A17 seems to be slapping everyone in the face.
My wishes for the next version of 7D2D is:
-Optimize
-Optimize more
-Yet more optimizing
Many of us are running top end rigs and STILL having issues. You cannot continue like you are now, to blame US for YOUR poor optimization.
I was talking about windowed vs fullscreen modes and registry keys, not the bug with resolution changes. Now the same code could be causing that issue too.I set my resolution to 1600x900 for it makes a huge difference in my fps running a GTX1060 6GB. Sometimes I log in to find my resolution has been set back to 1920x1080 is this the same issue your talking about and or something else?
16gb (2x8) 2666mhz Corsair Vengeance DDR4 RamA lot of people with similar hardware are playing the game fine, so telling us to optimize solves nothing, since we have already optimized the game in numerous ways. Our testers and us play the game on a variety of hardware just fine with the correct settings.
I have a Ryzen 7 1800x and until I updated my GPU a few months ago, I was also using a GTX 1060 6GB and the game played fine for me.
I have 16 GB of RAM. How much to you have?
What resolution are you running at? It makes a big difference. With a 1060 1440p was bad for me, so I would not go above 1920x1080 and reflections should be at medium or lower.
I think the problem with topics like that is no one can agree with anything, making it difficult to separate fact from opinion. But I agree in that it was a good read.Interesting Gsync with Vsync read:
https://forums.geforce.com/default/topic/1002056/geforce-drivers/understanding-how-g-sync-and-v-sync-work-together/
If a game can't render at exactly 30fps or higher, it'll drop down to I think 15fps (aka half). It tries to hold a steady fps instead of allowing chaotic fps to go all over the place. It doesn't remove bad frames or the tearing you're talking about... it just "helps" prevent it by simply stabilizing the fps. So if you're averaging 25 - 29fps... it won't render at that fps at all... it'll just drop down to 15fps because that's the rounded number v-sync is programmed to render at.It would not halve their fps, it would give them what they're already getting. Your card doesn't magically find the ability to create twice as many completely rendered frames simply because vsync is off. If you card can handle 20fps with it on and 30-35 with it off, the extra you're seeing are incomplete frames, this the tearing.
Also, v-sync drastically improves G-Sync, as is mentioned many times on the nVidia forums. Capping a framerate is NOT the same as v-sync. You can cap your rate and still get half-rendered buffers sent through. V-sync simply times things and makes sure the buffer is full before flushing it.
I am pretty sure I explained that this problem no longer exists in the present day. D3D employs a flip cue that will provide filler frames at the very next sync interval. It doesn't always show the most recent frame available because of timing issues and the fact that it is not true triple buffering. That may cause some felt mouse lag at times or it might not.If a game can't render at exactly 30fps or higher, it'll drop down to I think 15fps (aka half). That's what v-sync does. It tries to hold a steady fps instead of allowing chaotic fps to go all over the place. It doesn't remove bad frames or the tearing you're talking about... it just "helps" prevent it by simply stabilizing the fps. So if you're averaging 25 - 29fps... it won't render at that fps at all... it'll just drop down to 15fps because that's the rounded number v-sync is programmed to render at.
Are you playing the game on an SSD? If so, which one (as not all SSDs are created equal)? Some SSDs are so terrible in performance, they might as well be a cheap hybrid hdd.Just adding here that the stuttering in 17.1 is out of control. I beefed up my rig recently with a 1080 GTX and 32 GB of ram ... and the stuttering is out of control. It's not a framerate issue per se, but moving the mouse right or left will often just STOP ... continue. It's like there are brief micro second moments of NOTHING and then back to normal. Last night it was terrible. No Z's, just me moving through my base and looking around at containers etc. STOP move STOP move. Going up a ladder FREEZE BLUR move BLUR move. At one point I was looking towards my spikes (no Zs or anything around) turned to move away, and in the middle of the 180 the game FROZE so much that Iw as actually back looking at the spike (full 360) and walked into them. It's worse than I ever remember in previous versions.
Thanks for the response. I never had this stuttering in 14 or 15, this happened when I rejoined in 17, but to answer your question:Are you playing the game on an SSD? If so, which one (as not all SSDs are created equal)? Some SSDs are so terrible in performance, they might as well be a cheap hybrid hdd.
Ok, that ssd isn't too old / dated, so that clearly isn't what's causing it. (as there is a stutter issue that relates to hdd bottleneck, but I haven't seen anyone with a decent ssd have that issue yet)Thanks for the response. I never had this stuttering in 14 or 15, this happened when I rejoined in 17, but to answer your question:Samsung 840 Pro 512GB SATA3 2.5inch SSD
I can easily move this to a Western Digital Black 1TB SATA3 for testing purposes.
I've seen that in procmon, but I don't think it amounts to much, since it is a small file, but I don't think it needs to be doing that on a regular basis.