Brainfever

Hi, been inactive since a long time ago. Wondered where this amazing guide is still valid, updated etc. Actually, I'm trying to figure out whether to go for it or wait for the new TTW version and go for a modded TTW Fallout 3 experience.

Just a crucial notice. If still maintaining this guide you should add a note under the Fallout 4 HD Reworked Project Revised to disable the included .esp in the proposed file for download after installation. This esp causes humongous fps drops in Boston areas (no matter your gear GTX 1080 TI or whatever) like 30-40 fps and it's also mentioned through the comments section of that particular mod's Nexus page.

Its de-activated by default in the FWE sneak settings.

As I've mentioned already in other similar topics about stuttering, ENBoost with wrong settings can be a source of heavy stuttering. I am an AMD gpu user and although I never had any problem with ENBoost in New Vegas, FO3 had always bugged me. Anyway, it's good that you managed to solve your problem but disabling ENBoost in cases of heavy stuttering is a good start at least for those with AMD gpu's. By the way, this mod you posted is a compilation of ini tweaks which I really doubt how could or could not help with stuttering issues. Generally, I avoid messing with ini files too much since you can easily screw your game. Except the multicore added tweak and the ones about decals, you can ignore almost all of the rest. The suggestions on the first part of that mod's description though are really nice. GEM also rocks I use it as well for a really really sharp visual effect!

Verify integrity of game files in Steam or do a complete re-install of the game if not using a steam version. Run the FalloutLauncher.exe choose your video settings (Antialiasing and Anisotropic Filtering ---> Off, HDR ---> ticked, Water Displacement ---> unticked if planning to use ENB), launch the game choose your in-game settings (white fonts for optimal performance of Better High Detail Map mod, untick all autosave options), exit and then go in your Documents and set your newly created fallout.ini and falloutprefs.ini to read-only. Probably you should do the same for the Fallout_Default.ini (if it's not already by itself) in your Data folder. After all these, start MO create a profile, then go into your installation folder/Mod Organizer/profiles/your profile/ and untick the fallout.ini and falloutprefs.ini from being read-only so you can tweak and change them for that specific profile you created. That's how I keep my vanilla ini's intact and backed up. You can do all the font changes, Quad core fix tweaks and generally all the tweaks suggested by the guide in that MO profile's specific ini's. Always keep a totally vanilla FO3 profile in MO with just the official DLC's (maybe also the Updated Unofficial FO3 Patch) just for the sake of it, it's never a bad idea. It's also a good practice to create a new profile every time you finish a section of the guide and after you've checked that the previous one is working correct in all aspects. That way, when you screw something and come to a dead end you can always delete that profile, copy the previous one and continue from a point you know it is working fine. A general suggestion I remember seeing from some old Fallout Remastered topics would be to start a completely vanilla gamethrough, do all the generic stuff until you exit the Vault 101. Make a hard save there and start modding/testing your mods from that save on. It doesn't matter if it makes sense or not, this game is the most crash prone and bugged game I've ever seen so even pointless things matter. After you do all this and finish the UI section I might be able to help you personally with any problem, since I've followed this process like more than 30 times the last 1.5 year so I remember any issue that I came across. Believe me I have completed this guide multiple times just to start the game and see it crashing, not loading, not behaving as expected, etc. I've been where you are now so many times it's not even funny mentioning it anymore. Modding is a continuous trial & error process and every time you start from the beginning at least you feel stronger and far more experienced than the last one. When you finish all this, we can start talking about load order stuff since me personally I disagree with the use of LOOT or BOSS, since both are not perfect and have major flaws (for LOOT the fact that it places weather plugins like in the middle of your load order is just something to begin with). PS. I've never had any profile getting corrupted in MO. First time I read about that. Can you specify what do you mean by "corrupted"? A profile working fine and the next day not working?

User Interface problems in almost all cases are not a load order issue. It's just what xml file loads finally in your game. And of course how organized that specific xml is and what it contains. Which is what UIO is helping you with. The only visual conflict I can think of is with let's say 2 mods that both include an interfaceshared0.dds file in which case you'll be missing the customized icons, compass arrows, or whatever from the overwritten mod. Bare in mind, that the other UI problem I saw somewhere recently with the missing menu/mouse pointer when starting the game is not always a fonts/UI issue. I use a weapon replacer mod not included in the guide called Book Of Earache(BOE) which when loaded together with the any of the Big Town Overhaul's plugins it would make my menu/mouse disappear. Both mods do not conflict anywhere, either files or records in FO3Edit, but I would get this problem no matter what. FO3's engine is bugged as hell and nothing can be done about it. My advice, copy your current profile into a new testing profil and untick all the mods till your UI section. Start testing your hud in-game from there and make sure that everything works fine. Then add every section of the guide one by one (ok obviously you can skip this with the textures mods or mods that generally include only textures, meshes or sounds) testing your hud in-game until you find what bugs your game. Although I doubt it would be any mod later in the guide.

I really don't understand how all these problems occur to you people. You just follow the guide and everything works just fine. Ok, maybe I haven't installed everything since some mods are just a matter of preference, but especially after UIO the User Interface section is more than a piece of cake to accomplish. Imagine that in the past we had to deal with specific mods being able to install only through FOMM, then create mods from the Overwrite Folder in MO, sort them, look out for overwritten xml's, even manually manipulating xml's to include features from one hud mod with the other, etc. What I did was exactly following the guide's instructions for the mods I have included in my setup. I haven't installed the Advanced Recon mods for my own preference reasons and to save up some plugin slots, the Flashlight mod because I never actually used it or find it any useful in general, the Powered Power Armor mod again for preference/plugin space reasons and the same applies for the JIP mods. The Supplemental UI section is again a matter of taste for each individual but its not so critical overall. Mods like the descriptive icons or the no more dots mods are again a personal choice to not include them, but other than that if you install everything the way and order the guide instructs you there is 0 problems, at least for me. But even with all of them installed, like I did in a previous setup everything worked flawlessly as far as I remember. I would remember a missing compass and HP/AP bars for sure! I didn't tweak any of the occurring overwrites I just let them be in the order I installed the conflicting mods. After all, UIO is taking care of everything. Sorry if I sound aggresive, but there are so many topics popping about UI issues while in the meanwhile I can't seem to reproduce anything no matter how faulty I try to install the mods in the guide in order to let's say find the issue of yours and others problems. It's just non sense :O_o:

Started as an Outcast only once all these years I'm playing with FWE and I clearly remember I got a CTD the moment I start heading towards megaton. I cannot confirm whether its a reproducible CTD or not since I never actually paid much attention to that specific session/character but if indeed there is something that is causing a CTD for a certain reason, then it would be more than a good idea to track, find and fix it since it could probably resolve other possible CTDs with FWE in general. Your load order looks fine to me by the way.

To my understanding a Bashed Patch is also very useful for its function of merging whole mods in it thus leaving those mods' plugins redundant and saving up important space in your load order.

Maybe manually override in a custom patch in FNVEdit the LNAM - Hair length, HCLR - Hair color and FaceGen Data from FCO plugin in every entry it conflicts with YUP - NPC Fixes (Base Game + All DLC).esp? Probably gonna take a while if YUP affects a lot of NPCs that FCO changes. Sorry, I don't have New Vegas currently installed on my pc so I don't remember precisely what I did with my NPCs. But I remember the last time I accomplished a F&L setup, I did exactly what you want to do. I excluded NVR3 from my modlist and went for a FCO exclusive setup. Tweaking the NPC's records to my liking was a very time consuming process though. In many cases, I would have to choose what inventory items I wanted for specific NPCs besides the face characteristics.

https://www.youtube.com/watch?v=GE2BkLqMef4 It's official guys :D

Probably I'm off-topic (or maybe not) but in case someone missed it: https://www.youtube.com/watch?v=GE2BkLqMef4 FALLOUT 4 is now official :D PS. Just didn't know where else to post this..

Oh my F god! The second picture is just so... divine!

MGs Neat Clutter Retextures is a very decent retexture mod. Personally, I use it both in FO3 and FNV and I can tell there's nothing in there that I don't like. And regarding New Vegas there's an Ojo Friendly version of it so it doesn't conflict with Ojo Bueno. Actually, I just now realize it wasn't already included in the guide which suprises me.

And FOSE which is mandatory. For example, me when I try to run fose_loader.exe under compatibility mode I just get a nice CTD before even making it to the main menu. Not to mention, that changing compatibility mode on installers like the vcredist and dotnetFX exes makes no sense..