Jump to content


Photo

Guide:Skyrim Configuration Settings

guide ini skyrim.ini skyrimprefs.ini

  • Please log in to reply
46 replies to this topic

#16 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 20 August 2015 - 08:59 PM

Skyrim doesn't have a Test1 setting, so I'm not sure how you're reading that, unless this is an application of your own making. What I do know: comments don't work next to string settings. So, I just blanket recommend all comments be placed on their own line. There can't be any issue with that, and it is much cleaner.



#17 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 11,282 posts

Posted 20 August 2015 - 09:37 PM

I'm on DY's side for this one. Regardless of whether or not it only affects string settings, having a standard is good and DY's in this case is the correct way.



#18 Greg

Greg

    Dragonborn

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPip
  • 1,341 posts

Posted 20 August 2015 - 10:43 PM

This is an application of my making that just uses the same API functions that Skyrim uses. I agree with both of you that we do need to establish a standard for comments, and that comments should not be at the end of a valid setting.

 

My only intent was to find out the various effects semicolons and other special characters have on settings to give us some concrete information, meaning I think we can safely say that the GetPrivateProfile* and GetProfile* functions do ignore lines that start with a semicolon. I know you've already proven this on your own, I just wanted to verify that something like ;bMakeSkyrimCrash=true is a valid comment that can't be read even if explicitly attempting to read ";bMakeSkyrimCrash" as a key.



#19 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 21 August 2015 - 10:25 AM

Gotcha.

#20 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 21 August 2015 - 08:35 PM

I recommend that everyone add the following tweak. You'll thank me the next time you open your ENB in-game settings. Or if you don't have any kind of double cursor fix (either ENB's solution or the Double Cursor Fix mod).
 
Skyrim.ini

[Controls]
bBackgroundMouse=1

bBackgroundMouse toggles the ability of the mouse to move independently inside Skyrim (default where bBackgroundMouse is disabled) or dependent upon where the cursor actually is in the system (bBackgroundMouse is enabled). It is recommended to be enabled to prevent awkward mouse behavior during some actions.



#21 Greg

Greg

    Dragonborn

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPip
  • 1,341 posts

Posted 21 August 2015 - 10:00 PM

When I set this option, I get a double cursor that's visible and active on the second monitor. This means when the mouse scrolls into the second monitor (such as when turning around) and I click, the focus changes and Skyrim vanishes (meaning Skyrim no longer has the focus and is changed to a background process).



#22 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 22 August 2015 - 02:18 AM

When I set this option, I get a double cursor that's visible and active on the second monitor. This means when the mouse scrolls into the second monitor (such as when turning around) and I click, the focus changes and Skyrim vanishes (meaning Skyrim no longer has the focus and is changed to a background process).

Hmmm... that's an interesting setup. Adding the following to Skyrim.ini will cause Skyrim to always remain active, but that might not entirely fix that incompatibility:

[General]
bAlwaysActive=1


#23 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 22 August 2015 - 01:07 PM

  • Added "INI syntax" and rules and restructured a bit, moving the prefix explanation inside INI syntax under settings. The prefixes are vital to understanding INI settings!
  • Tweaked "Recommended changes" layout to be easier to add new tweaks
  • Added several vital tweaks to "Recommended changes"
  • Removed untested tweaks from the "Recommended changes" section and placed them inside new "Other useful INI tweaks" section
  • Added "Other useful INI tweaks" section
  • Added lots of "new" and useful INI tweaks
  • Added "Known harmful INI tweaks" section
  • Added lots of harmful INI tweaks with bad values in red


#24 Greg

Greg

    Dragonborn

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPip
  • 1,341 posts

Posted 22 August 2015 - 01:11 PM

 

Hmmm... that's an interesting setup. Adding the following to Skyrim.ini will cause Skyrim to always remain active, but that might not entirely fix that incompatibility:

[General]
bAlwaysActive=1

This keeps Skyrim active in the background, but it doesn't solve the issue with the double cursor appearing on the second monitor.



#25 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 22 August 2015 - 01:20 PM

Then I guess that tweak probably won't work on multi-monitor setups. No wonder it was disabled by default.



#26 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 07 September 2015 - 08:14 AM

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


#27 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 07 September 2015 - 09:03 PM

  • Added several map menu tweaks


#28 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 05 October 2015 - 07:34 AM

Be advised that the following tweak to remove blood splatter, which was recently added to the "Other useful INI tweaks" section, has been moved to the "Known harmful INI tweaks" section due to the fact that it causes the map menu to CTD. Killed my tweaking fun, that's for sure.

 

[ScreenSplatter]

bBloodSplatterEnabled
bBloodSplatterEnabled toggles screen blood splatter. Unfortunately, it also causes the map menu to CTD.

bBloodSplatterEnabled=0



#29 DoubleYou

DoubleYou

    Wiki Stepper

  • STEP Staff
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,463 posts

Posted 13 October 2015 - 02:24 AM

This tweak has a nice effect on distant light. It is similar to the grass fade range tweak, so it might eliminate light pop-in.
 
Adjust light fade range
fLightLODRange sets how far away light will fade from the start fade distance (fLightLODStartFade, which is Light Fade in the in-game Settings > Display menu). It is recommended to set it to 50000.


FLightLODRange%3D500.jpg

fLightLODRange=500
(Default)


FLightLODRange%3D20000.jpg

fLightLODRange=20000


FLightLODRange%3D50000.jpg

fLightLODRange=50000
(Recommended)

 
Skyrim.ini
[Display]
fLightLODRange=50000


#30 phazer11

phazer11

    Chatroom Supervisor

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,246 posts

Posted 14 October 2015 - 09:17 PM

Dude... is this like your theme song or something?

Either way good work.





Also tagged with one or more of these keywords: guide, ini, skyrim.ini, skyrimprefs.ini

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users