Jump to content


Photo

DynDOLOD Beta for Skyrim Special Edition and Skyrim VR 2.59

dyndolod lod special edition sse

  • Please log in to reply
1388 replies to this topic

#1381 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,131 posts

Posted Yesterday, 05:28 AM

Sorry for double posting(my account is too new for me to edit my last post)

I still get the map crash issue with only DynDOLOD.esm active, I can only avoid it if I have both disabled.

Good. That narrows it down quite a bit.

 

You can now do a binary search type of thing where you make a backup of the plugin and use xEdit to remove batches of records from the ESM. If the problem is gone, go back to the backup and remove other records. That way you will eventually end up only with the record causing the problem.

 

Logically the issue should only be with records with the worldspace Tamriel. So start by removing all other worldspaces. You do this in xEdit by right clicking on the worldspace name and selecting remove.

 

If it still has the issue after removing them, remove the Tamriel persistent cell 00000D74. If the problem goes away go back to the update and remove all "Blocks" which are childs of 0000003C Tamriel. If the problem seems to be in one of the "Blocks", remove them one by one or in 50% batches. The continue with the subblocks etc. Once you are down to a cell, remove the content of the CELL first.

 

It is possible that the problem is with something on the worldspace record 3C itself. So you might want to do a quicktest with removing all childs first.

 

In any case you should be able to narrow it down to a single record and it will go pretty quickly if you remove half the records each time.

 

Let me know if anything is unclear or needs more explanation.


  • 0

#1382 softboy_rodvt

softboy_rodvt

    Prisoner

  • Members
  • 7 posts

Posted Yesterday, 12:03 PM

So, having followed your instructions and stripping the DynDOLOD.esm's worldspace records to only 0000003C, I still get the interior cell map crash.

I feel I should clarify; I only get this crash when either starting or loading a save in an interior cell. If I open the map in an interior cell, having loaded into an exterior worldspace before that, the map shows up just fine with no crash. If I load the autosave made from the cell transition of entering a building and then pull up the map, it results in a crash when opening the map.

:crying:


  • 0

#1383 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,131 posts

Posted Yesterday, 12:05 PM

So, having followed your instructions and stripping the DynDOLOD.esm's worldspace records to only 0000003C, I still get the interior cell map crash.

I feel I should clarify; I only get this crash when either starting or loading a save in an interior cell. If I open the map in an interior cell, having loaded into an exterior worldspace before that, the map shows up just fine with no crash. If I load the autosave made from the cell transition of entering a building and then pull up the map, it results in a crash when opening the map.

:crying:

And if you remove the worldspace 3C from the plugin the problem is gone?


Edited by sheson, Yesterday, 12:06 PM.

  • 0

#1384 softboy_rodvt

softboy_rodvt

    Prisoner

  • Members
  • 7 posts

Posted Yesterday, 12:11 PM

And if you remove the worldspace 3C from the plugin the problem is gone?

Just tried that now; the problem still persists, even with every single worldspace record removed from DynDOLOD.esm.

Maybe it's time to just redo my load order, maybe 280 plugins isn't all that healthy to begin with, even if they're half ESL/ESPFE


Edited by softboy_rodvt, Yesterday, 12:13 PM.

  • 0

#1385 jmarceno

jmarceno

    Prisoner

  • Members
  • 2 posts

Posted Yesterday, 03:06 PM

Well typically works fine with multiple cores (and HT) on with one CPU.

 

The multi-threading is a bit brittle with Delphi and me not giving it all the required (if this was paid software) attention to potential deadlocks, resource or memory contention issues. Eventually xEdit and DynDOLOD will switch to the newer Delphi version - which seems to be much more picky in this regard as well. That means some time in the future that might just solve that issue for you.

 

The x86 version most likely just runs out of memory. The next version will use less memory when doing the atlas, so it should be able to create the atlas as well. It might run through require the same treatment as the x64 in your case.

 

The LODGen.exe process is started only once the atlas has been created so it should have no influence on this issue.

Thank you for the reply. Will continue to use with the 1 core affinity them. regards.


  • 0

#1386 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,131 posts

Posted Today, 01:45 AM

Just tried that now; the problem still persists, even with every single worldspace record removed from DynDOLOD.esm.

Maybe it's time to just redo my load order, maybe 280 plugins isn't all that healthy to begin with, even if they're half ESL/ESPFE

Interesting. If that is the case, remove the remaining records in batches as well.

 

You have SSE Engine Fixes installed?


  • 0

#1387 softboy_rodvt

softboy_rodvt

    Prisoner

  • Members
  • 7 posts

Posted Today, 11:04 AM

Interesting. If that is the case, remove the remaining records in batches as well.

 

You have SSE Engine Fixes installed?

I do, although removing Engine Fixes didn't solve my issue either

I ended up just reinstalling, hoping that a less bloated load order won't have this issue. My Skyrim VR install with DynDOLOD also doesn't have this problem either lol

Another thing I noticed is, when running the .dmp through WinDBG, the crash seemed to be due to an Acces Violation(ExceptionCode: c0000005). I have to wonder why it'd be reading as a memory issue on my end, all 32gb of my RAM is pretty fine last I checked. Maybe this reinstall will work it out either way :turned:


Edited by softboy_rodvt, Today, 11:13 AM.

  • 0

#1388 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,131 posts

Posted Today, 12:16 PM

I do, although removing Engine Fixes didn't solve my issue either

I ended up just reinstalling, hoping that a less bloated load order won't have this issue. My Skyrim VR install with DynDOLOD also doesn't have this problem either lol

Another thing I noticed is, when running the .dmp through WinDBG, the crash seemed to be due to an Acces Violation(ExceptionCode: c0000005). I have to wonder why it'd be reading as a memory issue on my end, all 32gb of my RAM is pretty fine last I checked. Maybe this reinstall will work it out either way :turned:

My question about Engine Fixes was about the persistent reference cap, since it would notify you.

 

The x5 Access Violation is such a generic error message, it seems it could mean anything.


  • 0

#1389 softboy_rodvt

softboy_rodvt

    Prisoner

  • Members
  • 7 posts

Posted Today, 01:06 PM

My question about Engine Fixes was about the persistent reference cap, since it would notify you.

 

The x5 Access Violation is such a generic error message, it seems it could mean anything.

Hmm, would it have notified me in the EngineFixes.log? I'm willing to bet it might be the persistent reference cap being the issue, but I'm not seeing anything relating to that in that log.


Edited by softboy_rodvt, Today, 01:07 PM.

  • 0



Also tagged with one or more of these keywords: dyndolod, lod, special edition, sse

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users