SergeTroy

Supposedly there are no stupid questions, but I may be putting that to the test. I’m planning on starting a new, modded Playthrough of Fallout 3 (Game of the Year Edition, of course) via Steam soon, and I needed some initial support. As the Fallout 3 forum seemed pretty dead (retro much) I figured I’d ask my initial two questions here. Firstly, would people recommend Mod Organizer 2 or Vortex as a preferred mod manager of choice? Or some third option? I know I’m asking in the MO forum so answers may be prejudiced, but I trust in more experienced gamers to be able to give me a reasonably balanced answer. Secondly, is L.O.O.T a solid way to create a more or less final load order for all the mods I want to use, obviously with some fine tuning I’m sure. If it’s not exactly the best way, or is only part way effective, is there someplace else I can go to better refine my approach? I know about and have bookmarked the STEP Guide, Clear & Present Danger, for Fallout 3. The main reason I’m asking more questions beyond what that guide has to offer is that I noticed via the changelog that the last update was in May (?) 2019. Since then there has been the update on Steam, and the Fallout Anniversary Patcher was released. Plus, I just don’t know if Mod Organizer 2 was even a thing back then. Thanks in advance for any help that can be offered. If this needs to be moved to the Fallout 3 specific forum I understand, I’m just trying to get the smarts of the active community.

Titling this was kinda difficult. SO: I'm thinking about making my first (re)run in Fallout 3 (using the guide and other tutorials) an evil run of the most vile variety (blowing up Megaton, burning Harold, tainting the GECK with the modified FEV, etc.) BUT my previous experiences have always left me with a certain fear of doing so. There always seemed to have been more bugs for the Evil story-lines than there were for the good or neutral choices. Has anyone here had a relatively bug / glitch free run as a Truly Despicable Lone Wanderer, where they used the Tenpenny Apartment for their Player home, completed most of the game (say, 75%) and otherwise chose to be an a**h0le at large?

Huh, before I read the post, by topic title I wondered if you were using any mods or whatnot. The problem with the various NPC's having different color textures for their bodies than their heads is mostly associated with the vanilla default game. The UPDATED Unofficial Fallout 3 Patch should resolve most if not all of that, but I dunno about Fallout Redesigned specifically. My first suggestion would be to include the latest version of the UUFO3P if you haven't already; failing that - if it was me - I'd kinda go through the various steps provided in the guide and look to any number of YouTube videos courtesy of GamerPoets. Sorry I can't personally speak more to this, I'm a fan of Fallout 3, but the time I've had to mod and play it has been fairly limited. The best recommendation I can otherwise make is update your OP with your mod list or LOOT export, detail the various important bits of your machine (OS, CPU, GPU, and version of Fallout 3 (Assume GotY, but Steam GoG, or Disc?)), and wait a few days for a more knowledgeable poster. Hopefully the UUFO3P is good 'nuff.

The basic summary is that I want to know what kind of consensus there is - if any - on what NVidia Inspector settings are vital to make sure the steps outlined in Kelmych's wonderful guide pay off. I run Windows 7 64-bit Home Premium and use a GeForce GTX 1070 (single card and gpu, single monitor). I am not using an ENB (at this time) although I am thinking about it. I will be using lighting mods, though the larger environmental lighting/weather mod I am really unsure of (I've been thinking DC Moods, but dunno). Where needed, I can put up a list of all the mods I intend to use. When I look into specific video card settings on STEP for NVidia and NVidia Inspectorl, I don't feel like I have a firm grasp on recommended values beyond a few definites. By example: Ambient Occlusion compatibility: “0x00000005 (Call of Duty: World at War)†Antialiasing compatibility: “0x000010C1†These are confirmed on the Guru3D forums thanks to the 'NVidia Compatibility Bits Master Thread and IQ Guide' by GuruKnight, and a few other sources I cannot remember currently. I only use a single card and GPU (GeForce GTX 1070) so I don't worry about SLI and leave those areas at their default values; for the machine I'll be playing on, there is only one monitor, so naturally "Single display performance mode" is what makes sense there. Other things like this make sense, but there are *so* many settings that I am really not sure of. When it comes to making sure the steps in 'Clear and Present Danger' pay off (ini settings and all), I am a little lost on what to choose. I've got a profile currently set up, but I'm certainly not using it until I've done a bit more research. If anyone needs more information, please ask. I'm throwing out the current profile simply as a point of reference, below:

I, uh, couldn't find a way to edit my prior post, so with apologies, I have a question on the Fallout 3 INI Tweak Guide page ... I think there's a small formatting issue within the Fallout INI section, as [Fonts] and </pre>--> are outside of any box (forget the BBCode or whatnot in describing that formatting, apologies). Also, I'd actually copied this page to a word doc back in ... Nov. 01, 2015; comparing the current page and my copy, I see that the "Rendered Terminal" section is missing, is that intentional? (I may be using my Post code wrong, I just went with CSS and no starting line number). [RenderedTerminal] ;from ''Higher Resolution In-Game Rendered Terminal Text'' fRenderedTerminalZoom=33 ;enable higher resolution text displayed within in-game rendered terminals

On the Fallout 3 INI Tweak Guide page, the link to DoubleYou's BethINI (as uploaded by Vuud) is wrong. Currently it links to a Mod Not Found kinda page. Correct link (as listed below) goes here. https://www.nexusmods.com/fallout3/mods/21741/?tab=description&navtag=http%3A%2F%2Fwww.nexusmods.com%2Ffallout3%2Fajax%2Fmoddescription%2F%3Fid%3D21741%26preview%3D&pUp=1 Currently going through a long night for modding - skimming the guide, linking and downloading, copy'pasting, thorough reading, (rinse, wash, repeat) so I'll update if I find anything else or whatnot. Truly love the usefulness of this guide for someone that's as absentminded and otherwise technically ignorant as myself.

Dunno, I have a talent for drama when I'm exhausted, best not to let it go to waste. But seriously, thank you for the link, I hadn't known how to access that otherwise. :)

Just double checking, but is anyone else only seeing the "Revision History" of the Clear and Present Danger guide at this time? For me it starts at the top with February 3rd, 2018, and goes down to August 18th, 2014. I suspect it's a temporary thing where Kelmych is adjusting this or that, but if anybody really crossed a line with the Man, that well and truly sux. :'(

Awesome, thanks DoubleYou! Have been away from video games for nearly 4 months and I feel so utterly out of the loop and brain dead on a lot of this stuff once again. It was enough that I was practially considering redoing my whole set up purely for the updated fINIp3 and UUFO3 patch. xD Have a great one!

Just because I'm never a hundred percent on this, when it comes to updating a mod mentioned in the Guide (be it DoubleYou's fINIp3 or the UUFO3Patch) when if ever is there a need to be concerned about additional ... tweaks to ensure everything's still set correctly? For example, are there cases where when you've updated fINIp3 or UUFO3 patch that you would need to redo LOOT or the Bashed Patch, or anything like that?

Basically, I'm a little concerned that there's more to updating the "Fallout INI Project 3" Mod than there might be with others. Does it really just come down to the steps laid out by DoubleYou / Vuud, to Uninstall the prior version, and then just install the new version as standard? If so, you would: Uninstallation: Replace your Fallout.ini and FalloutPrefs.ini files with the backups you should have made according to the warnings in installation and go to step 3. If you neglected to heed my warnings, delete Fallout.ini and FalloutPrefs.ini in Documents\My Games\Fallout3 and go to step 2. Run the Fallout Launcher and select your preset. If using Mod Organizer, copy the new Fallout.ini and FalloutPrefs.ini from your Documents\My Games\Fallout3 directory to your <ModOrganizer>\profiles\<Profile-Name> directory. Eat salt and vinegar chips.Followed by -> Installation: Download the main file. Run the installer. Follow the on-screen instructions. Read any warnings carefully! Once the installer has completed, the Fallout Launcher will automatically run to generate your new INI files. Please ensure that your screen resolution in the Launcher is selected correctly! If using Mod Organizer, copy the generated Fallout.ini and FalloutPrefs.ini files to your <ModOrganizer>\profiles\<Profile-Name> directory. And then just double checking to ensure that the variables you want set per preference are set, profile specific, via MO's INI editor? Do you need to do anything else? Some possibilities that occurred to me would be: disabling all mods prior to this update, and re-enabling after but prior to the review of the MO INI Editor's tweaks; Possibly needing to redo LOOT ordering and even the Bashed Patch. I don't know for certain in this and so I'm just a little concerned and curious on the thoughts of the communities wiser heads.

Hey Nameerf, this is a somewhat known issue with Dynavision, unfortunately. If you actually watch Gopher's own "Let's Play Fallout 3" series, you'll note he runs into this in a number of places. For me the most common has been in Rivet City, particularly in areas around the stairwells, and with the Doctor of the ship. I'm not really thinking there is a precise fix to this by memory, sadly and I'm not willing to disable the mod either as it's otherwise such a wonderful option. I would say that if it's occuring far too much, than you may want to consider disabling EITHER Dynavision or the Lone Wanderer's ENB, as I believe that it's been stated by Gopher that while they are compatible (or at least, not incompatible) they kinda just do the same thing in a lot of ways so that may be increasing the problem.

The short of it: I'm looking to remove a fix that originated with the original Unofficial Fallout 3 Patch, where the modder set the Bloody Mess perk to be disabled for the duration of the Side Quest, "You Gotta Shoot 'Em in the Head." And because I'm feeling a little out of my depth, I thought I'd consult a more knowledgeable community for assistance with this. :) [spoiler=Long Winded Explanation for Why I want to Fix the Fix] I'm seeking a little help with editing out one of the fixes that's currently included with the UPDATED Unofficial Fallout 3 Patch, and originates with the original UFO3P. The modder had decided that to avoid having PC's unintentionally fail the side quest, "You Gotta Shoot 'Em in the Head," he would change some conditions / effects with the Perk Bloody Mess so that it would be disabled for the quest's duration. This would keep bloody mess from gibbing off an NPC's arms and legs as well as the head. And while there's some sense to that, there's also some arguments against. Firstly, the quest doesn't really require you to kill the target's mentioned in the quest with a head-shot specifically (Dukov at Dukov's Place, Ted Strayer at Rivet City, Dave in the Republic of Dave, and Alistair Tenpenny at Tenpenny Tower). There's an alternative way to go about things where you don't even need to kill them at all (discounting Tenpenny, but even then it's not required (I think) that he dies by a bullet in the brain). Secondly, there's the issue of how long the perk could be considered disabled. The quest giver, Mr. Crowley, is located in Underworld within the Museum of History, within the Mall. And most player's are going to be heading off to the Mall fairly early just to get Galaxy News Radio up and running. Now, the various people and locations relating to the quest are spread out all over the Capitol Waseland, pretty much cornering the whole region (Tenpenny Tower, the Republic of Dave, Rivet City, and Fort Constantine). So excluding those player's that decide to start this quest only after they've already found every location, and then just fast travel between each, most player's will find that this quest extends throughout a great part of their time in the Capitol Wasteland, and attaches neatly to the Main Quests, and other side quests as they rove here, there, and everywhere. A duration during which Bloody Mess (a 6th level perk) is completely disabled save for the 5% damage increase (which isn't why most get the perk, I'd guess). Now when I looked into FO3Edit to get an idea of what might be needed for "fixing the fix," it looks like the patch purely added a condition to the Fallout3.esm ActorEffect for PerkBloodyMess. To be explicit, it looks something like: [spoiler=Fallout3.esm \ Actor Effect \ 00079AE3 ] Conditions CTDA – Condition Type: Not equal to / Or Comparison Value – Float: 10.000000 Function: GetStage Quest: MS14 "You Gotta Shoot 'Em in the Head" [QST: 00014EA1] Run On: Subject Note: the actual changelog for the UFO3P mentions this specifically, "Fixed the Bloody Mess perk making it harder to complete the quest "You Gotta Shoot 'Em in the Head" since Bloody Mess can blow off more then the head if you get a head shot causing the script to mess up, the "Bloody Mess" part (not the damage) of the perk will be disabled when the quest starts and enabled again once the quest finishes (Altered Actor Effect: PerkBloodyMess)." Lacking that one change, I'm imagining that the fix would be removed. When I looked at references, there's only one and that for "Record: DLC03LibertyPrime "Liberty Prime" [CREA:04001FCC], File: [04] BrokenSteel.esm" which seems more likely to be related to the standard unedited ActorEffect of Bloody Mess rather than what the patch changed. I've taken a quick look at the quest entry for "You Gotta Shoot 'Em in the Head" and there are a number of references to other changes made by both the add-ons as well as the UUFO3P, none also reference to the perk bloody mess. I then looked at the NPC's directly involved with the quest, and again, no link to bloody mess. Still, If anyone that has a better grasp of the relation of things within FO3Edit (meaning everyone) has a reason to believe I'm not being cautious enough or careful enough in my trimming, I'd really appreciate it. I'm very much looking forward to starting a new game of FO3 here, and while HairyLegs over on the Nexus is set to include this with the patches next iteration ... I'm the impatient sort. :D Thanks very much to anyone that can assist. :)

GSDFan, Nebulous112, thank you both. The solution was actually probably the combination of both, I'm giving GSDFan the solution simply because that was an option I had never thought to try before (the deletion of the webcache folder). What the final resolution was - insofar as goes the lynch-pin of it - truly slapped me in the face: It wasn't that I had to just login / access the Nexus Network through the Mod Organizer 'Globe' icon, I had to actually download a mod, and (possibly unnecessary) install it through that connection. When I saw in the window, 'retrieving credentials,' and 'user is premium,' as well as the logged in user name on the (lost-the-right-word) Window Header, I could only stop myself from smashing my face into my keyboard because I love this keyboard way too much. Thank you both, I need to go watch something really stupid to make myself feel smart again.

Hey GSDFan! Did what you said and it did provide some benefit; the "Cookies seem to be invalid" message in the log window has disappeared, it otherwise implies everything seems to be fine (e.g. "interface Local Area Connection seems to be up ('gives the address')"), but I'm still showing as "(not logged in)" on the overhead bar, and there's nothing about my Nexus Credentials (I'm 'FearlessFelix' on the Nexus, and I could have sworn it usually said something about either how that would be confirmed, or something on the premium part). Honestly, it's just REALLY weird. I think I'm what I'm going to do is this: I'm going to delete the Password & Username currently listed in MO's Nexus Settings, uncheck the "Automatically Log-in to Nexus" box, and repeat the process of A. backing up the current contents and then B. deleting the MO Web Cache folder contents. Next, I'm going to once again change my nexus password. Last time I had to make use of the forgot password option because the change I thought I put in place didn't take and I forgot the original. I have no idea if that screwed things up. Once the password is updated and I've got it down, I'm going to clean sweep everything in my browser, just like I normally do and have done in the past. Cause I'm paranoid and weird. Run what I consider to be a full clean sweep on the computer (utilities for keeping system smooth and clean, anti-malware and anti-virus stuff), and then reboot. When I restart, launch Steam first. I always wonder if that matters; I understand it SHOULDN'T but I have no real tech knowledge so magical thinking for the win/loss. Load up NMM and get the pw in the manager updated. Launch my browser and make sure I'm logged into the Nexus. Confirm the Web Cache folder is still empty; launch MO and pray there's some weird bug that somehow sorted itself out in this process. Again, it's not like there's really a problem per se, it's just so darned weird to have lot that "logged in" status and not see account credentials confirmed or whatever in the MO main window. And yes, agree my detailed nuttiness could be used against me in a court of public opinion.