DoubleYou Posted August 21, 2015 Posted August 21, 2015 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.
TechAngel85 Posted August 21, 2015 Posted August 21, 2015 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.
Greg Posted August 21, 2015 Posted August 21, 2015 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.
DoubleYou Posted August 22, 2015 Posted August 22, 2015 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=1bBackgroundMouse 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.
Greg Posted August 22, 2015 Posted August 22, 2015 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).
DoubleYou Posted August 22, 2015 Posted August 22, 2015 On 8/22/2015 at 3:00 AM, Greg said: 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
DoubleYou Posted August 22, 2015 Posted August 22, 2015 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
Greg Posted August 22, 2015 Posted August 22, 2015 On 8/22/2015 at 7:18 AM, DoubleYou said: 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=1This keeps Skyrim active in the background, but it doesn't solve the issue with the double cursor appearing on the second monitor.
DoubleYou Posted August 22, 2015 Posted August 22, 2015 Then I guess that tweak probably won't work on multi-monitor setups. No wonder it was disabled by default.
DoubleYou Posted September 7, 2015 Posted September 7, 2015 Tweak of the day: Skyrim.ini [MapMenu] Increase map menu rotation rangefMapWorldYawRange 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
DoubleYou Posted October 5, 2015 Posted October 5, 2015 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]bBloodSplatterEnabledbBloodSplatterEnabled toggles screen blood splatter. Unfortunately, it also causes the map menu to CTD.bBloodSplatterEnabled=0
DoubleYou Posted October 13, 2015 Posted October 13, 2015 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 rangefLightLODRange 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=500(Default) fLightLODRange=20000 fLightLODRange=50000(Recommended) Skyrim.ini[Display] fLightLODRange=50000
phazer11 Posted October 15, 2015 Posted October 15, 2015 Dude... is this like your theme song or something? Either way good work.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now