Jump to content

DoubleYou

Administrator
  • Posts

    7,933
  • Joined

  • Last visited

Everything posted by DoubleYou

  1. Sorry, my mistake. Been staring at INI settings too long. Don't know where 3000 came from.
  2. If you use the latest version of SkyUI, you must use 1.7.3. No reason not to at the moment. No known detrimental bugs.
  3. Please make sure all BSAs are checked in the Archives tab, particularly the Skyrim - Meshes.bsa, and try again.
  4. Higher resolution screens should alter iShadowMapResolution to their screen width, as I have already indicated. Also, remember these settings are for vanilla, non-ENB users. fShadowDistance, which you have very high, seems to be very buggy, unfortunately, at high settings. It causes flickering on shadows that are too far away in my testing, and may increase shadow pop-in. Unfortunately, it is also buggy at low levels, causing a distinct line of change. Default is 2500 and Ultra setting is 3000. I found 2800 to be the better compromise. ENB users should be able to increase this with no problem. bDrawLandShadows is already in the Skyrim Configuration settings guide and can be toggled on/off at will for better/worse performance. I haven't tested it if is buggy or not. bShadowsOnGrass is already in the Skyrim Configuration settings guide and can be toggled on/off at will for better/worse performance. bTreesReceiveShadows is already in the Skyrim Configuration settings guide and can be toggled on/off at will for better/worse performance. fShadowLODStartFade -- I simply haven't been able to figure out if this setting does anything at all. Currently I think it does nothing.
  5. I am recommending the following settings for shadows after my testing: [Display] bDeferredShadows=1 bShadowMaskZPrepass=0 fInteriorShadowDistance=4000.0000 fShadowBiasScale=1 fShadowDistance=2800.0000 iBlurDeferredShadowMask=4 iShadowFilter=3 iShadowMapResolution=1366 ;set iShadowMapResolution to your screen width
  6. Revised Recommended changes section to follow a better format that will allow more INI tweaks to be added easily and prevent possible errors.
  7. What are we deleting/hiding?
  8. Install Skryim to SSD (quick trick: copy and paste the files to the new location and Steam will auto-discover them if they are in the right location) Install MO to Skyrim Change directory of downloads to HDD Profit?
  9. Perhaps what you want is to alter fBookPosHeightPercentage and fBookPosWidthPercentage in Skyrim.ini under [interface] https://wiki.step-project.com/Guide:Skyrim_INI/Interface#fBookPosHeightPercentage
  10. Some INI facts to chew on that I've added to this guide: INI syntax The INI files follow this basic format: [Section]setting=valueThere are some rules about this structure that must be observed generally and specifically. General rules Spaces are ignored before and after [sections], settings, values, equal signs (=), and square brackets ([ and ]). That means that setting=value will do the same as setting = value .A setting cannot accept a value that is on a new line. That means that the following value will not be used:setting=valueComments do not exist, yet they do exist, because they do not exist. In essence, a comment is read as a setting that merely does not exist, and therefore does not affect anything, allowing it to exist. Comments should only be placed on a line that does not contain a setting, lest it be mistaken for a value of a setting.[section] rules [section] names are case insensitive. That means that [Display] and [display] will be read as the same.There may only be one [section]. Duplicate sections will not be used in any case. If more than one section exists, only the first one will be used. This means that if [Grass] exists at the top of the INI, and another [Grass] exists at the bottom of the INI, only the top section will be used, even if the second section contains settings not listed in the top section.Setting rules Setting names are case insensitive. That means that iPresentInterval and ipresentinterval will be read as the same. There may only be one setting. Duplicate settings will not be used in any case. If more than one setting exists, only the first one will be used. This means that if iPresentInterval exists at the top of [Display], and another iPresentInterval exists at the bottom of [Display], only the top setting will be used, even if the first setting is blank.The setting's name is defined as all characters between the start of the line and the equal sign (=) underneath a [section].The prefixes Each setting has a lowercase prefix and a name. The name identifies what the setting modifies. The prefix determines what kind of value the setting can accept. Below is a list of the different prefixes and their meanings. b-prefix settings accept a Boolean value of 1 (true) or 0 (false).f-prefix settings accept a floating point numeral value (any rational number, positive or negative, with or without a decimal, such as 5, 0, or -38.0003). Some default values for these settings can only be estimated with decimal numerals (think π). Floating point values may use exponential (e) notation. In exponential notation, the number before the e is multiplied by 10 to the power of the integer after the e (e.g., 1e7 equals 1 with 7 zeros after it, i.e., 1,0000,000 and 1e-7 equals 1 with 7 zeros before the decimal point, i.e., .00000001).i-prefix settings accept an integer value (any whole number, positive or negative, without a decimal point, such as 5, -38, or 0). Integers are limited between -2147483648 and 2147483648 (2 x 1024 x 1024 x 1024).r-prefix (including some s-prefix) settings accept a color value in RGB (e.g. 93,216,234) or possibly even RGBA (e.g. 93,216,234,1) format.s-prefix (also str) settings accept a string value (usually text, but may contain numbers, punctuation--anything really).u-prefix (also ui) settings accept an unsigned integer value (any whole number, only positive or 0, without a decimal point, such as 5, 38, or 0). Unsigned integers are generally limited between 0 and 2147483648 (2 x 1024 x 1024 x 1024), however some may incorrectly recognize negative values.Value rules The value is defined as all characters between the equal sign (=) and the end of the line within 255 characters prior to the first character that the setting will not accept.A setting will accept whatever value is given it, but will stop accepting that value if it goes outside the range which that setting is allowed to accept, determined by the type of setting it is defined as per its prefix (e.g., iPresentInterval=1;disable is read as iPresentInterval=1 and sIntroSequence=BGS_LOGO.BIK;disable is read as sIntroSequence=BGS_LOGO.BIK;disable).If a setting has a blank value in the INI, the default value will be used instead of a blank value except for string settings (those with an s-prefix), where setting it blank will cause the string value also to be blank.
  11. -LOOT's installer now uses Inno Setup instead of NSIS. YES!!! LOL. I just love Inno Setup... makes wrapping things up into a handy installer for all my non-geek friends so much easier.
  12. Make sure they are enabled in the left pane.
  13. Okay, so I watched the video and... I can't even see a difference. Is this mod really a great change or something? I can't even see it!
  14. I still haven't updated
  15. Our "hide" instructions are MO-specific, as indicated by the MO icon.
  16. Check overwrite and ensure that it is empty. You say your INIs in MO and in My Games\Skyrim are identical, yet you say the one skips the Bethesda logo and the other does not. That indicates that your INIs are indeed different. Please post your MO INIs (Puzzle button --> INI Editor). Place in spoilers: [spoiler] Content [/spoiler]
  17. From the wiki: "If you receive a This application cannot be started message, most likely you forgot to enable the mod in the Left Pane." Please enable the FNIS mod.
  18. Get WinAero tweaker. Since you disable UAC, you will find a number of problems with "disabling" it, as it doesn't completely disable itself (at least last I tried it). You will want to disable it and enable the Admin account and use it.
  19. SSME and ENBoost is not the same thing. SSME is the same as SKSE with the skse.ini memory settings. If you drop ENBoost, Skyrim will again have the 3.1 GB memory limit.
  20. You can install, and probably need to install, version 3.5. Everything else is included... I think.
  21. The double launcher problem is caused by the fact that MO currently inserts the wrong App ID. That is why you must change it to 22330. If it doesn't possess the correct App ID, MO will attempt to launch Oblivion with the wrong App ID, fail, and Steam will automatically relaunch it with the correct App ID, but MO will not hook it then, causing the issue with no mods loaded. Disc users launch OBSE loader. That's its purpose. The big limitation of MO for Oblivion is not being able to manage OBSE plugins. Perhaps this will be fixed with the hook update that is rumored.
  22. From the previews, I'd say that the mod is new and different, but not necessarily better.
  23. I have disc version. This will not work. You MUST use Script Extender to as the load mechanism in Oblivion.
  24. A hint is if you click the FileTree button you get a nice explanation of hiding files in MO.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.