Thalan1a Posted March 13, 2011 Share Posted March 13, 2011 I am trying to use FNVEdit to check mod conflicts but every time I load it I get this: "an error occured while loading modules. Editing is disabled. Check the message log and correct the error". the last few messages in the message log shows this: [00:02] Background Loader: [FalloutNV.esm] Building FormID index[00:03] Background Loader: [FalloutNV.esm] FormID index built[00:03] Background Loader: [FalloutNV.esm] Building EditorID index[00:03] Background Loader: [FalloutNV.esm] EditorID index built[00:03] Background Loader: [FalloutNV.esm] Warning: File contains duplicated top level group: GRUP Top "AMEF"[00:03] Background Loader: Fatal: <Exception: FormID [00160C43] in file FalloutNV.esm refers to master file FalloutNV.esm which has not been assigned a global load order>[01:45] Background Loader: finished Any advice on what to do would be great. I have never used FNVEdit before so I don't know what to do at this point. Link to comment Share on other sites More sharing options...
davidlallen Posted March 13, 2011 Share Posted March 13, 2011 Check your load order and make sure that falloutnv.esm is first. Also, sometimes despite your load order, you can have this problem if the file timestamp of a mod you are loading, is older than the file timestamp of falloutnv.esm. I recently had this problem when I took a previous mod, and used it with my new re-installation of the game. There may be a cleaner way, but what I did was to take the mod with the old timestamp, bring it up in geck, make some change, make it back to the original (not using "undo") and then save. This saves with a new timestamp. Link to comment Share on other sites More sharing options...
Thalan1a Posted March 13, 2011 Author Share Posted March 13, 2011 Check your load order and make sure that falloutnv.esm is first. Also, sometimes despite your load order, you can have this problem if the file timestamp of a mod you are loading, is older than the file timestamp of falloutnv.esm. I recently had this problem when I took a previous mod, and used it with my new re-installation of the game. There may be a cleaner way, but what I did was to take the mod with the old timestamp, bring it up in geck, make some change, make it back to the original (not using "undo") and then save. This saves with a new timestamp. Unfortunantly I don't know anything about load orders or how to use the geck. I never could get the geck to install properly and I have tried over 5 times. Link to comment Share on other sites More sharing options...
davidlallen Posted March 14, 2011 Share Posted March 14, 2011 If you install the FNV geck into the FNV directory, there should be no problem. If you install the FO3 geck, or you install into some other directory, then it won't work. Can you look in Windows Explorer and confirm that the mods you want to check conflicts for, have a newer timestamp than falloutnv.esm? This is *probably* the problem, but I suppose it could be something else. There is no one right way to change timestamps, there may be many ways. Link to comment Share on other sites More sharing options...
RealmEleven Posted March 22, 2011 Share Posted March 22, 2011 (edited) I run FNVEdit "as administrator", because I encountered a similar problem when I first fired up FNVEdit. To do this: Context-click the shortcut for FNVEditSelect Run as administrator from the context menuConfirm when Windows asks if it is really you trying to start this program If this allows you to run FNVEdit properly, you can set it to run as administrator each time by doing as follows: Context-click the shortcut for FNVEditSelect Properties from the context menuGo to the Shortcut tabClick the Advanced buttonTick the Run as Administrator checkboxClick the OK button once for the Advanced window and again for the Properties Window Et voila! That just makes it a bit easier. The problem is caused by the fact that the mods are located deep under the Program Files directory of the file system which, for security reasons, is not a smart place for the operating system to allow file alterations to be made. Normally, user data winds up being written to My Documents and application data to, funnily enough, Application Data and the operating system is fine with that because executable files are not supposed to launch from those areas. It is likely that one of the up and coming versions of Windows will disallow file execution from these areas and finally close a big hole in the overall security of the system. In the meantime, files that alter anything in directories designated for executable files and their libraries must get manual confirmation to ensure that there is nothing going on behind your back. The GECK also needs to be run as administrator for the same reason. [EDIT Title=Addition as Follows]That last was to address the "editing is disabled" issue. Load order is a common problem, especially considering that updates are automatic and load order is based on the timestamps attached to the master files. The most common and easiest way to fix that problem (at least to my knowledge) is the Fallout Mod Manager also known as FOMM, which can be found here:http://www.newvegasnexus.com/downloads/file.php?id=36901[/EDIT] I hope this helps - and whatever you do, never ever run any web browser as administrator no matter how safe people say it is... Edited March 22, 2011 by RealmEleven Link to comment Share on other sites More sharing options...
gavinsco1 Posted October 5, 2014 Share Posted October 5, 2014 (edited) Please ignore this post... Edited October 5, 2014 by gavinsco1 Link to comment Share on other sites More sharing options...
Recommended Posts