Kelmych

I'm sorry you had these problems. I added the comment about upgrading to the most recent DirectX to the guide. I wouldn't have thought that it would matter with an ENB (which uses a different d3d9.dll) but perhaps there are other updated files that the newer d3d9.dll expects.

As Brainfever mentions, it's a always good idea to load the vanilla enb files and then edit them when you are making changes in enb parameters. Since there is a new version of the Fallout enb series (0.263) I need to review the guide to make sure the parameter recommendations for ENBoost are still correct. Also make sure that Fallout.ini and FalloutPrefs.ini haven't changed. I've had problems when these are inadvertently changed while I was making other changes. The Troubleshooting section at the bottom of the guide lists all the problems with launching that I've seen discussed, and when I hear of new problems and solutions I add them. In the game I started to test the guide, as I get further into the game I do have occasional problems with game CTDs when loading old save games and opening doors. I've found that removing d3d9.dll sometimes reduces this problem; I can add it back later.

The bashed patch shouldn't include any Skyproc created patches; they should load after the bashed patch.

I couldn't find the mod installation order recommendations when I looked recently on the STEP guide. I'd like to reference it in the DDSopt guide, but I no longer see it in the DLC wiki pages (of course, I might have missed it).

The description of optimizing the vanilla textures in Fallout 3 has been added to the DDSopt guide in the Fallout QUICK-START guide tab. The batch files provided in the guide that simplify this are the same ones used when optimizing Fallout New Vegas textures. The use of optimized vanilla textures has been added to the Clear and Present Danger guide for Fallout 3.

Thanks. It is now removed.

I looked at the current version of the guide (it changed today but the Fallout NV pictures haven't changed) and I don't see any problems with them. The text around them does need to be moved a little. What problem is there with the pictures so they can be fixed if needed?

A new version of the batch files for the DDSopt guide is now available. The only change was the pre-optimization sorting batch file. It was changed based on some discussions in this thread over the past few months. The main changes are: Small facial textures that might be collapsed from 256x256 to 1x1 by DDSopt are no longer optimized. They will be available in the optimized texture archive with the optimized textures, and the Creation Kit and other tools that need full resolution versions of these facial textures will have them.The pre-sorting provides 5 folders so that Exterior textures and Exterior normal maps have their own folder, providing more flexibility in selectively optimizing different categories of textures. All of the other similar batch files (those for Skyrim mods, vanilla Fallout textures, and Fallout mods) already do this.The process for optimizing Fallout 3 vanilla textures was added to guide; it is in the same section as optimizing Fallout NV textures. It uses the same batch files as are used for Fallout NV. Some simplifications in the process description for vanilla Skyrim optimization were made in the "DDSopt Optimization" tab.

I'm running an AMD R9 290X (4 GB). I am not using an ENB at the moment. Outdoors in Skyrim I sometimes, but not always, see VRAM usage between 3.8 and 3.9Gb. I'm using 2k exterior color maps and 1K exterior normal maps. The FPS is almost always above 30; interestingly, in the unusual cases when it isn't the CPU and GPU usages aren't especially high.The GPU usage never gets really high, and I don't hear any noise from the graphics card. The only time I hear the computer fans a bit is when I'm running DDSopt to optimize textures. It uses all the real and virtual cores on my i7-4770 and close to 100% of the CPU, based on the CPU monitor tool I use.

I meant to say that the STD and DLC optimized textures go after the corresponding cleaned ESMs and before the corresponding unofficial patch. The optimized HRDLC go after the original HRDLC BSAs which are deactivated as are the esp plugins for these.

I'm fairly sure the load order details for the optimized textures used to be in some detailed instructions for the STEP guide. Perhaps this changed when moving to LOOT vs. BOSS; the installation pane itself isn't affected by LOOT but in some cases the exact installation order is flexible. We'll add this to the update of the DDSopt guide that will be provided very shortly (probably tomorrow). The answer is that each of the optimized textures typically go right after the associated cleaned ESM files for optimized STD (optimized Skyrim - textures) and the 3 DLC. The optimized HRDLC go after the corresponding vanilla BSAs so they overwrite them, and the UHRP should be after all the optimized vanilla textures. In the picture you show some of the files seem out of order. Unofficial Dragonborn patch would typically be right after the optimized Dragonborn textures.

I don't think you understand some of the points I was trying to make. The issue is, as you mentioned, getting MO to "hook" the virtual file system, FOSE and Fallout 3 all together. The Steam examples were intended to look at options in how MO can simultaneously hook multiple things together. Did you try using the approach that the second post in the Steam overlay discussion suggested? It had less to do with Steam itself and more to do with how MO can hook FOSE and Fallout3 together. None of us has seen the exact set of circumstances that you have, and we are just trying to come up with some possible solutions.

I haven't tried using MO with the CD version of Fallout 3 GOTY (I don't have this) and I don't know what problems this causes. I have the CD version of Fallout 3 and 2 of the DLC, but I got the Steam Fallout 3 GOTY version on a Steam sale rather than buying the CD versions of the rest of the DLC. I don't know how MO works with the copy protection for the non-Steam version of Fallout 3 GOTY.

I tried the method GDSFan mentions and I can get the game running with FOSE and Steam overlays, but none of the mods or Fallout.ini/FalloutPrefs.ini from MO seem to be present when I tried this. I haven't tried the 2nd method yet, but I expect that any other FOSE mods like Enhanced Camera will also need to installed directly into Data.

In my comment I was also thinking of the use of DDSopt to improve quality with better mipmaps and to make some of the small format changes that DDSopt does for compressed textures that could be in a more compressed format (e.g., DXT3 vs. DXT5). In addition, body replacers often use large uncompressed textures for a few of the textures (e.g., "upperbodyfemale.dds" in the Type 3 body in the guide). For users with 1GB of VRAM or less it might be good to change this to R5G6B5 format or to reduce the size to 1Kx1K uncompressed (R8G8B8).

I think the problem you are having is related to the one discussed in this thread. Steam doesn't work well with any mod manager in Fallout 3. I expect the version of Fallout 3 GOTY you have requires the same kind of "hooking" between Steam and a mod manager (e.g., Mod Organizer) to start the game that is needed to get the Steam Overlays working. The posts even mention that some users have the problem launching the game and not just getting the overlays. As you can see on the thread, there are no particularly great solutions. However, you might want to try the solutions/hacks that were mentioned in the referenced thread.

The screenshot being referenced is the "Working Folder "Vanilla Extracted" Screenshot" to the left and up. The next time the guide is edited we''ll make this clearer. The guide still needs the screenshots and text for Fallout 3. Thanks for catching this. Currently the instructions are only in the Fear and Loathing in New Vegas guide. The reference to the Skyrim guide was removed. When EssArrBee has identified more mods that need optimization the section on Fallout NV mod optimization will be expanded.

I'm not sure what is happening. Right click the Fallout 3 GOTY folder and make sure that all users have full access. Make sure that Mod Organizer itself isn't in a User Access Controlled directory. You can try changing the Mod Organizer executable properties to include Administrative Access, but this shouldn't generally be needed. Have you added FOMM-fork to the list of executables in MO? If so then try running FOMM-fork from MO and see if it works.

When you run FOSE with MO you said that you get a DOS box then it crashes. What happens when you run the Fallout Launcher from MO? Do you see the standard small startup box with several options? What happens when you run FO3Edit from MO; does it run successfully?

Are these fose logs from when you tried to run FOSE from inside MO or outside MO? The logs of interest would be any that were written from your unsuccessful attempts to run FOSE from inside MO. The fose logs look fine; if they were written during your unsuccessful attempts to start Fallout 3 using the FOSE loader then they say that FOSE itself is successfully started and the problem isn't with FOSE but something that happens after FOSE. You didn't say whether you tried including the changes to Fallout.ini that I mentioned. I'm assuming you are using only the vanilla Fallout 3 files and no additional mods.

There is a troubleshooting section at the bottom of the guide that might help. It sounds like you already ran fallout so the registry entries and Fallout.ini and FalloutPrefs.ini were created in "user name"DocumentsMy GamesFallout3. Did you try adding the two Fallout.ini entries in the guide under "Fallout 3 Dual-Core and Multi-Core Fix" using the ini editor in MO? On my system I get a CTD if these entries are not present. Did the loading proceed far enough to provide entries in fose_loader.log or fose.log in the GOTY directory? If so it would help if you provide the contents in a post. Are the five lines you posted the only entries in "mo_interface.log"; the entries in my log are not quite the same as the ones you posted? Are you using MO 1.2.11 ? Did you try reinstalling MO in case the installation had a problem? Here is what I have in the bottom of my "mo_interface.log" when I startup: 16:00:46 [D] configured profile: Pure Vanilla16:00:46 [D] activate profile "Pure Vanilla"16:00:46 [D] displaying main window16:00:46 [D] using load order from file16:00:48 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillamodlist.txt saved16:01:14 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillainitweaks.ini saved16:01:14 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillaplugins.txt saved16:01:14 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillaloadorder.txt saved16:01:14 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillaarchives.txt saved16:01:14 [D] save D:/Games/FO3 Mod Organizer/webcache/cookies.dat16:01:14 [D] save D:/Games/FO3 Mod Organizer/webcache/nexus_cookies.dat

The FOSE src folder isn't needed, it just has information for those who want to understand it more deeply such as those building scripts to use with it. If you read the sticky post at the top on the Nexus page for FO3Edit it suggests not using 3.0.31 to clean FO3 mods; use 3.0.32 instead.

MO works fine with FOSE and other FO3 utilities and mods. Look at the "Clear and Present Danger" guide in my signature for detailed instructions, and on the associated forum posts here and here. There are some mods that can install using the version of FOMM built into MO, and a few that need FOMM-fork which can run with MO. There are examples in the guide for both cases. The guide has a small troubleshooting section including some typical reasons why the game fails during launch. By the way, the current FO3Edit version is 3.0.32 which came out in July 2014.

I'm really glad to see you are healthy enough to post on the forums again CJ. It's also always great to have your perspective on the mods here again. I use Frostfall, and like Teabag86 I find Inns and Taverns extremely helpful - some warm places in otherwise bitter cold areas of Skyrim. I don't use the inns or taverns near cities that conflict with other mods. When the exciting new changes to REGS are complete, I'll probably modify I&T to create a version for myself that only includes the remote inns and taverns. I'm not using an ENB, at least right now, and like some others have mentioned I have not seen the FPS problems with Dawn of Whiterun that some have reported. I'm mostly looking forward to the set of city mods that has been discussed here over the past few weeks as it sounds like they should be reasonably compatible.

You were very close. The Blackened FWE+MMM+Project Beauty patch included a subrecord that pointed to a mesh from EVE, which didn't exist since I hadn't loaded EVE in the profile I was using. Maybe I should just load EVE and live with the transient VRAM usage explosions. My graphics card can handle it, but I was trying to see which mods could be included for users with 1Gb VRAM. Several years ago when I played Fallout 3 with a 1GB VRAM card EVE was the main cause of CTDs for me.