DoubleYou

I can imagine it now... "Experience porn like you have never before..."

It's in my Utilities Pack. I need to redo my signature.

It is not redundant to the many many users who have multimedia keyboards, only to the few who have lame keyboards. I just turned 23, so maybe I am a little childish, but since when has redundancy = must remove? This is a simple install and forget about it mod, so why remove it? There is no reason to remove besides redundancy. As to users who cannot use ENBoost, I merely believe there are people out there who don't follow the guide fully, taking it in bits and pieces, ignoring the stuff they don't understand. I know that I was one of those people, and would have been much the loser for these not being in the guide. ENBoost just seemed like something that my machine wouldn't be able to handle at the time. I don't think redundancy is a good reason for removal.

I was pretty sure that was the case too.

Why remove it? It doesn't conflict. You might as well get rid of Double Cursor Fix as well if you pull this one. It doesn't even take up a plugin slot! And what about users who might not be able to use ENBoost for whatever reason? I'm against removing it. Have we not had this discussion like 5 times before??? And once again, Alt+F4 works with ENB, but multimedia keys don't. What kind of lame keyboard do you got that doesn't have them??? Right backatcha...

When the installer is finished, it should run the Skyrim Launcher, and it should redo your INIs. If that is failing, please tell me at what point it is failing. That is, is the Skyrim Launcher failing to run, or is it failing to detect your graphics card and apply a preset? If it is the former, please ensure that Steam is running, as if Steam isn't on, the Skyrim Launcher may fail to run. If it is the later, I would like some more information from you, which I shall ask if that is the case.

Change the password in settings.

There are some ESP errors with many of his plugins, but that's about it on the problems side. I've used and enjoyed many of his mods.

Mod Source: BethINI by DoubleYou Wiki Link BethINI STEP Wiki Link BethINI (pronounced "Bethany") is an attempt to restore decency to the INI configuration files for games created by Bethesda. It currently supports Oblivion, Skyrim, Skyrim Special Edition, Fallout 3, Fallout New Vegas, and Fallout 4. It arose out of my research into the Skyrim INI files over on STEP. Why You Need This There are many advantages to using BethINI: 1. It automatically reorders your INI files into a sensible order, making them much easier to navigate for manual tweaking. 2. It automatically fixes common errors, including some that can cause CTDs. 3. It automatically detects mods you have installed and makes changes recommended by the mod authors where deemed appropriate. If your mod or a mod you know of requires such support, please contact me, as this is the easiest thing in the world to implement. 4. It's presets are superior in graphical fidelity and performance (95% of the time) to the official presets one can create via the game launcher. 5. It allows for the modification of more settings than is accessible via native game settings, and provides explanation for each setting and what it does. 6. It automatically backs up your INI files. 7. For Skyrim, it automatically configures the Creation Kit to support multiple masters and any installed DLC, if enabled. TL;DR BethINI fixes your INI files and lets you tweak your INI files to improve performance and quality. Installation: BethINI is a portable application. You can run it anywhere. Simply extract and run. Do NOT run through Mod Organizer! Recommended usage: 1. Please do not delete your INI files prior to running this! 2. Run BethINI 3. Mod Organizer users should go to the Setup tab and select the profile they wish to use via the ''INI Path'' setting. Your profiles should be autodetected. It is highly recommended to close Mod Organizer if open. 4. Click Default. This will refresh your INI files to the default state. 5. Original Skyrim ENB users should tick the ''ENB Mode'' checkbox. This does not apply to users who ONLY use the ENBoost portion of ENB. This should be autodetected, so if you are unsure, leave this alone! 6. Click your desired preset. 7. Tick the ''Recommended Tweaks'' checkbox to apply tweaks recommended for all users. 8. Click the Save and Exit button. Testimonials FAQ Q: The program will not load. The cursor spins, but the program does not load and the process is not created. A: Add BethINI.exe to your antivirus exclusion list. Q: Virus! A: False positive. See the VirusTotal report. Q: Should I delete my INI files before running this? A: No! Indeed, it is likely the game launcher shall kill your INI files if you do this! Q: Why is my savegame crashing? A: Not all INI settings can be changed mid-game (e.g., uGridsToLoad). If you used some bad INI tweaks (e.g., Ewi's INIs) on a save, they can cause your save not to work with good INIs. Either copy some of the problematic lines back into your INI, stick the old INIs back, or start a new game. Q: Does it work with ENB? A: Yes! Skyrim users can simply tick the ENB Mode checkbox (should be autodetected) to ensure that all necessary tweaks are applied. ENB users of other games may need to check to make sure that they haven't accidentally disabled any necessary settings (as I currently don't know what settings are necessary for the other games, as I haven't used them. Sorry.) Q: If I use ONLY the ENBoost part of ENB, do I need to tick the ENB Mode checkbox? A: No. Again, this should be autodetected. Q: I get an error when I start the game that says, "failed to initialize renderer." A: Your screen resolution is incorrect. Please change your resolution to one that your monitor supports. Custom resolutions can be manually typed into the Resolution box. Q: I want to go back to the way my INIs were before I used BethINI. Is that possible? A: Simply go to the setup tab and select "Before BethINI" in the "Restore Backup" dropdown.

Moved as this kind of rant does not belong in the DynDoLOD support thread. What the problem was: ILS with DynDoLOD Please post your Memory Blocks Log here in the forums in spoilers [spoiler] Contents of log [/spoiler]

I like it already. I was kinda asleep when I made that comment. Although, technically, I think Skyrim is bisexual...

How about "Female Unicorns." That oughta turn heads.

That is not a good idea. What you should do is append optimized to the end of each folder and simply copy them into mods.

Where's my salt shaker...

What is an injected record?

I didn't add them in, as I was afraid people who don't have all the DLC might use them eventually. Shouldn't be hard making them a download.

In case anyone wants less messy INI files (ones that aren't all mixed up alphabetically, etc.), I have rearranged them below. The only modification I've made is I've added bAllowMultipleMasterLoads=1 to the [General] section of SkyrimEditor.ini and any changes that automatically occur from starting it up and moving the windows to a less irritable location on my screen. BTW, are those edits supposed to be for SkyrimEditorPrefs.ini? SkyrimEditor.ini SkyrimEditorPrefs.ini

Okay, so seeing how messed up Fallout 3 INIs are, I decided to clean them up a bit. I have gone through the Fallout_default.ini, which is applied to both Fallout.ini and erroneously to FalloutPrefs.ini at Fallout Launcher startup (most annoying) and removed all the erroneous settings and all lines that are not different from the default. The result is given below: Fallout_default.ini As you can see, I've added comments throughout to tell of the changes from the default values. Most of these changes are assumed to be fixes (a large number of them are at least) and are recommended to be in everyone's Fallout.ini. What I recommend Edit your Fallout_default.ini file in the Fallout 3 directory to have only the following within: This will cause the Fallout Launcher only to apply these necessary changes to the Fallout.ini at startup. Unfortunately, this doesn't stop it from erroneously copying these to FalloutPrefs.ini initially, however, copying the default FalloutPrefs.ini below and tweaking it to My Games\Fallout3 and then applying your preset will allow you to have only the necessary lines. FalloutPrefs.ini

I haven't recreated a fixed up Fallout_Default.ini for Fallout 3 yet, although I will soon. As of now, yes, replace FalloutPrefs.ini with one here, then select your preset. The end result should not have a bunch of extra settings, which will show that you did it right.

In my research with Skyrim INI settings, I figured it would be fun to apply what I've learned to Fallout 3. From this I have created a the following, which is a comprehensive list of all valid settings for Fallout 3(any settings not listed here are invalid and not recognized by the game) along with their default values, with floating point values estimated to four decimal places. I have also added relavent comments left by Bethesda from the Fallout_default.ini file and some of my own. It is not recommended to use these as your INI Files! Well, actually, on second thought, I totally recommend everyone replace their FalloutPrefs.ini with the one given here and selecting your Fallout Launcher preset again, as the default INI generation mechanism makes a royal mess out of the FalloutPrefs.ini file. Extra tip: Fallout 3 allows you to make a Custom.ini that works just like the SkyrimCustom.ini if you care to do so. Please note that this is not the same as the Fallout_default.ini in the Fallout 3 game directory, which is copied as your default Fallout.ini file at startup. These are the default settings that are hardcoded into the game itself if the setting is not specified to be some other value. In the case of the FalloutPrefs.ini, most of the defaults are determined by the values assigned when pressing the Defaults button in the in-game settings. The rest were gathered from the saveini command with a blank INI with three exceptions. With three exceptions. Those three exceptions are the following, which are required to exist in the Fallout.ini for Fallout 3 not to CTD at startup. It is assumed that the default settings for these three settings are erroneous, and therefore the values from Fallout_default.ini were used. These three settings are: [Archive] SArchiveList=Fallout - Textures.bsa, Fallout - Meshes.bsa, Fallout - Voices.bsa, Fallout - Sound.bsa, Fallout - MenuVoices.bsa, Fallout - Misc.bsa [Fonts] SFontFile_2=Textures\Fonts\Monofonto_Large.fnt SFontFile_7=Textures\Fonts\Baked-in_Monofonto_Large.fntWithout these settings, Fallout 3 will CTD at startup. It should also be noted that four settings also had to be added to the FalloutPrefs.ini in order to satisfy the Fallout Launcher that it needed to detect game settings, or are only used by the Fallout Launcher and therefore reproduced here, as they do not affect the main Fallout 3 game in any way: [Display] sD3DDevice="AMD Radeon HD 8650G" ;This is the name of my video card, which would be the name of your video card. This is the only setting required for the Fallout Launcher not to run its detection. [Launcher] bEnableFileSelection=0 bShowAllResolutions=0 uLastAspectRatio=1 ;These three setting are only used by the Fallout Launcher, and these are the defaults. They have been changed in the FalloutPrefs.ini below to their most desirable values.Now here are the default INIs: Fallout.ini FalloutPrefs.ini

A Guest managed to use the Report button to try to say the following, which I have reproduced here. one step further: the last question is needless. I did the backdate to 1.3.8; and by the first try FNIS is now a executable by MO again. It works, no warnings. InGame-test even not controlled, but normally, what should happend? More Information after some InGame-experience will follow. It would be interesting, to update NOW, when FNIS is incl. the executable list, but I`m really do not trust myself, so I will wait a while. THANK YOU!!!! The "not-to-endores-problem" is still on, as also in 1.3.10 still was". Hope that it will be fixed in a further update. :: Hello, I just wanne give my report to your solution about the FNIS-MO-executable-problem. I did as you told, after some in-game-hours without any problems, I update MO to 1.3.10, - and everything was OK. So now, this things are working great. 2 Issues still on: the non-endorsement issue, I cannot endorse via MO; and one another problem is a non-registration in MCM-Menü, but that`s another stories. Thank you for help

You each need to have your own Mod Organizer install, or else you both will constantly be trampling on each other's settings regardless if you fix the permissions issue. Profiles are affected by other profiles if you modify/update/change a mod in any way. The only true solution is to make a copy for your brother. You can keep a common downloads folder, but you're just gonna be at each other's throats otherwise. Either that or you're gonna have to make some rules you can agree on and abide by them strictly (which with human nature is impossible). What you need is to buy more space, or get your brother his own computer. I'm serious.

Make sure that you have set up Mod Organizer correctly and using it correctly: In Workarounds, ensure that Steam AppID is 22330Also ensure that load mechanism is set to Script ExtenderEnsure that OBSE is installed to the game directory. OBSE and any related plugins must be installed manually.Ensure that the Archive Invalidation BSA is at the top of the Archives tabOblivion must be launched directly from Steam, not from Mod Organizer

How did it fair with the tweaks to remove tree and grass animations?

I do the same thing regarding saves.