DoubleYou

You misread something. sD3DDevice, uLastAspectRatio, bShowAllResolutions, and bEnableFileSelection only work in SkyrimPrefs.ini, which was why there needed to be the exception in my statement for Skyrim.ini, since it cannot use those four values. Sorry. Now I'm confusing myself. In my experimentation I concluded that INI-Tweaks Composite overwrites everything everywhere. If that is the case, it cannot merely be creating new Skyrim.ini and SkyrimPrefs.ini files, because then Plugin INIs would overwrite INI tweaks, unless he creates a virtual plugin INI as well (highly unlikely). I think he batch searches all INI files and overwrites all INI settings in every INI in the system with those values if the value is present, and superimposes extras into the INIs somehow. I'm sorry, but that is just super-confusing. And it might not be correct. Therefore, we should ask Tannin. Any comments on the above-quoted definitions?

Then I think the problem lies with Steam and not with Mod Organizer. Fix Steam and that should fix Mod Organizer. That being said, I cannot see how you might fix Steam.

We will need to ask him, because I honestly cannot tell via experimentation.

But why? Why is your system special? Are you using an outdated version of Steam?

I disagree. We need a portal to talk about tweaks as a whole, and I was thinking of turning it into a guide for the effective use of the configuration settings.

I don't think it matters.

I consider all settings configurable except for the settings that Bethesda decided to leave out of the INIs (Arisu mentioned a figure like 5000).

Why do you need to run Steam in compatibility mode?

I would like this guide to be renamed. How about... Skyrim Configuration Settings Guide

They will work. They will need patches from several mods. I cannot give you a comprehensive list off the bat, as that requires inspecting all the mods to find which ones need a patch.

Download and install process_blacklist.txt into your ModOrganizer directory.

After extensive testing, these are the results: Skyrim.ini can modify all effective settings with the correct effect, including the settings that can be placed in SkyrimPrefs.ini (verified by checking if it could modify screen size) if the setting does NOT exist in SkyrimPrefs.ini, with exception of the four values used ONLY by the Skyrim Launcher, namely sD3DDevice, uLastAspectRatio, bShowAllResolutions, bEnableFileSelection (verified). It overwrites the default values hardcoded into the game executable.SkyrimPrefs.ini can ONLY modify settings with the SkyrimPrefs-allowed property hardcoded into the game executable. It overwrites the default values hardcoded into the game executable AND Skyrim.ini. These are all documented on the SkyrimPrefs guide.Plugin INIs can modify all effective settings with the correct effect EXCEPT the settings with the SkyrimPrefs property hardcoded into the game executable. It overwrites values in Skyrim.ini and/or the default values hardcoded into the game executable. This means that Plugin INIs can ONLY modify values that DO NOT go/work in SkyrimPrefs.ini. For example, you cannot effectively set shadow settings in a Plugin INI as the values will be entirely ignored.INI Tweaks as used in Mod Organizer can modify all effective settings with the correct effect including the settings with the SkyrimPrefs property hardcoded into the game executable. It overwrites ALL values for all settings, including Plugin INIs. If it doesn't seem to be working anywhere else, try here! Already done, and all those settings are on the guides.

Just tested iPresentInterval as an INI tweak, and it works, so INI tweaks may be able to overcome the limitations for SkyrimPrefs.ini. Test: Skyrim.ini with iPresentInterval=1 and INI tweak with iPresentInterval=0 Result: Test: Skyrim.ini with iPresentInterval=0 and INI tweak with iPresentInterval=1 Result: Also tested as a Plugin INI. Test: Skyrim.ini with iPresentInterval=1 and Plugin INI with iPresentInterval=0 Result: This proves that SkyrimPrefs.ini is the only INI in which iPresentInterval does not work.

Yes, but... -it requires a different format for external images -it doesn't glow -it doesn't add the caption text underneath it

Lightened.

Discussion topic: Template:GallerySimple Purpose & Usage Simplifies formatting of image examples under INI Settings guides. Performs a clear to force content to appear directly below floating content as well as the caption text aligned underneath the image. This is a template to add images to a INI Settings gallery more simply than by using the standard Gallery template. parameter img is the link to the image. It may be hosted locally (e.g. Image:MyImage.jpg) or externally (e.g. https://copy.com/1tY1UA6B0lhN83Ch). parameter caption is the caption. parameter id is the id for the gallery on the page. Images with the same id get placed in the same gallery. Change the id to separate galleries. parameter width is the width of the image thumbnails. Since it floats left, it is best to call the {{clear}} template afterwards. Differences from HigslideGallery plugin: HigslideGallery requires a different format for external images HigslideGallery doesn't glow HigslideGallery doesn't add the caption text underneath the image Example Code: {{GallerySimple|id=bShadowsOnGrass|width=250|img=Image:TESV-2015-05-28-15-24-44-93.jpg|caption=bShadowsOnGrass=0}} {{GallerySimple|id=bShadowsOnGrass|width=250|img=Image:TESV-2015-05-28-15-21-58-77.jpg|caption=bShadowsOnGrass=1 (default)}} {{clear}} Result: bShadowsOnGrass=0 bShadowsOnGrass=1 (default) I decided I needed a better way to create a gallery for the INI guides and such.

Well, my rig is not even baseline for STEP, so I would think I would know what low system performance it is. Indeed, it is this fact that has made me all the more curious about those ~1500 INI tweaks. As it stands, that information is nowhere in our guides and should be fixed. The closest we have is here, which is confusing at best. After much research in the INIs, calling these default possesses some issues, as there are parameters in them that are not recognized by the game anymore (gasp!). I consider default INIs to be blank INIs, which means the settings hardcoded inside the game are used. Leaving a setting out means that the hardcoded defaults are used. All the default settings cannot, unfortunately be accurately placed down in INI format, because some of the numbers are like pi: they cannot be expressed using decimal numerals. If you look at each guide I have created, you will see a link to default INI files for each, which are the hardcoded values (I found using the Configurator as a basis was less than useful). It is not perfect, and should NOT be used, but gives a good approximation of the defaults as can best be expressed in decimal numerals. Any mod in Mod Organizer can have a tweak in it. All active tweaks are combined and written to the initweaks.ini file inside the active profile's folder. The paperclip is only shown in the plugins list. I guess Tannin decided not to make it a flag in the mod list as that could clutter that up, and really you only need to see it in the plugins list. Game file: They are all located inside TESV.exe and can be retrieved via analysis, as per Arisu, and summary work with a hex editor on my part. However, you can retrieve a decimal approximation to four decimal places of all recognized parameters and their default values via the saveini command in the console when using blank INIs. I have used Arisu's more accurate decimals on top of those (it is quite apparent where they apply). Yes, if you mean in-game. All settings you change in the in-game menu are saved to SkyrimPrefs.ini. However, the Skyrim Launcher does set bReflectLODLand, bReflectLODObjects, bReflectLODTrees, and bReflectSky inside Skyrim.ini. Yes. Tweaks that are not recognized by the game have red descriptions describing this on the INI guides already, and "ineffective" settings (both verified and unverified) have yellow descriptions describing this. This is mostly finished already. This has been the result with every setting I've tested so far, with exception on those values which are numbers that cannot be accurately expressed with decimal numerals. Despite being valid, using those causes bugs. A classic case are the rUIMistMenu_Ambient settings, which the use of causes the menu to gain a red tint. I haven't sufficiently tested this statement yet. I do know that there is only a short list of parameters that work inside SkyrimPrefs.ini, but I do not know all the restrictions on Plugin INIs and MO INI tweaks.

Which is correct. Some values will only have an effect in Skyrim.ini, which is why I then point out... Only some values work in SkyrimPrefs.ini. These are hardcoded into the game itself. I am testing parameters to see what rules they follow. As to bShadowsOnGrass, the performance difference is negligible, similar to bTreesReceiveShadows.

But, when in doubt, test again, and I do believe it does do something, just not what you would have thought: bShadowsOnGrass allows objects casting shadows to cast shadows upon grass! Also, as some kind of byproduct, it changes the locations where grass is rendered. How did I figure that out? Below are three tests. First is with bShadowsOnGrass=1. Second is bShadowsOnGrass=0. Third is with bShadowsOnGrass=1 again. First and Third shots look identical, even though First was a setup shot and third was a save load of the same position. I had to check file hashes just to believe somehow they weren't carbon copies. The game is consistent on where it renders grass! Also notice that the Trees casting shadows actually show upon the grass when bShadowsOnGrass=1. In other news, I found out I can create 1920x1080 screenshots if I do it in windowed mode on my 1366x768 screen. Tune in tomorrow to where we hear of the tragedy of my laptop blowing up due to some obscure INI setting!

So that proves the problem is the SSD. Don't know if there is an INI tweak somewhere that might fix that.

ALL settings in SkyrimPrefs.ini CAN be placed inside Skyrim.ini and work, BUT settings in SkyrimPrefs.ini will take precedence over values in Skyrim.ini. Only settings with a hard-coded property attached to them will work in SkyrimPrefs.ini. Furthermore, settings in mod INI files (where an ini file is the same name as a plugin) will take precedence over values in SkyrimPrefs.ini and Skyrim.ini. For this reason I have contemplated removing the SkyrimPrefs INI guide and combining it with the Skyrim INI guide. Arisu when he collected all the INI settings for Skyrim in January 2012 found hundreds of settings, including bShadowsOnGrass, to be "not used anywhere in the game." The only place he was found to be wrong were with some controller related settings due to the fact that he did not have a controller connected. In game testing of fields of grass around Whiterun when I tested showed absolutely no perceptible difference with the setting on and off, the same being true for bDrawShadows. If the setting does anything, ENB must be reading it.

Thanks!

If that's the case, then I think the problem is with you SSD.

Well, you said you only have 6gb left, which to me is like saying your health is low in Skyrim. Why can't you move Skyrim on the SSD? Lots of people have done that without issue.