Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Also take a look at this guy's thread on Reddit I think.... https://www.reddit.com/r/HuntShowdown/comments/yze89t/horrible_stuttering_frame_drops_on_amd_system/
Look at that main response up top. Looks pretty thorough and maybe that guy points out something you might not have tried?
Sell it and buy an RTX 3070.
I'm not seeing anything substantially odd in the metrics, but I'm definitely observing some awkward pacing that not even the frame graph explains.
I notice though that once you set v-sync it clears it up.
This sounds like what I may have said earlier in the thread (but you answered with it happens even at 60 FPS).
If you want to dig further, enable the PCI Express link state utilization (can't remember what Afterburner calls it but it exists). I would highly doubt this is your issue but it'd rule it out.
This 100% describes it as a result of shader compilation. Every time driver version is changed, the shaders need rebuilt.
This is why consoles don't deal with this. The hardware is all the same.
PCs have too many combinations of OS, GPU, and drivers to make pre-compiling them practical.
FWIW, when I get up to anywhere around 5.5 GB (on a 6 GB GPU) and above, that's when I notice there's a chance the system starts dipping into system RAM for VRAM needs. The reason is you might have ~500 MB left, but the next allocation it tries to do might be a vast portion of that or even above it. Maybe it's the system "paging out" VRAM data that isn't immediately being used to keep something open for immediate VRAM needs (similar to how Windows itself deals with actual RAM management). It's close enough to be calling it into question for sure.
You know in that one reddit thread that I just posted (later realized it was a guy on an AMD system instead of Intel lol, but probably still relevant), one of the posts in there explains what you just said about textures and stuff needing to be re-compiled after driver or other kind of update. I just noticed that he kind of mentioned the same thing. So since it seems like he just mentioned it comes back after a driver or other update I'm wondering if that implies that AFTER the shaders are rebuilt is the gaming is perfectly fine UP UNTIL another update of some kind?
If so all of this is perfectly normal and expected behavior?. I don't remember him specifically stating if it happens like every single time he re-launches the game though even if he hasn't done any updates.
Edit: I'm confused again but about the video being 4k when I'm reading 1080p on it. Not sure if it was accidentally games/recorded at 4k or if it was recorded at 1080p but somehow upscaled to 4k?
Sorry I missed this part somehow.Of course I can make a new video of the part where it stutters the most
Right most games don't utilize 100% of VRAM and start consuming RAM at about 80-90% VRAM saturation,but Hunt is an exception to the rule.This game is coded so that it can't use RAM to compensate for the lack of VRAM.It just stops loading textures instead so if you play it on a 2-3gb card you'll notice a lot of texture popping and extremely low poly LODs.As i already said there was no stuttering on a 1060 3gb with high textures except the texture popping issue
Shader caching seems like a realistic explanation but still unreasonable. I mean how are you supposed to play an entire game with the thing stuttering like that JUST to re-build the shaders? Kind of ruins the game? are you supposed to re-play it all over again SIMPLY to re-build the cache then do another run-through to get the smooth experience? And then do it all over again when you update drivers? lol. WTF. That's crazy.
I don't get it, like I said it makes sense but it doesn't to me. I'm sure others are having a smooth experience, there has to be something up with your config somehow and yeah without hands on to see something that maybe we could see that you aren't catching, it's pretty hard to say.
And yes, this is 100% normal. I said it way earlier in the thread that I think OP might not have an "issue".
That being said, the first part of the video posted there does seem awkward and I'd say that might be some issue. High frame rates and relatively smooth frame graph but awkward choppy feeling (and it's just consistent the entire time so that's not really shader compilation, which is typically more brief when entering new levels/areas/whatever). Once they set v-sync it's 100% smooth though. I'm not sure what to make of that part. I'd personally just play with v-sync myself. 100 FPS means nothing if it's looking/feeling like that.
Yeah, I mean I think that is the whole problem to begin with. Up to now inexplicable. He'd be better with consistent garbage fps or even typical shader complilation than that choppiness.
I got the serious feeling with Serious Sam 4 which is why I didn't play it. Great fps and on paper it was a great experience but it was a permanent jerkfest only I really think that was just by design somehow. Just seemed off to me so I didn't play it. A lot different than this situation which seems much much worse at moment then clears up later on but still unacceptable.
When you re-installed Windows both times (or even previous times) did you install your directx thing? as well as your vcredistributables?
Those are two pre-requisites I always install first thing alongside actual drivers and all that stuff.
Do you do that? If not I would just to see if it helps any. Kind of doubt it will but I still do it out of habit and I never really have issues.
Directx I suppose you can just google, vcredistributables I get from here https://www.majorgeeks.com/files/details/visual_c_redistributable_runtimes_aio_repack.html
I'm not sure if someone will respond with "those have nothing to do with this and won't fix anything". They might even be right, but I still do it anyways and would try it if I were you. Obviously reboot after. See if it helps. Should only take a couple minutes.