Recently I encountered an issue with missing main menu data on start up. After a laborious process of elimination, the problem was, amusingly, my conflict resolution patch. The symptoms were reproducible and unique to the patch. The patch was based on the SRLE Template, modified over the last few days to resolve lingering issues with my particular build. TES5Edit offered no warnings or error messages, and there was nothing readily apparent to indicate an issue. I made some successful test runs throughout the editing process, but somewhere it simply went awry. Obliviously the mistake was mine, but unlike my previous mistakes, I could not ascertain what I had done wrong. So I have created a new modified SRLE Conflict Resolution Template that currently works without issue. However, I need to make additional edits to get all of my added mods to work right. Before I start this process again, I respectfully request some guidance. Is it possible to make too many edits? For a Patch to have too many masters? I generally avoid touching anything in the records that I don't understand in terms of function, but I was wondering if perhaps there are somethings that simply should not be touched. I will be starting the process again tomorrow, and I plan to take a more systematic approach with more integrated test runs. However, in the interim, if there is any helpful advice available, it would be greatly appreciated.
Hello all.After going thoroughly with the guide, I have some kind of problem with the ENB files. Whenever I start up my Skyrim, I get a limegreen screen.I hear the game in the background playing and can hear the menu sounds.If I disable ENB through the ENB Manager, it's all fine.I tried googling but found no answer. I have an ATI AMD Radeon HD8970M graphic card with 2gb.
Thanks if anyone can help me with this particular problem.
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.
Recently Browsing 0 members
No registered users viewing this page.