They then restart game, and it does not crash anymore because data is now read from RAM cache instead of HDD. You can tell if, say, streamers on Twitch are running game from HDD if their game crashes during the cutscene where Teersa tells Aloy that the mountain is her mother. Since this is a console port, many things are tied to framerate, and sudden framerate drops cause crashes. HDD doesn't just affect loading times in this game. Not just textures but also high-resolution geometry and sound. HDDs are great when storage capacity matters, but they are causing issues in games because pretty much every modern game engine is streaming assets on-the-fly, even in non-open world games. This is why I finally ditched HDD and am only using SSDs now. Stuttering disappears if benchmarks are repeated several times because Windows reads data from RAM cache instead of HDD. Even putting pagefile on NVMe SSD doesn't help. Star Wars Jedi: Fallen Order cutscenes stutter on HDD but not SSD. Assassin's Creed Origins benchmark stutters on HDD but not on SSD (though game yields ~25% performance boost on HDD for some weird reason). Not just in this game but many others as well. I did move game back and forth between HDD and SSD, the difference is visible. It is a red herring.Įxcuse me, but this is not true. TLDR HDD wont affect frame rates or "hitching". The more GPU memory you have the more it can cache data without needing HDD access. What has a much greater effect is GPU memory. Unless you have a mechanical HDD from 20 years ago, then access time is irrelevant to frame rates. And since Windows uses a shared memory pool for the GPU system, it can easily stream textures to reserved memory and then in to GPU memory completely negating any access time issues. HDD & SSD access times only affect loading times and texture streaming.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |