DoubleYou

MO copies your INI files from My Games\Skyrim the first time you start it up and uses those same INIs on any new profiles you create. That's why it's in all your INIs. You must have added it when modifying your INIs sometime previously, as there is no way the game itself put that line in Skyrim.ini, unless an older version of the Skyrim Launcher used to do that (and I'm not going to test all the ins and outs of outdated Skyrim Launchers, as even the current one is quite messed up). The line will never affect your game in any way, as it does nothing and is unknown to the game.

Default INIs shouldn't cause the following however: 15:57:26 [D] sD3DDevice in wrong ini file (skyrim.ini, should be skyrimprefs.ini)So I take it you erroneously added this value, or else MO has a bug in its INI detection, which is possible. The following 15:57:26 [D] unknown ini setting uMaxSkinDecalsPerActoris caused by the fact that not only is the setting in the wrong INI file, but it is also misspelled by default (uMaxSkinDecalPerActor and not uMaxSkinDecalsPerActor). The rest is as explained in the console.

FRAPS outputs high filesize. Probably he ran it through Movie Maker to reencode and upload to youtube. I always just use ffmpeg, but I guess not everybody is a fan of the command prompt ;)

I think we have NebuLa's permission to use the texture we have of his in our setup, so if it was banned it probably could be solved by adding it to the STEP Texture Compilation.

Well, to be honest, I'm still somewhat skeptical on the issue, and I would like to back-date some loose files and see if this is an issue at all, or if it was some fluke somehow. I've been meaning to do an in-depth study of AI across the games, but have yet to do so, as other things take greater precedence. It by no means can harm Skyrim users to back-date their BSAs, so I've just left it at that for the time being.

I'm pretty sure it makes no difference when you click the Back-date BSAs button. Is someone creating a new mod from 2000?

One thing I find interesting is that Bethesda added sResourceArchiveListBeta with the official 1.6 patch without a word. I wonder if this new setting is capable of loading BSAs in a different manner.

Thanks! Great catch!

It's on the Mod Organizer page... the Mod Organizer wiki... how many places need I to have it repeatedly written down???

I just started working night shift, so I know what it's like to be in hyper drive. Get yourself a good binaural beats app and that should help you sleep.

The right card being selected in the Skyrim Launcher or SkyrimPrefs.ini does not matter at all. You need to use either the injector version of ENB or use the Nvidia Optimus Fix.

Another little known tip: holding the right mouse button on the map menu will allow you to rotate the camera. This is extremely useful those times when you cannot get to the map marker because the map menu is angled in such a way to disallow you from clicking it. You can tweak how much it is allowed to rotate using some tweaks mentioned on the Skyrim Configuration Settings Guide.

And they shouldn't. Those two settings were removed from Skyrim in the official 1.6 patch. I didn't think they were popular or even known, so I decided to not even mention them. If there is a popular guide that uses them, I guess I could add these to the guide to explain that they are outdated and no longer do anything. As to the Configurator, it may order the settings and sections differently, but that is at its author's discretion. The INI guide is best understood when arranged lexicographically descending, with each of the prefixes separated. The Configurator has rather randomly arranged sections and mixes up the prefixed settings.

Could you give your modwatch? (See my signature)

It isn't related to the textures being used on objects, say, the wall texture. I've seen this all over the place and thought it was just a bug in the shadow system until TechAngel's observation. What I believe was happening was that, due to the value being the wrong size, it would flicker between the set size and the nearest correct size.Shadows and textures being used don't matter.fShadowDistance doesn't affect iShadowMapResolution (I believe). There is a bug with vanilla shadows where there is an obvious change in the shadow quality at low fShadowDistance values that I believe is hardcoded (the shadow LOD settings appear to be non-working). The solution is to move fShadowDistance out farther to 4000 or more. See the videos showing this effect here: https://wiki.step-project.com/Guide:SkyrimPrefs_INI/Display#fShadowDistanceGood question. Testing this with the cell borders on might prove useful.

Ok, I have thoroughly tested your theory, and I believe you are correct. I tested with 1000, 1022, 1023, and 1024, and the only one that didn't show the issue at all was 1024. It would seem then that the shadow map might indeed be influenced by a texture, and by setting it to the incorrect multiple of that texture, it flickers. Great find. Now, that entire behavior was the reason I forbade high fShadowDistance settings in vanilla. With that discovery we can put that back up to 4000 again. ENB does its shadows quite differently and it doesn't surprise me that it has no issue with those settings. Edit: Updated OP with new recommendations.

Thanks for the report. Will test. That may prove to be an invaluable observation, although I sincerely doubt it. It is more likely that the increase or decrease in resolution reduced flickering in the locations you were observing.

Finally tested that little setting, and it is useful. I've added it to our recommended changes.

I am aware of that post. I also will have you know that the majority of what people have said about these shadow settings have proven to be false. For example, iShadowMapResolutionPrimary and iShadowMapResolutionSecondary, mentioned in that post, are not even recognized in the game! Please observe the https://forum.step-project.com/topic/3758-shadow-optimization/ as well. ZPrepass is a method used by games to try to prevent rendering of objects that cannot be seen for a possible performance boost. If Bethesda had something else in mind in the creation of bShadowMaskZPrepass, it is rather doubtful. But, bMainZPrepass is undoubtedly used for this purpose, and has proven to be exceedingly buggy. Since the main ZPrepass is buggy, we have determined to leave bShadowMaskZPrepass off until it is found to be both a) useful and b) bug-free. Currently, however, in my limited testing, I have not found it to produce any effect whatsoever.

Added several map menu tweaks

You should probably have noted that these settings are in the [Camera] section. Most of these settings have never been tested. Indeed, try googling some of these settings. I've been happy to notice that this guide, with as limited information as it has, is at the top of the list. They most likely do something that we haven't figured out yet. Notice that the ones with "Fly" in them were added with the official 1.8 patch, which introduced Dragonborn combatibility. That is a strong hint that it has something to do with dragons, and I'm presuming perhaps when the player is mounted on a dragon, or perhaps the other settings when mounted on a horse??? Guessing. Bethesda didn't hand out a manual.

Tweak of the day: Skyrim.ini [MapMenu] Increase map menu rotation range fMapWorldYawRange sets the yaw range that the map menu's camera can turn when the right mouse button is pressed. Setting this to 400 allows the user to rotate full circle once. Increasing this beyond 400 allows the user to rotate more than full circle. Obsessively high values (e.g., 3600) induce crashes. fMapWorldYawRange=400

If you use Unofficial Skyrim Patch, the setting is in its Plugin INI.

I'd bet that it's the SSHD drive that's making the difference. I bet SSD users have no trouble with 4096. For some time I've noticed the issue he describes on my own machine: footsteps, especially from horses, eventually cutting out altogether. I've never earnestly tried to fix it, but this points me back in that direction again most certainly. I'm on a regular HDD.

Added information about settings that have been added/moved/changed across official updates