Hi, first question on the forum.
Followed the install process for dyndolod 2.98, using vortex and ran loot once the load order conflicts had been resolved.
Got a single, worrying error from loot:
- CRC: 03E1DF5C
- Attributes: Master Plugin, Light Plugin
- Error: This plugin contains records that have FormIDs outside the valid range for an ESL plugin\. Using this plugin will cause irreversible damage to your game saves\.
I searched the manual and the forums and couldn't find anything looking like this. Has anyone come across this and if so what is the fix?
I haven't run the game since seeing this error as I'm already a couple of hundred hours into playing and don't want to lose my save files.
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.
So I posted this over on the Wrye Bash thread but since most of them don't actually use MO2 (instead opting purely for WB), they directed me over here.
Anyway, what happens is that whenever I attempt to start Wrye Bash standalone (306 or the new 307 beta 1) from within MO2 (both 2.0.7 and 126.96.36.199), it instantly crashes.
The MO2 log says the following:
The Wrye Bash log ("Wrye Bash.exe.log") reads:
Anyone seen this before or have a workaround? I'd like to get this running as merging oodles of records in xEdit is not all that appealing.
Recently Browsing 0 members
No registered users viewing this page.