As I'm going through the Clear & Present Danger guide I noticed something that I'm sure would've been caught before if it was wide-spread, so I can only conclude it is peculiar to me.
I've just cleaned all the esms for Fallout 3 and I was just going to check the process got everything by running LOOT.
As you are aware MO has a stripped down version of 0.5 and the latest stable version was 0.6. I also have the beta version, 0.7.
I usually just go with 0.6 and have it set on my MO toolbar. So I clicked it, ran it and looked at the report. Imagine my surprise when the DLC were all tagged as dirty and in need of cleaning. Maybe I had them in the wrong place, perhaps for some reason they didn't update the files in the Data folder and were hiding in the 'overwrite' folder? Maybe?
On a whim I ran the MO version, 0.5. That report showed all the esms as clean. WTH. Okay lets try 0.7. Same thing, all the DLC files are correctly shown as cleaned and need no attention.
To test this further I ran the 0.6 version from outside MO and again it showed them as dirty. I then ran the 0.7 version and it too correctly showed them clean.
What's the story here? Has no one ever seen this happen with LOOT v0.6? I'm finding hard to believe this is just me.
Question
GrantSP
As I'm going through the Clear & Present Danger guide I noticed something that I'm sure would've been caught before if it was wide-spread, so I can only conclude it is peculiar to me.
I've just cleaned all the esms for Fallout 3 and I was just going to check the process got everything by running LOOT.
As you are aware MO has a stripped down version of 0.5 and the latest stable version was 0.6. I also have the beta version, 0.7.
I usually just go with 0.6 and have it set on my MO toolbar. So I clicked it, ran it and looked at the report. Imagine my surprise when the DLC were all tagged as dirty and in need of cleaning. Maybe I had them in the wrong place, perhaps for some reason they didn't update the files in the Data folder and were hiding in the 'overwrite' folder? Maybe?
On a whim I ran the MO version, 0.5. That report showed all the esms as clean. WTH. Okay lets try 0.7. Same thing, all the DLC files are correctly shown as cleaned and need no attention.
To test this further I ran the 0.6 version from outside MO and again it showed them as dirty. I then ran the 0.7 version and it too correctly showed them clean.
What's the story here? Has no one ever seen this happen with LOOT v0.6? I'm finding hard to believe this is just me.
0 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now