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
    It is a replacement for PapyrusUtil specifically for what DynDOLOD needs in game. No more no less. The main reason was the lack of PapyrusUtilVR and be independent in case of game updates. Starting with version 2.45 there is now the alternative DynDOLOD DLL available for testing. You will have to test to find out if one or the other works better for your load order. Realistically performance should be the same, but the scripting works a bit differently. I really can't say if one is significantly better than the other.
  2. sheson
    Was this load order with the exact same mods working fine? So what exactly changed? New mod or new DynDOLOD? If new DynDOLOD, which versions did you use before/after - also of DynDOLOD Resources? Are you generating traditional tree LOD or ultra trees LOD? Trees anywhere else are fine? Low, high, Medium? Use tfc or tcl to get a better picture of the problem. Do they change to correct trees when getting closer?
  3. sheson
    DynDOLOD likes plugins just fine as long as the plugins are valid and do not contain errors. OPs problem was most likely a broken Bashed Patch, caused by old versions of Wrye Bash - just as the DynDOLOD FAQ mentions, based on countless troubleshooting posts here. Disabling plugins is a troubleshooting step. If it helps, it most likely means the plugin has a problem. Of course it is also possible there is an issue or constellation that xEdit/DynDOLOD does not know how to deal with properly.
  4. sheson
    It really doesn't fix whatever happens with the SKE string or getmod description functions. I just added a backup method in case they fail. I hate doing that instead of fixing the cause. However, since I currently have no equipment to check myself and VR users are out of firstborns and the problem seems to be with SKSE I figured sooner or later it will show up somewhere else and someone else will have to look into it eventually anyways.
  5. sheson
    No worries. Enjoy.
  6. sheson
    You are welcome.
  7. sheson
    The program checks if its file name is TexGen.exe or TexGenx64.exe, then will it run the TexGen mode. Otherwise it will run in DynDOLOD mode.
  8. sheson
    Fixed. Thanks for letting me know.
  9. sheson
    Those red exclamation marks are missing meshes. Those seem to be unrelated to LOD. Get the MfgConsole plugin, then open console, click on them to get the base form id. Its first two digits are the hex load order of the plugin that adds them. That should help to find out what mods needs to be reinstalled or looked into.
  10. sheson
    xLODGen Beta 40 updates Enderal to use new launcher registry path and fixes holes caused by coarse quality in conjunction with protect cell borders.
  11. sheson
    Black textures could be a sign for running out of video memory. Make sure to use Crash Fixes with UseOSAllocators=1 and ENBoost is setup properly. Check VRAM usage with an appropriate tool for your graphics card or Skyrim Performance Monitor. The ENB overlay can also show VRAM usage. 3D tree LOD is demanding. Make sure not to use full model fallback. Try setting lower distances in the launcher or the DynDOLOD SkyUI Settings page. You could try manually shrinking the atlas textures created in Textures\DynDOLOD\LOD\*.dds to half their size. If all that seems fine, maybe post a screenshot, since it possible it is something else.
  12. sheson
    Thanks. I will see if I can replicate and do something about it.
  13. sheson
    [00:00:04.605] [00:04] Background Loader: [Mutilator.esp] File loaded (CRC32:451C3EA4)[00:00:04.605] [00:04] Background Loader: Error: record TES4 contains unexpected (or out of order) subrecord DATA 41544144[00:00:04.605] [00:04] Background Loader: Errors were found in: [TES4:00000000] You may want to error check Mutilator.esp in xEdit and fix all errors. The exception later is when it creates the texture atlasses. It probably runs out of memory. Try using the x64 version.
  14. sheson
    Thanks. Have you tried if it runs through using the 2048 setting with the x64 version?
  15. sheson
    Good to know. Enjoy.
  16. sheson
    I am sure you can comprehend the difference between the term "seeing fine " and "it is fine", no matter what your mother language is. Try a different quality setting see if it changes anything.
  17. sheson
    Test what happens if you use the x64 version instead. It might run out of memory.
  18. sheson
    If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_Enderal_log.txt to official forum
  19. sheson
    Read the rest of the messages after the error. Then do what it suggests.
  20. sheson
    The DynDOLOD FAQ has an entry for this message from the xEdit plugin loader: FAQ: TexGen.exe/DynDOLOD.exe: A: ESL plugins can only add new records with form IDs between xxxxx800 and xxxxxFFF, but the plugin defines a form id outside these limits. See https://www.afkmods.com/index.php?/topic/5079-plugin-files-and-you-esmeslesp/. The plugin needs to be fixed. Broken plugins cause issues in the game. The best option is to change the form id of the record. However, it might be not as easy as that as other things might rely on the form id. Refer to the author of the plugin.
  21. sheson
    I can see perfectly fine, however you are not giving any useful information whatsoever. As far as I remember there never has been ever a report like this. Obviously you already checked if this problem is known or not. This typically means that there is something that nobody else has encountered before. So, everyone else generates these meshes without such error. I am out of glass balls and can not magically create unique issues in the load order or tools just by looking at some random screenshots. Common sense and basic courtesy would be to give as much information as possible so people can reproduce this error only you have come across so far. For example: Are these meshes actually generated by LODGen and if so, which version? Check the NIFs header info. Does it happen with the latest version? What version of xLODGen was used. Does it happen with the latest version? Were there any error or warning messages from xLODGen or LODGen. Post the log. What settings were used in xLODGen. A screenshot of the options would suffice. Which Skyrim version, DLCs, plugins cleaned or not, which other plugins from mods are in the load order.
  22. sheson
    The message log is the message window were all the messages are printed, including "An error occured while loading modules. Editing is disabled. Check the message log and correct the error." So simply check the message log lines above the error message for the error. The message log will be saved to a log file in DynDOLOD\Logs\ when the program is closed.
  23. sheson
    I am not sure would the problem is supposed to be? The path c:\Users\[username]\Documents\My Games\Skyrim Special Edition\Skyrim.ini is what the game and every tool uses. If everything is setup correctly, MO maps profile specific INIs to that path when the game or the tools are started from MO.
  24. sheson
    Please upload the bugreport.txt and DynDOLOD_SSE_log.txt from 2.55 if you have an error.
  25. sheson
    The current English Steam version of Enderal has the same terrain LOD meshes and textures as the "old" version, so yes, but: Optionally install the higher resolution and improved terrain LOD meshes and textures for Vyn and Half Moon Island from DynDLOD Patches. They are not required. They were made with Oscape a while ago. Consider using xLODGen terrain LOD beta to generate even better terrain LOD meshes and textures. The terrain meshes will benefit a lot from using xLODGen with the Protect Cell Border setting. The Oscape ones I did years ago suffer quite a lot from the unsightly drops at cell borders. Back then I also did some manual optimization with the higher LOD levels, so maybe only do LOD Level 4 meshes. I will probably update the patch myself at some time, but no promises.
×
×
  • Create New...

Important Information

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

  I accept