Deadmano Posted May 8, 2016 Share Posted May 8, 2016 Hey guys! So I'm having a REALLY weird issue that has set me back WEEKS of hard work... Basically I was putting together a rather large patch for the hundreds of mods that I have, when today I realised that a ton of records have the incorrect FormID, which then causes many issues like "Error: Could not be resolved >" to appear. I have no idea when this started, or why... But another mega patch I did that has thousands of records did not suffer this issue... :sad: If I manually change the FormId of a record to the master it was referencing, all is well, less the error part that you need to copy across... But obviously this isn't something I can do with the near thousand or so records across this patch.... Any ideas as to how this happened, and what I can do to try resolve the issue? Thanks in advance! :) Link to comment Share on other sites More sharing options...
exploiteddna Posted October 14, 2016 Share Posted October 14, 2016 Hey guys! So I'm having a REALLY weird issue that has set me back WEEKS of hard work... Basically I was putting together a rather large patch for the hundreds of mods that I have, when today I realised that a ton of records have the incorrect FormID, which then causes many issues like "Error: Could not be resolved >" to appear. I have no idea when this started, or why... But another mega patch I did that has thousands of records did not suffer this issue... :sad: If I manually change the FormId of a record to the master it was referencing, all is well, less the error part that you need to copy across... But obviously this isn't something I can do with the near thousand or so records across this patch.... Any ideas as to how this happened, and what I can do to try resolve the issue? Thanks in advance! :smile: always make sure you use the 'Sort Masters' function when you start adding new masters to the plugin header.. you want to try to keep them in the order of the accepted load order. This becomes an issue when, for example, you make a patch that requires dragonborn as a master. So your header only has Skyrim.esm and DB.esm in the header. Then next week you go back and add another override that requires dawnguard. you then add DG to the master list, but it is out of order.. the header would read:1. skyrim.esm2. dragonborn.esm3. dawnguard.esm you should then right click and select 'sort masters' from the context menu. This function can go a long ways to preventing these types of issues.. not always, but much of the time. Good luck Link to comment Share on other sites More sharing options...
Recommended Posts