TechAngel85

Not so much theory because that is how basic vsync works (this doesn't account for the various vsync options available because I don't know if they'll work or not, but rather standard vsync only) If vsync can't match the frame rate to the monitor's refresh rate, it'll cut the frame rate to the next available setting. It's is typically 2/3 or 1/2 of the monitor's refresh rate. In this case, since 2/3 would still be too high, it should have cut it to 1/2 which would have been 60FPS. I'm unsure if it would have cut it down further due to the game being modded, which would have been 40FPS and closer to what the user was experiencing; however, using my own system and other user's reported experiences as a reference, that's not how vsync should be working with Skyrim. I've only ever ran into this issue with users who have 120/144Hz monitors. Using a limiter has always been the way around the issue. So far no one has reported any problems and until they do, I have to assume this option is the best/correct one to take in such circumstances. It would be nice to officially test it, though.

What comments?

Is MO telling you is missing any masters? If it's only happening outdoors, I'd start by looking into any lighting/weather mods you have installed.

Then it has to be something in your mod setup. That's the only thing left.

We're aware.

It will only verify that the default game files are intact and replace them if not. It won't touch the other stuff. You may have to reclean the files in TES5Edit, depending on how you have them set up.

Those files aren't used: https://wiki.step-project.com/Skyrim_HD

I would uninstall it and then verify your game in Steam if you're sure the files are all being removed.

We only use the landscape textures.

And you don't have any leftover files after uninstalling the Preset? Are you using MO?

Thanks! I've checked out the file and it seems to match our recommendations. I've updated the mod page.

Change bFloatPointRenderTarget back to 0 when not using an ENB Preset or just using ENBoost. If you're using MO, do this change in MO using MO's editor for each profile.

Normally, that would be good advice, but that often doesn't work with newer 120/144Hz monitors as is evident in this case. There is no fallback (that I've ever seen) by limiting the framerate rather than using vsync in Skyrim. Triple buffering should remain on as long as there isn't any input lag. I generally like "blanket" solutions that work for all users, however, with the large varying degree of changes from system to system I simply don't think this is one of those cases. Especially when you consider the two completely different pieces of hardware involved (AMD vs Nvidia). We know just how differently these two can work just by looking at ENB. Vsync synchronizes the frame rate of the game with the monitor refresh rate. That's it's most basic function. If the monitor's refresh rate is higher than 60Hz (Skyrim's limit before issues happen), then you often get undesired results when you should be getting FPS equal to 2/3 or 1/2 the refresh rate; 80 or 60FPS, respectively. This typically works flawlessly on newer games, however, Skyrim isn't new and wasn't built for such technology because it didn't exist in the mainstream when Skyrim was being designed and released. The result is that we often see what was happening here. Using a limiter is a good alternative that has no side effects that I've never seen or been told about by other users. This is just another workaround for newer tech on Skyrim's old and clunky engine. It's not uncommon if you simply search it on Google. Also, your 30FPS comment is a matter of opinion and is subjective to the individual user. I know when Skyrim drops to those levels I most definitely can notice the gameplay is not as smooth nor fluid as it is at 45FPS+. 45-60FPS, imo, is the sweet spot for Skyrim. This is, of course, subjective as well. ::

I don't use either of the limiters so I wouldn't know. ::

None and I would normally recommend Nvidia's. I said to use ENB limiter because Winflakes said the limiter wasn't an option when looking in Inspector.

Z has been editing things without knowing what he's doing. I'll fix it.

Yes and no. I haven't myself personally due to Dilemma being a requirement of the STEP Patches. I simply don't have time to remove it for proper testing. But I would say this could easily replace Dilemma.

Pretty sure there is already a thread for this. Could be wrong. The STEP Female Overhaul (not yet released) is using some assets from this mod.

If it's just interiors, then you'll need to adjust the interior reflection settings in the ENB. If this is happening everywhere and not just interiors, it could be spectacular settings rather than reflections. Both can be tweaked in the enbseries.ini file.

Well, I've given this several days for the masses to tear apart my idea and it hasn't happened. So from this point on, I'll be moving forward with my plans to put the basement into its own worldspace (meaning you'll have to walk through a loading door to enter). My only concern is figuring out how to make the NPCs span across both spaces. Nothing to worry about at this stage since I haven't even dived into that stuff yet. I'll eventually have it set to once you enter the house, your follower will do their own thing.

As I mentioned, it's just for females right now but a male version will be coming eventually: https://www.nexusmods.com/skyrim/mods/70367/? EDIT I really wish CaBaL would finish up the rest of the armors.

Using ENB Preset?

No, it won't be used at all if it's turned off. Best bet is the hertz of your monitor is what's causing the issue. Turning off all vsyncs and limiting the frame rate should allow the game to run as fast as it can without going over 60fps, which causes havok issues.

There's another retexture for this armor that I'm keeping an eye on for Core. Just waiting for the male version to be released and that one will be tested against Core. It's a HD retex, where this one looks like vanilla textures that have been painted. I haven't looked at them directly, though, so they may not be.

Ah, turn off all vsync (driver, game, enb) and set the limiter in enblocal.ini to 59.9. That should fix it. Let me know of it does.