Jump to content
  • 0

SR Conflict Resolution Patch


Geheiligt

Question

Hi all, to start I hope this is the proper forum for this thread~

 

I recently completed an SR:LE install, briefly tested, and went on to install REGS. As of now I am at the SR:LE - REGS conflict resolution step and in the process of making my REGS - SRLE Patch.

 

I will admit, I learned how to make the patch through TES5Edit initially via following SR:LE, and then a bit of laziness hit me and I simply downloaded the pre-made patch.

 

However, I encountered an odd error within the SR Conflict Resolution.esp patch.

 

Here is the TES5Edit bug report. (Probably redundant, details below)

 

date/time         : 2014-07-02, 19:34:24, 226ms

computer name     : MKGDY-DESK
user name         : Mkgdy
registered owner  : Mkgdy
operating system  : Windows 8 x64 build 9200
system language   : English
system up time    : 16 days 22 hours
program up time   : 27 minutes 53 seconds
processors        : 8x Intel® Core i7 CPU 950 @ 3.07GHz
physical memory   : 7591/12286 MB (free/total)
free disk space   : (C:) 16.27 GB (D:) 413.93 GB
display mode      : 1920x1080, 32 bit
process id        : $1270
allocated memory  : 1.63 GB
executable        : TES5Edit.exe
exec. date/time   : 2013-10-05 04:14
version           : 3.0.31.0
compiled with     : Delphi XE
madExcept version : 4.0.5
callstack crc     : $b421e453, $2859942f, $3a67e996
exception number  : 1
exception class   : Exception
exception message : Found a LGTM reference, expected: IMGS.
 
main thread ($142c):
0074087f +005b TES5Edit.exe wbInterface       9713   +4 TwbFormIDChecked.FromEditValue
00734d0f +0037 TES5Edit.exe wbInterface       6040   +4 TwbIntegerDef.FromEditValue
007729fb +00fb TES5Edit.exe wbImplementation  9380  +13 TwbSubRecord.SetEditValue
0077a67a +006a TES5Edit.exe wbImplementation 10878   +6 TwbElement.Assign
00759d04 +00cc TES5Edit.exe wbImplementation  3338  +15 TwbContainer.Assign
0077058c +0564 TES5Edit.exe wbImplementation  8605  +85 TwbSubRecord.Assign
0075f515 +0605 TES5Edit.exe wbImplementation  4960 +105 TwbMainRecord.Assign
0075f1a3 +0293 TES5Edit.exe wbImplementation  4911  +56 TwbMainRecord.Assign
007756d6 +18e2 TES5Edit.exe wbImplementation  9863 +240 TwbGroupRecord.AddIfMissing
00743ca0 +0124 TES5Edit.exe wbImplementation    87  +16 wbCopyElementToFile
009f3ab2 +047e TES5Edit.exe frmViewMain       7013  +95 TfrmMain.mniViewHeaderCopyIntoClick
00525caf +00a7 TES5Edit.exe Menus                       TMenuItem.Click
005271ab +0013 TES5Edit.exe Menus                       TMenu.DispatchCommand
0052838a +0082 TES5Edit.exe Menus                       TPopupList.WndProc
005282d9 +001d TES5Edit.exe Menus                       TPopupList.MainWndProc
004c4d6c +0014 TES5Edit.exe Classes                     StdWndProc
75ae8a61 +000b user32.dll                               DispatchMessageW
005b1f4b +00f3 TES5Edit.exe Forms                       TApplication.ProcessMessage
005b1f8e +000a TES5Edit.exe Forms                       TApplication.HandleMessage
005b22b9 +00c9 TES5Edit.exe Forms                       TApplication.Run
00a1abb3 +005f TES5Edit.exe TES5Edit            71   +7 initialization
758486e1 +000c KERNEL32.DLL                             BaseThreadInitThunk
 
thread $16b4 (TWorkerThread):
75a31123 +66 KERNELBASE.dll                      WaitForSingleObjectEx
75a310af +0d KERNELBASE.dll                      WaitForSingleObject
005d2001 +19 TES5Edit.exe   VirtualTrees 6308 +3 TWorkerThread.Execute
00472c87 +2b TES5Edit.exe   madExcept            HookedTThreadExecute
004c20a6 +42 TES5Edit.exe   Classes              ThreadProc
00407530 +28 TES5Edit.exe   System          7 +0 ThreadWrapper
00472b69 +0d TES5Edit.exe   madExcept            CallThreadProcSafe
00472bd3 +37 TES5Edit.exe   madExcept            ThreadExceptFrame
758486e1 +0c KERNEL32.DLL                        BaseThreadInitThunk
>> created by main thread ($142c) at:
005d1ee9 +19 TES5Edit.exe   VirtualTrees 6251 +1 TWorkerThread.Create
 
thread $f9c:
758486e1 +c KERNEL32.DLL  BaseThreadInitThunk
 
thread $138c:
758486e1 +c KERNEL32.DLL  BaseThreadInitThunk

 
I'm not sure if that's helpful, so here is basically what I have found:
 
SR Conflict Resolution Patch.esp a "LGTM" reference in Cell Block 3 Sub-Block 5 000CAB91 WinterholdCollegeHallofAttainment under "XCIM - Image Space". The error I received when following the REGS - SRLE conflict resolution patch (Referenced below) stated TES5Edit expected an "IMGS" reference but received an "LGTM" reference. 
 
Every .esp record contains "FarmInteriorIS [imgS:00059B60]" up until Ele-Interior Lighting Merged.esp, which contains "JZWinterholdInt_IS [imgS:AF02D651]". Followed by the downloaded SR Conflict Resolution.esp which contains "JZDB_DefaultDun_LT [LGTM:AF02D5F1]".
 
When I cross-referenced the SRLE conflict resolution wiki page, it doesn't reference the XCIM header, rather simply copy the ELE - Interior Lighting Merged.esp record, followed by a DATA record from the USKP.
 
 
Could I have perhaps done something wrong, or is the SR Conflict Resolution patch outdated and/or referencing the wrong image space?
 
This has been a great learning experience so far, going through both SR:LE and REGS. Thank you all who are involved!
 
SR:LE Conflict Reference (per wiki)

Block 3 > Sub-Block 5 > 000CAB91 WinterholdCollegeHallofAttainment

Conflict Resolution: Use record from ELE-Interior Lighting Merged.esp then move the DATA - Flags records from Unofficial Skyrim Patch.esp. Remove the XCCM - Sky/Weather from Region record.
Problem Resolved: Fix from unofficial patches were not properly forwarded.

 

REGS Conflict Reference (per wiki)

Cell Block 3 Sub-Block 5 000CAB91 WinterholdCollegeHallofAttainment

  • Use record from SR Conflict Resolution.esp.
  • Copy the Owernship, the XCMO – Music Type and the XLCW – Water Height records from CWIELnFXPatch.esp.

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

  • 0

Just to make your aware, I have maintained a pure SR:LE install, a SR:LE install with my own mods added, a pure SR:LE - REGS install, and a SR:LE - REGS install with my own mods added. I am well versed in all the modding tools thanks to Neovalen. That said I have never learned how to do conflict resolution on my own. If you are good at it, then I would recommend a SR:LE - REGS install. I personally I have given up on REGS because while it says it is compatible with STEP and SR:LE, the truth is that Nearox retired from Skyrim for Elder Scrolls Online (ESO). It seems he has sense returned though I do not know in what capacity. CJ never had a SR:LE build to my knowledge, so Nearox was responsible for SR:LE compatibility.  If you look the page has not been updated since June 13th (a life time in the computer/internet age), but SR:LE has and continues to under go major changes. For REGS it is easy to keep up with the latest version of STEP as it is largely static.  That however, is not true for SR:LE. Therefore, unless you have to know how to identify and resolve conflicts between SR:LE and REGS, I would avoid it for now. By the way, you would probably find more help in the REGS forum.

 

EDIT: Tried to fix grammar and context.

Edited by DanimalTwo
Link to comment
Share on other sites

  • 0

I would not worry about the conflict resolution for REGS and SR:LE at present. It has not been updated for a while. They are only minor conflicts AFAIA and should not hurt the game. I have an up to date SR:LE install with REGS and Rquiem all working nicely without doing any other patching. REGS does work well with SR:LE. The CR for this guide (SR:LE) is fine and you need to keep it as is. Any questions to do with REGS should really be addressed to the REGS part of this forum - LINK.

 

::):

Link to comment
Share on other sites

  • 0

Thanks for the clarification everyone  ::D: . I guess my primary confusion was regarding the downloaded SR Conflict Resolution patch, and why (or where) the LGTM reference was there, given that particular record would have been copied from ELE - Merged Patch and gave me an error.

Link to comment
Share on other sites

  • 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.