Jump to content

sheson

Mod Author
 View Profile  See their activity

  • Posts

    13,180

  • Joined

  • Last visited

  • Days Won

    431

 Content Type 

Everything posted by sheson

  1. sheson
    I think is error is related to this The Bashed Patch is most likely fine if you use a recent (Discord) version. Test with next DynDOLOD version and then let me know. I hope to release it within 24 hours. Unrelated: Remove SkyFalls/Mills for best performance and visuals. Edit: This should be fixed now in DynDOLOD 2.48
  2. sheson
    FAQ: DynDOLOD.exe: Exception in unit xxx line xxx: Can not copy xxxx from xxxx.esp into xxx.esp A: Often caused by a broken bashed patch. Use a newer Wrye Bash version to create the patch or do not use the merge patches option. A: There might be plugin in the load order with errors. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help. This may also be caused by having old DynDOLOD Resources SE or *.patch files, however it is hard to tell without the entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_TES5_log.txt
  3. sheson
    I hope with "redoing the process" you mean creating an archive from the already existing and valid output and not running DynDOLOD over and over again.
  4. sheson
    Delete old bugreport or log files, since new reports are usually just added to existing files letting them grow. Use an external service like pastbin or a file hoster if the size exceeds limits. What you were able to post was enough, though. This bug should be fixed with the next version, which I hope to release some time this Friday/Weekend.
  5. sheson
    Since DynDOLOD.exe clearly has created and saved the DynDOLOD plugins your problem is not with DynDOLOD. This forum is for support with DynDOLOD, not some unrelated third party programs. The obvious assumption would be that there is a problem with the used compression program A first troubleshooting step would be to update it or use a different program or to simply move the output to the MO mod folder directly.
  6. sheson
    it should still work the same way. The error is bug I need to fix. To help with that can you please upload the bugreport.txt it created when you had the problem with the latest version trying to do Open Cities?
  7. sheson
    There is only one DynDOLOD Standalone and the latest version is 2.47. It is the first file listed on Nexus https://www.nexusmods.com/skyrim/mods/59721?tab=files When DynDOLOD.exe is started it will show a line DynDOLOD Worlds 2.48 (1) using TES5LODGen by Ehamloptiran, Sheson and Zilav, starting... after it finished loading plugins, just before it opens the options window.
  8. sheson
    The latest version is 2.47. The log you uploaded shows 2.44. If the error still happens with the latest version, upload that bugreport.txt please.
  9. sheson
    Also try the second suggestion, starting without the DynDOLOD plugin and see if generating from scratch works. Use latest version of DynDOLOD.
  10. sheson
    FAQ: Game: DynDOLOD requires PapyrusUtil A: If the intention is to use DynDOLOD DLL, make sure the papyrus scripts from DynDOLOD DLL overwrite the papyrus scripts from DynDOLOD Resources.
  11. sheson
    It looks like you might have been running the tools in their default mode for Skyrim, probably because the -sse command line argument might have been not added correctly to run them in Skyrim Special Edition mode. The output settings in TexGen do not change the ability to read/find textures in the load order. It is also possible that running the tools in a special windows folder like Desktop under c:\users\ might be blocking the tools from properly writing/reading files.
  12. sheson
    Thank you that helped. This will be fixed in the next version, which should be available soonish.
  13. sheson
    Could be caused by Antivirus or as the log says, try to: Ignoring Bashed Patch, 0.esp. Please remove from load order if generating LOD does not complete successfully! Update an existing DynDOLOD.esp? If this is not successful start from scratch. If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_TES5_log.txt to official forum
  14. sheson
    To create the DynDOLOD.esm from scratch DynDOLOD copies the data from the highest available ESM flagged plugin at the time of LOD generation. For the DynDOLOD.esp the highest available non-ESM flagged plugin is used. So if there is any problem with such data in either DynDOLOD plugin, it is because of the data that was copied from existing plugins. It would be best to run the script before generating LOD / the DynDOLOD plugins, but it will work just as well to to update the CELL records in the DynDOLOD plugins or whatever plugin is the last overwrite for the CELL.
  15. sheson
    I know it is easy to miss the instructions printed in the error, but can you please post the entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt
  16. sheson
    https://www.virustotal.com/en/file/cd88fd5d8ec4b122382b79519bb97070026395610e8e1ed79206a454265a4220/analysis/1541550990/
  17. sheson
    Thanks for reporting. That's not LOD though, but copies from references in the child Markarth to the parent world Tamriel that do need to be copied. Such copies use the LOD model for the loaded cells. You can just disable them in game or remove the references from the plugin. To not have them added when generating LOD add the lines Skyrim.esm;0010E456;MrkCityIntCWwall01Skyrim.esm;0010E457;MrkCityIntCWwall02Skyrim.esm;0010E458;MrkCityIntCWwall03 to DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[TES5|SSE]_childworldlod_Tamriel.txt. That update will be included in the next version.
  18. sheson
    FAQ: DynDOLOD.exe: Exception in unit xxx line xxx: Can not copy xxxx from xxxx.esp into xxx.esp A: Often caused by a broken bashed patch. Use a newer Wrye Bash version to create the patch or do not use the merge patches option. A: There might be plugin in the load order with errors. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help.
  19. sheson
    That's great to read. Thanks for letting us know.
  20. sheson
    Old scripts and data remnants would cause all kinds of weird problems. Glad you found it.
  21. sheson
    I am going assume the message is: "DynDOLOD requires DynDOLOD plugins version 2.44". If that is not the message then you will have to reproduce the exact message and circumstance in a more qualified error report. A: Either the plugins were generated with an older standalone version or the papyrus scripts from DynDOLOD Resources / DynDOLOD DLL are the wrong version. A: Make sure to generate LOD with DynDOLOD standalone version that has matching or higher version than DynDOLOD Resources / DynDOLOD DLL. Do not use DynDOLOD Resources / DynDOLOD DLL with higher version than version of DynDOLOD standalone. A: Make sure the DynDOLOD Resources / DynDOLOD DLL version is high enough for the DynDOLOD standalone that is being used. For example plugins generated with DynDOLOD standalone 2.45 require DynDOLOD Resources 2.45 / DynDOLOD DLL 2.45 The papyrus scripts in the load order are version 2.44. You need to update them if you generated with DynDOLOD Standalone 2.45 or higher. If this happens with an existing save game but not with a new game, then make sure to follow the update procedure as explained in the manual.
  22. sheson
    Generating LOD for Skyrim broke in 2.46 with the changes made for Skryim SE/VR, now it works again. If the problem happens with a new game (also try coc whiterun from main menu, then save ... load) there seems no much use doing any tests with old saves. Check Papyrus log. Use debug mode anyways to see how far it gets even. I would straight go into troubleshooting mode and see if the same thing happens with new game and using DynDOLOD DLL / Papyrus Util. Then disable DynDOLOD.esp and if it works, go right ahead with removing references / data from it in a 50:50 fashion until only the data causing the problem is left.
  23. sheson
    Started a new game, ran to western watchtower, saved, loaded without problem. DId it twice, once with DynDOLOD DLL and then PapyrusUtil. Both worked. The only thing that happens when loading an interior cell is a something the MCM script and the Quest script running. The Quest scripts prints out a few lines to papyrus log. The lines from DynDOLOD Quest you should see with PapyrusUtil are something like [11/07/2018 - 01:29:57AM] [sHESON_DynDOLOD_Quest ] Load DynDOLOD_Worlds.json TRUE [11/07/2018 - 01:29:58AM] [sHESON_DynDOLOD_Quest ] Load DynDOLOD_Tamriel.json TRUE or FALSE if in interior[11/07/2018 - 01:29:58AM] [sHESON_DynDOLOD_Quest ] Load DynDOLOD_Tamriel_Objects.json TRUE or FALSE if in interior[11/07/2018 - 01:29:59AM] [sHESON_DynDOLOD_Quest ] Assigning INI values 2.700000 The changelog is were it always is: bottom of first posts and in the standalone archive docs folder.
  24. sheson
    Then I suggest to follow the FAQ / readme to troubleshoot CTD for invalid nif. Edit: If debug method does not reveal anything, do the 50:50 removal of references - typically only needed in DynDOLOD.esp and do not remove DynDOLOD_[Master|Firstborn|Minion]Activator
  25. sheson
    What happens with new game, like coc whiterun from main menu?
×
×
  • Create New...

Important Information

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

  I accept