Kelmych

I also use Mod Organizer 1.3.x for the two Fallout games. The BSA management capability saves a lot of work.

I don't see this problem in my game. I had some of the problems you mention before installing the recent NO FOSE version.

Are you using the Exeter Type 3 Armor Fix mod. The instructions for this mod including disabling he Exeter clothing and armor plugins leaving only the meshes and textures. The plugin from Exeter Type 3 Armor Fix mod does not include any stat changes such as the ones you mention. Perhaps the guide should have an additional note to emphasize that if the Exeter armors/clothing are used this mod should be enabled.

I'll add it to the userlist.yaml.

At the beginning of the game leaving the Vault produced problems for me until I slowed down a little to let the game engine "catch up". Playing with MMM active I avoided downtown DC and avoided the Metro as much as possible near the beginning of the game mostly because the Super Mutants were too tough, but also to avoid overloading the engine and reducing the frame rate to low value as Greg mentions. I avoided fast travel almost entirely to avoid breaking the game scripts which aren't very robust. When I got above level 20 I started having more of these problems, but I avoided the places that caused the most problems and was able to proceed. I didn't see red triangles but I did see low frame rate and game stuttering when there were problems. Interestingly I didn't see high CPU or GPU usage or even RAM usage when this was happening. Of course, the game was designed for Windows XP vs. Windows 10...

I looked at the LOOT rules for CPD and I notice, as you mention, that rule is no longer present. I don't use DC Interiors Room with a View myself since the games I saved and use to test the guide have already completed the "Those" quest. I'm not sure why the LOOT rule was removed. Let me know if it needs to be added back into the LOOT rules when the DCRWAV-FWE patch is used.

I'm using the GOG version of Fallout 3. My base Fallout 3 folder is around 10 Gb. I have a lot of mods installed, and my FO3 Mod Organizer\mods folder is around 40 Gb. I have more files installed than most users would have since I run tests with mods before adding them to the guide and I have some mods installed that are not in the guide as well as some backups of vanilla files in case I need them. These folders are both on an SSD. I have the download folder for FO3 Mo Organizer on a different volume (a disk partition).

Fixing problems with missing master files is discussed in a post I entered today in General Feedback.

When mods are combined to eliminate the need for one or more plugins it is possible that another mod may still expect the original master. This can be fixed with xEdit or Wrye Flash; the result is that the need for the missing master is eliminated. The procedure is described in this guide page for Skyrim starting with the subsection titled "Changing Master File Names in Plugins"; use FO3Edit instead of TES5Edit and use Wrye Flash instead of Wrye Bash.

I'll add it soon.

Thanks. This will be added to the guide (or you can add it if you want)

Multiple users have reported having this problem. I have not had it myself and many other users haven't, and no users have reported understanding the cause of the problem. It was discussed recently in the thread starting here. My load order is posted in this thread. Getting the load order correct can be difficult if a lot of plugins are used that have conflicts. There is no base universal load order that works for all cases, especially with all the weapon, armor and body mod choices possible for Fallout 3. The guide tries to avoid choosing a single set of these and instead allowing user choices since many users of this forum seem to want this. You can see the choices I made in the load order list. Your post is in the correct place; the previous thread isn't. To post a link to a thread or url highlight the text and click the icon that looks like a cloud with a green ring, then enter the url. The url for a post can be obtained by right clicking the post number in the upper right of each post and selecting Copy Link Address.

BethINI changed to a portable application since that part of the guide was written; the guide needs to be updated for that change. You should follow the steps on the Fallout 3 BethINI page. I haven't run BethINI lately on Fallout 3 but I expect it still runs the Launcher. The warning needs to be updated or perhaps eliminated as part of this change. The warning relates to the profile used in item 3 on Recommended Usage on the BethINI Nexus page (namely that the INI files for that profile will be changed, so I typically backup the selected profile before running BethINI in case I want to compare what was originally there to what is present after BethINI runs). Since BethINI backs up the INI files the warning is probably no longer needed. If I run BethINI on a profile that is used for a game that is underway I sometimes run BethINI on a simple proflle (vs. one with some changes for mods), at least initially. "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."

I posted it in this thread. When using a bashed patch setting the bash tags is important and sometimes you need to look at the bashed patch to check what it is doing, and to then change tags (or create a small patch that loads after the bashed patch). There are many choices for which weapons can be used in the game, and as mentioned in the guide most weapon mod authors unfortunately chose to overwrite the vanilla weapons rather than creating standalone weapons. Most weapon mods that add weapons can't be made compatible with at least some of the other weapons mods.

Several users have reported having this problem. I have never seen it and I don't have any good ideas of what might be causing it. I'm running the current version of Windows 10 Pro, and previously I ran other versions of Windows but never saw this problem. I posted my load order in the forum a little while ago; perhaps you you find some useful ideas on this problem by looking at it.

If you are familiar with FO3Edit you can look at some NPC types that are affected and see what models (meshes) are selected by the last plugin that affects the NPC type. I've not seen this particular problem so I'm not quite sure what might cause it.

The guide tries to indicate which mods need cleaned ITMs. Whenever we know that they should not be cleaned it is indicated in the guide. Mod developers and users have generated a bunch of compatibility patches for FO3, but most of these include one or more of the popular mods (e.g., WMK, RH_Ironsights, FWE, EVE, MMM). When these mods aren't used the compatibility patches may need to be done manually. Several such patches have been created specifically for mods in the guide, but this is only done when there aren't already available related patches on Nexus. The Patch section of the guide covers several possible sets of mods and the compatibility patches to use, but there are too many mods to provide a complete list of such patches for a large portion of the possible combinations.

If you use the userlist.yaml referenced in the guide for LOOT it helps in getting the correct load order, and in noting some of the bash tags needed by mods. The Project Beauty problems are usually taken care of by the bashed patch if the bashed tags are setup correctly. If mods are used that aren't in the guide that change NPC face characteristics then you will might have to either build a patch or determine what bash tags should be added. Any weapons that want to use Ironsights need to have Ironsights compatible meshes for the weapon, and need to have the correct value for the !st Person IS flag. The Millenia Assaultrifle Replacers RH WMK Patch should have taken care of this flag unless some other later loading patch undid it. The Wasteland Patch Collection patches provide some help with getting the correct models and flags for various weapons, but they only work if you happen to use all the plugins for each patch used. Getting the correct load order for weapon mods and getting the bashed patch and other patches to provide the right values, particularly for the models and flags, is especially tricky with Fallout 3, as mentioned in the guide. The guide tries to handle this for several possible sets of weapon mods, but when different weapon selections are used and the patches and/or core mods mentioned in the guide aren't used it will take a little bit of effort with FO3Edit to avoid missing weapon textures and to get Ironsights and/or WMK to work properly.

When I did the ranger mission I didn’ Have any significant problems in the game itself, by the way.

Mod Organizer should always start an installation with a choice of manual installation; I don't know why it didn't in this case. The line you mention was taken from the FNV guide; I'm not sure exactly which file it references. It looks like DarN has once again lost control of the site used by the guide for this mod. Did you find an alternate site for the 7zip version of the mod or did you already have it? If you have only the fomod version make sure to change the extension to 7z before installing (as mentioned in the guide).

A large number of your plugins are not ones included in the guide, so many of the forum participants won't have much information on possible problems and solutions. The standard approach for resolving issues like this is to use Mod Organizer to create profiles with portions of the mods, starting with profiles that have only a few mods. Unfortunately if your issue is that everything works fairly well until you increase the number of plugins then it's difficult to debug the problem. For these problems it's best to first remove mods that make large scale changes like FO3 Optimized and then start by using only profiles that have mods that make small changes.

The values that are hidden are intentionally hidden so users won't see them. They are left in the guide in case there are changes that would allow or require using these settings. The changes for DarnUI fonts are not needed if UIO is used; it takes care of this. The Rendered Terminal settings changes cause problems with some mods; you can search in the CPD thread posts and find the details of these problems.

Anyone can edit the guide; obviously some care is needed. Please don't remove or add mods directly to the guide; post information in the forum if you have recommendations to add or remove a mod including your experience with the mod if it's relevant. There is also a guide section that lists interesting mods that users might want to try; feel free to add to this section including some brief comments about the mod. If you want to change versions of a mod in the guide make sure you test the new version to make sure it works, and add a comment in the changelog about the version change. Currently the versions of LOOT and Wrye Flash are old, by the way. I'm currently testing some mods for addition to the guide.