Darklocq

4064 what? Is there more detail about this somewhere? I keep wondering how seriously to take claims/warnings like this years after they were originally posted, since the drivers and hardware and yadda yadda change over time, and smarter people than me figure out various workarounds. I've been trawling various forums, but a lot of them seem rather moribund (even over at NexusMods). But Skyrim should not be run without FPS restriction. Again and again people have demonstrated that doing so causes Havok to flip out, including mangling HDT-PE and HDT-SMP, but also just screwing up vanilla behavior. It's not even enough to constrain it to literally 60 FPS, but to 55 to 58 or so, because even at 59 it can spike over 60 and still cause Havok to go berserk. I have to wonder if this entire thread's horror story has a lot to do with failing to constrain the FPS to < 60. This isn't a 2020 game and wasn't meant to run at break-neck FPS rates. The engine (or, rather, specific parts of it) simply cannot handle it, and at some point our eyes aren't good enough to tell the difference anyway. Everything I've been reading on this over the last several years (plus my own experimenting) seems to suggest enblocal.ini settings of EnableFPSLimit=true and FPSLimit=57.0 or thereabouts, and iFPSClamp commented out in Skyrim.ini (let ENB do it; don't try to do it in two places at once or you'll get a slow-motion effect). I'm sure this is a YMMV thing like everything else, but this sort of advice is very common and quite consistent. If Sheson is correct that the "macro-stutter" problem is related to the engine trying to cycle through tens of thousands of trees per frame until it is done loading all the cells at the border, this could easily explain the issue. Why make it do that 100+ times per second when 50-something is adequate and safe? I'm on too much of a potato (actually a VM on a Mac!) to test this stuff out adequately, beyond tweaking things and noticing whether they improve the results. Any benchmarks I generate would be useless, since the "hardware" Windows thinks it is seeing is virtualized VWmare stuff allocated from my pool of actual Mac RAM and cores, and its performance depends heavily whatever else my Mac is doing in the background.