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
Im the OP, so Root Enumerator disabling worked for me.
idk why people think it's a good idea to say 'this works' without providing any supporting information whatsoever.
Very random, and not even always same place or enemy
Most recently had it while trying to clear asshat knight and his furry slave warrior(what else is going on there) at mr angry man’s castle.
Most of yest, didn’t happen, few of my tries tho? Ssttttttuuuuttttttteeerrrrr time, it’s to do with games “time step” mechanic, reading up on modders who make pause mechanic, exact same nonsense they describe happens when unpause where not stuttering(not other games stutter), it’s game catching up in span of a few frames
OP before make call give it at least ten hours game time, my bet is still there cos convinced it’s the game not hardware or OS related
you're not very bright
At best it's a 1-2% difference in overall performance anyways with it on.
At worst it can destroy performance.
It's not something I'd recommend permanently disabling, but can be temporarily disabled as a workaround for very specific games and use cases, and Elden Ring on some people's PCs turns out to be one of these use cases. It simply comes down to bad programming on FromSoft's side, who don't really have a solid understanding of how to correctly handle shader compilation on PC.