Jump to content
  • 0

Error: could not be resolved for XLCN - Location


G4Z

Question

Hi Sheson

 

I have recently installed Lady Lexy's LOTD Guide, Everything was plain sailing until i got to the end of the guide where you generate DynDOLOD.... Typical i know  :lol:

 

I get this error: https://imgur.com/pdrDjIJ

 

I am hoping this is an easy fix and maybe you can point me in the right direction, i am aware you have to find this error in xedit. 

 

Things i have tried to no avail: 

 

--- tried to find 08060D7E form id and cannot seem to find it anywhere. (not even sure if i am meant to look for this)!      08 in my load order is Skyrim Project Optimization - Full Version, I have checked all blocks within that mod and XLCN Location are all green.

 

--- unchecked Cutting Room Floor in MO2 and tried to generate, And any patches relating to Cutting Room Floor.

--- unchecked Audio Overhaul Skyrim just as a test considering that mod is at the end of the log.

 

 

That is about it really.

 

Thanks  :;):

 

 

Link to comment
Share on other sites

2 answers to this question

Recommended Posts

  • 0

FAQ: Exception in unit xxx line xxx: [xxxxxxxx]

 

A: There is a plugin in the load order that links to a non existing form id. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help.

 

 

Of course you can not find 08060D7E, that *is* the problem. A plugin links to that form id, but it does not exist.

Link to comment
Share on other sites

  • 0

FAQ: Exception in unit xxx line xxx: [xxxxxxxx] < Error: Could not be resolved >

 

A: There is a plugin in the load order that links to a non existing form id. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help.

 

 

Of course you can not find 08060D7E, that *is* the problem. A plugin links to that form id, but it does not exist.

:clap:  I have just found it! Also generated DynDOLOD with 0 problems. 

 

Turns out 11060D7E was the problem weirdly enough. The error was situated inside one of the merge plugins during the installation. 

 

Delete this thread if need to Sheson, and thanks  ::):

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.