Thief IV: stuttering

[RoboX]

My specs: I7 920@4GHz - GTX 670 - 6Gb DDR3 1600

The game has stuttering even if the frame rate is high (50-60 fps).
With all the graphics settings to the maximum I noticed the vram saturated, but also lowering some settings and then vram occupied, the stuttering remains.
I also tried to rename the folder of the 32bit to 64bit but I did not change anything.
Do you know if it is possible to solve?
Thank you

 

[FordGT90Concept]

I'm having the exact same problem. Ironically, we have the same CPU and amount of RAM. I'm thinking it might be because more memory is needed...

Edit: I'm 99% sure it's because of inadequate memory. "Free" memory in Windows Task Manager is zero or near-zero when the lag hits. Windows is not releasing standby memory (hovers at about 1 GiB, appears as "Cached" in Windows Task Manager) so the game stutters. This is probably why they made it 64-bit. Even though the 32-bit version of the game can't exceed 4 GiB of memory use, with an OS that can consume north of 3 GiB by itself means it will stutter in a 32-bit and 64-bit environment where there is 6 GiB of memory (it can only access 2-3 GiB).

You can use RamMap from Microsoft/Sysinternals to "Empty Standby List" For me, that freed up about 600 MiB that Windows was otherwise wasting.

 

[avatar_raq]

Same CPU (930) here. I had stuttering at first. I tried using the 32 bit version, forcing vsync and triple buffering by D3D overrider and finally turning off the supersampling in game settings. I think the latter did the trick for me back then and I got rid of stuttering once and for all. Now I am playing it @5760x1080 everything maxed out (apart from supersampling ofc) with 40-60 fps. While playing, I noticed that the game uses almost all of vRam (3GB).

Edit: Supersampling is called SSAA in this game.

 

[Dent1]

I don't mean to gloat,

If this happened on an ATI card you guys would be shouting "ATI's drivers suck". "Damn ATI and your micro stuttering".

 

[FordGT90Concept]

Edit: Supersampling is called SSAA in this game.

It was already off.

I don't mean to gloat,

If this happened on an ATI card you guys would be shouting "ATI's drivers suck". "Damn ATI and your micro stuttering".

It isn't microstuttering.

 

[RCoon]

I don't mean to gloat,

If this happened on an ATI card you guys would be shouting "ATI's drivers suck". "Damn ATI and your micro stuttering".

Well ATI don't exist anymore, so I suppose their drivers probably do suck.

 

[FordGT90Concept]

Memory usage is hovering around 4.5 GiB instead of 5 GiB and there's far less stutter.

 

[Dent1]

It was already off.


It isn't microstuttering.

9/10 even if it isn't micro stutter, everyone would still say ATIs drivers suck and no real help will be offered.


RoboX, your HDD might be slowing down, use HD Tune to measure read/write throughput

 

[Hilux SSRG]

My specs: I7 920@4GHz - GTX 670 - 6Gb DDR3 1600

The game has stuttering even if the frame rate is high (50-60 fps).
With all the graphics settings to the maximum I noticed the vram saturated, but also lowering some settings and then vram occupied, the stuttering remains.
I also tried to rename the folder of the 32bit to 64bit but I did not change anything.
Do you know if it is possible to solve?
Thank you

I'm having the exact same problem. Ironically, we have the same CPU and amount of RAM. I'm thinking it might be because more memory is needed...

Edit: I'm 99% sure it's because of inadequate memory. "Free" memory in Windows Task Manager is zero or near-zero when the lag hits. Windows is not releasing standby memory (hovers at about 1 GiB, appears as "Cached" in Windows Task Manager) so the game stutters. This is probably why they made it 64-bit. Even though the 32-bit version of the game can't exceed 4 GiB of memory use, with an OS that can consume north of 3 GiB by itself means it will stutter in a 32-bit and 64-bit environment where there is 6 GiB of memory (it can only access 2-3 GiB).

You can use RamMap from Microsoft/Sysinternals to "Empty Standby List" For me, that freed up about 600 MiB that Windows was otherwise wasting.

I have a setup similar to both of yours and don't doubt the 6gb or less memory is a factor.

But I've had luck in the last year and a half disabling HyperThreading or unparking cores to run BF3/BF4 and similar high performance games with all the options turned up.

Seems our aging Nehalems are finally hitting a performance wall, ehh?

 

[FordGT90Concept]

I watched the memory usage and the closer it got to 5 GiB, the worse it got. It was negligible/nonexistent between 4-4.5. By the time it reached 4.9 GiB, in-game cutscenes would get choppy. Restarting the game does help by forcing it to purge all data and start again with only assets it requires.

 

[avatar_raq]

I think the 64 bit client has a known memory leak issue. Use the 32 bit version. Also try disabling v sync in game and using D3D overrider. It might have helped to stop the stuttering for me, I'm not sure.

 

[mafia97]

Similar specs ,and I get massive stuttering

 

[Dent1]

Sounds to me a lot of people are having this issue. Could it be just a badly optimised game?

I haven't heard this much performance protest since GTA IV.

 

[Frag_Maniac]

I watched the memory usage and the closer it got to 5 GiB, the worse it got. It was negligible/nonexistent between 4-4.5. By the time it reached 4.9 GiB, in-game cutscenes would get choppy. Restarting the game does help by forcing it to purge all data and start again with only assets it requires.

For me it was mainly when I got near the spots where they were burning things, but now that I have 8GB instead of 6GB RAM, maybe I'll get less of it.

There are a few sites that have tweaks you can try, including PCGamingWiki, Steam forums, and one other if you Google for Thief stutter, but I'm not sure if they work. The 32 bit trick is mentioned and one on the Steam forum claimed it worked for him.

Seems hit and miss though with any tweaks for this game, it's just poorly coded.

 

[FordGT90Concept]

I don't think it is poorly coded, it's just more aggressive with memory than your typical game. This explains why it defaults to 64-bit out of the gate as well. The solution is more memory. The question is whether I want to spend $700 now for a Haswell upgrade or $70 for another 3x2GB memory.

It looks like everyone that says they get the massive stuttering have 6 GiB of memory. It's unique to Nehalem because Nehalem is unique in having 3 DIMMs per channel (6, 12, 24, 48 instead of 8, 16, 32, 64). 8 GiB is probably enough, 6 GiB is not because Windows is such a memory hog.

Eidos Montreal says the minimum memory requirement is 4 GiB. I suspect that is when using the 32-bit binary.

 

[Frag_Maniac]

It looks like everyone that says they get the massive stuttering have 6 GiB of memory. It's unique to Nehalem because Nehalem is unique in having 3 DIMMs per channel (6, 12, 24, 48 instead of 8, 16, 32, 64). 8 GiB is probably enough, 6 GiB is not because Windows is such a memory hog.

Well honestly, I don't recall getting "massive stuttering" even when I had 6GB RAM. More like intermittent stuttering where fires were burning.

I was in a very similar situation to you having 6GB DDR3 1600 HyperX, but I found when I added another HyperX 2GB module, it not only handled the same 7 CAS rated timings of my triple channel kit fine (single module is rated 9 CAS), my MB manual (ASUS P6X58D-E) said I could still run triple channel with 4 2GB modules. You just use a black and blue slot with two modules for the first channel, then two blue slots for the other two channels with a single module each. Honestly I don't know why these single modules are rated 9 CAS, it looks like the same exact module. It might be they only casually test them, vs stringently test the tri channel kits.

Anyways, between the release of other titles and my finding the game to be boring and repetitious, partly due to repeat petty theft to amass money, I haven't played it much. I still think a "memory hog" game with this level of graphics is still poor coding though, same with Wolf: New Order.

 

[FordGT90Concept]

I get it especially in the large maps like the Stone Market. It is particularly annoying during cutscenes because the audio gets out of sync with the video.

That configuration of memory would be dual channel, not tri (two DIMMs per channel). How you buy the sticks doesn't really matter so long as they can all hold the same timings and clock speed.

 

[Frag_Maniac]

That configuration of memory would be dual channel, not tri (two DIMMs per channel).

Straight from the manual...

...aaaand, if that's not enough for you...

I'm doubting the problem you're describing is RAM related. I had nowhere NEAR that kind of problem when running 6GB. It could have a lot to do with your GPU, plus it's only 1GB.

 

[FordGT90Concept]

The stick in A2 would be single channel. I thought you meant a stick in A1, B1, A2, and B2.

Background processes weigh in on memory requirements too. I always have Steam, Origin, Pidgin, and BOINC running. BOINC especially can take 1 GiB by itself.

Everyone that complained of stuttering had 6 GiB and a 920/930. That can't be a coincidence.

 

[Frag_Maniac]

The stick in A2 would be single channel. I thought you meant a stick in A1, B1, A2, and B2.

Background processes weigh in on memory requirements too. I always have Steam, Origin, Pidgin, and BOINC running. BOINC especially can take 1 GiB by itself.

Everyone that complained of stuttering had 6 GiB and a 920/930. That can't be a coincidence.

I explained it in detail even with the DIMM colors.

I don't see why you NEED all those background processes running.

Source of that stuttering only with 6GB or less claim please?

Have you tried the tweak to use 32 bit mode? Some on 6GB claim it works, but if all it takes is another 2GB module, why don't you just get one?

There's a myriad of descriptions, meanings and perceptions with ANY game when it comes to performance. One person's idea of bad stutter might be slight hitching when transitioning to new areas. Another's might mean continuous bad pauses.

Like I said, I ran 6GB on it and managed to find settings that rendered adequately smooth gameplay in most areas. I only got noticeable choppiness in areas where they had set things on fire. Then again I don't have all that stuff running in the background, and if you insist on using them, it's for THAT reason I'd get more RAM.

 

[FordGT90Concept]

I don't see why you NEED all those background processes running.

Steam, yes, because it is a SteamWorks title. Origin, can't be arsed to stop it (uses 120 MiB). BOINC, I could stop but I don't want to for obvious reasons. Pidgin doesn't use much.

Source of that stuttering only with 6GB or less claim please?

This thread. Four users have 920/930 w/ 6 GiB and all report the problem.

Have you tried the tweak to use 32 bit mode? Some on 6GB claim it works, but if all it takes is another 2GB module, why don't you just get one?

No, I have not used 32-bit because I know it will fix it. They had to decrease the aggressiveness of caching in 32-bit because there simply isn't enough space to aggressively cache in. It's a bandage for a more serious problem.

I have Star Citizen and its minimum requirement is 16 GiB. This is just the first game, of many to come, that have high memory requirements.

There's a myriad of descriptions, meanings and perceptions with ANY game when it comes to performance. One person's idea of bad stutter might be slight hitching when transitioning to new areas. Another's might mean continuous bad pauses.

When it does it, is very bad. I've been spotted many times because it happened at a bad time (there is no good time really).

Like I said, I ran 6GB on it and managed to find settings that rendered adequately smooth gameplay in most areas. I only got noticeable choppiness in areas where they had set things on fire. Then again I don't have all that stuff running in the background, and if you insist on using them, it's for THAT reason I'd get more RAM.

I'm only playing on Medium at 1920x1200. I don't see any noticeable slow down near flames. As I said previously, it is the worst during in-game videos (first time I noticed it was talking to Basso and the bird bit him) and in the really large maps (the map connected to the clocktower; won't do it the first time, it takes a while before it gets bad).

 

[Frag_Maniac]

If I were running BOINC, I'd probably relegate my previous PC to that, which I don't use anymore. God forbid if I actually had any Origin games, I certainly wouldn't leave it running. That's the one that baffles me most.

No link for that thread but four people isn't much to go by really, and I'm one whom on 6GB had nowhere near the problems you're describing. There has to certainly be others, it's just that most feedback threads are going to be complaints. Most enjoying a game don't bother talking about it on forums. I've also read one person say his performance got worse as VRAM use rose, and he was talking WAY above 1GB.

Yeah I agree stepping down to 32 bit is hard to take, but it seems to me it would be better than what you're describing, and this late after release I'm skeptical whether they'll ever fix the performance issues properly.

Yeah Star Citizen though is not your typical game. It has very realistic graphics and a LOT being rendered on screen at once. It's a good candidate for Mantle and last I read it was helping quite a lot. I'm just not sure if Mantle requiring less CPU also means less RAM use though.

I'm still not getting your response to why you aren't just adding another 2GB module to your current sys though? Are you saying you plan to build a new rig soon with 16GB instead? I might not build a new sys until DDR4, but even if I were building one soon, the $25 I spent to upgrade the RAM on this one is well spent I think. DDR3 is only going to get more expensive.

I don't recall performance issues ever being a cause of detection, I'm pretty sure I'd have remembered that. I'm picturing intermittent hitching so bad it greatly affects your speed and smoothness of going from cover to cover, and I didn't have that. Worse yet it would be unpredictable if intermittent, which could easily kill a good streak of sneaks. That's the main reason I'd use the tweak. We can't always be stubborn about settings as poorly made as PC games are sometimes.

Yeah my issues around flames though weren't nearly as bad as you described, even with higher settings. I never even considered dropping to Med.

When I get time I'll fire it up again now that I have 8GB to see if it makes much difference. It's been so long since I played it though that I don't remember all the settings I was using, or even if I used any cvar tweaks, of which there are many.

 

[FordGT90Concept]

Yeah Star Citizen though is not your typical game. It has very realistic graphics and a LOT being rendered on screen at once. It's a good candidate for Mantle and last I read it was helping quite a lot. I'm just not sure if Mantle requiring less CPU also means less RAM use though.

Unfortunately, Thief is. It may be the first PC game out (that I played anyway) that is ported from Xbox One/PlayStation 4. Both consoles have 8 GiB of RAM. The previous generation of consoles had 512 MiB of RAM and, when ported, they could consume 2-4 GiB of memory. That's 4-8 times as much. It is entirely realistic that console ports in 2-3 years could consume upwards of 32-64 GiB of RAM. This is why it is time to upgrade and not cut corners.

Oh and Star Citizen is made on CryEngine 3 which more titles on that engine are coming. They're just as likely to have high memory requirements as Star Citizen.

 

[Frag_Maniac]

t is entirely realistic that console ports in 2-3 years could consume upwards of 32-64 GiB of RAM.

Yeah I may very well go 16 GB on my next sys, so I get that part.

This is why it is time to upgrade and not cut corners.

Which is why I don't get why you've yet to add more RAM to your current sys, even refusing to bump down to 32 bit because of it. The alternative is sounding severe.

I don't know, maybe you're unsure whether adding 2GB would help enough. Does your MB support the 8GB triple channel scenario I posted above? I guess I assumed most X58 MBs do.

I guess what you meant was if you DO upgrade your RAM you'd only consider doubling it to 12GB? Well, to that I reiterate what you just stated. The new consoles have 8, and most games currently are not memory hogs, and most ports aren't SO bad that they consume THAT much more RAM.

I also can't help but think that this game, or even this game plus Wolf: New Order, are not good enough to warrant another 6GB tri kit, of which there are getting few. I just checked and Newegg only has two such kits in 1600.

This one @ $67 isn't bad though, and free shipping. Hell, I paid almost half that ($30) after shipping on just my 2GB module. It was mostly that I was being picky about getting the exact same modules though. Plus, filling all RAM slots has been known to increase latency.

(EDITED)
Just noticed, why do you have your 1600 RAM running at only 1066? Maybe that is part of the problem.

 

[FordGT90Concept]

My contention is that I'm not so sure the 920 will be adequate in the next five years. I have three choices:
1) Add 3 x 2 GiB ($70) to my current system bumping the total to 12 GiB. When Broadwell releases in about a year, upgrade.
2) Buy 3 x 8 GiB ($220) to put in my current system and transfer to a Haswell refresh upgrade when the time comes.
3) Do nothing until I decide to bite the bullet on a new/upgraded system.


Wolfestein: The New Order is another Xbox One/PlayStation 4 port to PC so it is likely to require a healthy amount of memory too.