MO and Breeze Textures in FO3

[PupCrypton]

I'm kinda stumped on this and I think the answer is going to be cave-man simple, or somewhat involved.

 

Playing through FOMM with Midharstic ENB installed and running perfectly with latest ENB executable, I have no problems with Breeze Body Replacer, and its patch. All the textures look great with no smearing and nothing missing. I've installed it with all of the options, and without the body suits as well.

 

And then there is Mod Organizer.

 

I install it and the patch in MO through the FOMod, which works perfectly. I install it with the same options. And I get smearing and missing textures. Here's what I'm talking about (troll faces are for youngins, especially my own who sometimes play a more sanitized version of Steam games on my PC):

 

 

 

 

 

There's no musculature, no hair, and no navel. No tattos, no nothing. I tried exporting the installed and working version from FOMM, and then re-packing it for installation via MO. That didn't work at all.

 

So, if anyone has any advice on how to fix this problem I'd surely love to know about.

 

Thanks all!

Edited June 29, 2015 by PupCrypton

[Purr4me]

Fomm :

 

Playing through FOMM with Midharstic ENB installed and running perfectly with latest ENB executable, I have no problems with Breeze Body Replacer, and its patch. All the textures look great with no smearing and nothing missing. I've installed it with all of the options, and without the body suits as well.

used default ini data to control overlay's

Mo uses it's own ini data to control overlay's

 

your bug is separated..and your right, it is cave man simple.

qualifying ini files need to be in the C:\users\(username)\My Documents\My games\fallout3\ *.ini

Mo uses these to install but the ini files it uses are not those, this same thing applies to ENB's their INI files and or instructions need to be in the profile mangers location with in Mo.

 

your only other choice given is to put the ini instructions directly into the root of the game right next to home central, this will fix it, try that and see

Edited June 29, 2015 by Purr4me

[PupCrypton]

Purr4Me: Nope. That's not it. I understand how ini files work and where they are located in MO <Profiles>, and where they are installed by Bethesda/Steam in My Documents <Games>. And I did of course correctly modify the ini files for both the ENB and FOMM, and then made the appropriate changes to the ini files in the MO profile when I switched. Otherwise FO3 wouldn't have launched through FOSE in MO to begin with.

 

I use MO exclusively with Skyrim, which I've played for some years. I used FOMM exclusively for FO3 until about a week ago, when I switched to MO, and that's when the trouble started.

 

So, thanks for the input. But that's not the answer.

[Purr4me]

try and see if mod's advanced section got messed up, giving knowledgeable about it I need not direct you but rather throw ideas as to where to look.

so, back track a bit for if you can, before making any changes and the game was solid......what did you do?

Mo's tools are very touchy, I am not sure ENB instructions will get along well with mo's ini's I know I did try that and it does work, I also know I screwed it up toughing the wrong settings in mod's ini configuration.

 

suppose we try and find out what can or can't work. Dis-function is useful here, serves as a test bed.

 

until about a week ago, when I switched to MO, and that's when the trouble started.

 

ya know, are you running fomm from inside MO ?

Edited June 30, 2015 by Purr4me

[Purr4me]

what I am getting at .is this, if it worked before, and you changed the start-up programs, fomm was in-control of the system plugin.txt file, Mo does not use that, so now, you have a different set of instructions acting on the mods files.

 

IF Mo runs Fomm, xedit, Fose and every thing should get back to normal...of corse you will be executing the game from with in fomm VIA fose loader but still it's Fomm VIA Mo...only a single step.

any other way? no. you have to start a new game.

Edited June 30, 2015 by Purr4me

[Purr4me]

it's like some one pulled the rug out from under you.

one moment your running hot and heavy plugin.txt

the next. new guy Mo default profile.txt

 

these two are not the same and one last thing here, Mo will not use the default game plugin.txt.

[PupCrypton]

Hehehe. No. Its none of that. FOMM is a mod-handler, like Mod Organizer. You don't run the one through the other. FOMM was made specifically for FO3. However, it does not isolate mods as MO does, and that is why MO was/is attractive, and is phasing out NMM. So when you overwrite a file with FOMM, its kinda permanent until you uninstall and then re-install. With MO, you just move the mods around because they are isolated.

 

ENB should not interfere with any graphics mod. Further, if your ini files are not properly set, the game is unplayable (graphics go haywire).

 

I am starting to think the problem lies in how MO handles and translates files through the executible. With FOMM, the textures, meshes, esm's and esp's (and whatever else) are placed within the Data folder. With MO, they are not - they are kept separated. MO was actually designed for Skyrim, so I think there's something getting lost in translation because I've noticed other slight texture anomalies as well when using MO. They are not present in FOMM, and the load order is the same.

 

Thanks for your ideas!

Edited July 2, 2015 by PupCrypton

[Purr4me]

 

1. FOMM is a mod-handler, like Mod Organizer.

Correct.

 

You don't run the one through the other

Totally false assumption on your part.

 

FOMM was made specifically for FO3.

Correct:

 

However, it does not isolate mods as MO does

Wrong, it does and it does not, but used as I directed, it does.

 

So when you overwrite a file with FOMM, its kinda permanent until you uninstall and then re-install

Correct:

 

With MO, you just move the mods around because they are isolated.

correct:

 

ENB should not interfere with any graphics mod

Incorrect, It most certainly does inter-linearly interfere with graphics mods, man that there is so far off base, I am at a loss for words.

 

With FOMM, the textures, meshes, esm's and esp's (and whatever else) are placed within the Data folder

Correct IF and Only IF you run it "standalone" Not as I directed you to use it.

 

MO was actually designed for Skyrim,

This is Highly disputable sense the FOMOD *.dll's are FOMOD related Oblivion and Fo3 based..this is not disputable. It 's the core of Mod's design, it's the core of Loot, it's the core of NMM and Fomm as well....that is an incorrect assessment.

 

I think there's something getting lost in translation because I've noticed other slight texture anomalies as well when using MO.

Of corse there is Mo uses different graphics controls, these are isolated controls to control virtual space and other things going on for isolating programs.

 

They are not present in FOMM, and the load order is the same.

They are there only IF you active and use the utility built in and no, the load orders are not the same.

---------------------

ok, so I give to you a possible way to isolate a bug issue ? and you don't believe me?

here:

• http://postimg.org/gallery/2p0f1fg3a/
• http://postimg.org/image/i7sundmdh/

what ever is going on there with your PC and game files is out of my domain, I am not here to convince you on how to experiment, I thought I was doing you qa favor by divulging a method to fix your game.

I am one of those you can't fool....I test every thing openly and make damm sure I'm right before I make any posts here.

 

you ,always have that choice to use the information or Ignore it...but darn wrong in disputing a gift.

have fun.

kitty