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
if you play with 100fps, so to AVOID this spike, your system would have to write 5MB to the hard drive within a hundredth of a second. So a writing speed of 500MB/sec while your nVME is busy loading follow-up data as quickly as possible. So it's a bandwidth problem
In fakt: this spike depend on your system/nVME AND framerate.
50fps would double the time window to write the 5MB to the hard drive, ergo: less fps = less traversal and savegame stutter
Because, not only are we losing some frames, but inputs executed during the stutter are not effective. I play a lot with the perfect parry and it's become unplayable.
And is not about the ssd, so far I've seen this happen on 6000mb/s gen4 ssd, on 5000mb/s gen 4 ssd, and on 500mb/s sata ssd.
The save file increases with time and progress, guess that's why the stuttering gets more pronounced the longer you play. It's really starting to bother me. On my system the game is installed on a very fast gen4 NVMe and Windows (where the save location is) on a different fast gen4 NVMe.
I suggested to get off the 30 sec autosave, only do it when not moving/fighting or do incremental saves with very small file sizes; anyway, saving should be async if possible.
I don't understand these autosaves at all, unless they were a desperate last second measure to prevent progress loss because the game was so prone to crashing. But I'd guess the autosaves are also the reason for savegame corruption - when the game crashes while saving.
If the game was stable - and I didn't have a crash for a week - it would be sufficient to only save at Vestiges or when you exit to the main menu, no?
I wish we could disable autosaving by command line option. It's superfluous if the game runs stable for you.
https://forums.guru3d.com/threads/importance-of-pagefile-for-gaming-smoothness.447687/
https://imagizer.imageshack.com/v2/394x518q90/924/lHwTmG.png
"recommend setting Windows manage the pagefile size. But to be clear, the pagefile size is not important. What is important, is having a pagefile on the same drive that the game is installed on, because as I have stated, Windows restricts memory usage when a pagefile is absent.
This is especially true for high RAM using games like Hogwarts Legacy which stream lots of data."
also steam startoption for lords of the fallen -NoTextureStreaming
if user is on nvidia use driver 357.58 every driver above till the latest one has issues in stuttering, texture flickering and lightning glitches
after everything is done you have 95% better smothness
use everything whats explained steam startoptions aswell -NotextureStreaming
you can have 128gb of RAM but when windows restrict the usage without a pagefile then your system is limited
https://www.youtube.com/watch?v=B_bGg98n6Gg
Stutter and autosave symbol always at the same time.
you can try it or let it be its in your hands
on my system https://valid.x86.fr/87majn everything on ultra and on 1440p
looks like this https://www.twitch.tv/videos/1970269774
here and tghere after 4 hours+ there is some hickups but nothing big to notice
Which game version was the recording made on?
And I'll try your suggestion tomorrow.
game is up to date
on a Samsung 970 EVO Plus 1TB
i think you can google everthing else you need