Jump to content


Mod Author
  • Content Count

  • Joined

  • Last visited

  • Days Won


sheson last won the day on September 27

sheson had the most liked content!

Community Reputation

715 Phenomenal


About sheson

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Some of it looks like z-fighting between object LOD and object LOD or maybe terrain LOD. Are the trees affected or not? If there is ultra tree LOD set standard tree LOD to zero. Some of it looks like almost like there is something going on with the snow LOD shaders. https://dyndolod.info/Help/Snow-Ash-LOD-Shader, check what overwrites those records. Test without DynDOLOD plugins to make sure it has nothing to do with dynamic LOD and this the large ref workarounds. Large ref workarounds can only work in the uLargeRefLODGridSize. Test with default INIs. Make sure no custom INI or [plugin].ini in data folder either. Test without the water (falls) mod that has controller blocks in LOD models (the block itself is not causing the issue as it is ignored, but it means somebody made bad static object LOD models). Which version of Water for ENB is it? https://dyndolod.info/Mods/Waterfalls (meshes in DynDOLOD Resources for these mods have the full model CRC32 in their filename) Do you use other full models for LOD. Especially ones with BSEffectShaderProperty. Some shader settings/flags can cause wierd effects. The last few seconds of the video shows switch between LOD levels.
  2. Now what are the actual questions in addition to the explanations from https://dyndolod.info/Messages/Property-Not-Found-In-Scripts or https://dyndolod.info/Messages/File-Not-Found-Meshes? Install the latest version of mods. For example it looks like Serana Dialog add on just had an update today. Maybe the missing property was fixed in case it was an actual problem. In case of Pilgrim checking the https://www.nexusmods.com/skyrimspecialedition/mods/54099?tab=bugs it seems that the 2 meshes are not used. You checked if all BTOs are valid? I am pretty sure they would cause CTD in game in case that error goes through unnoticed. That tree is not used that often, so check where it is positioned to find the filename for the bto to see if it opens in NifSkope without error. What makes debugging this not take some time is that it takes ages to let it do the reuv to see what is happening.
  3. Read the first post which log and debug log to upload when making posts. See https://dyndolod.info/Messages and/or https://dyndolod.info/Help/Summary-Of-Messages for explanations about messages, their severeness and possible (often optional) solutions (obviously only brief/generic and non exhaustive ). If further help is required ask specific questions and provide the log/debug log files.
  4. It reported this in the log [00:04] <Error: File not found textures\DLC03\Architecture\PierShacksSiding03TwoWideRed_s.dds. Used by textures\DLC03\Architecture\PierShacksSiding03TwoWideRed_d.dds> The textures were copied fine to the new _s name, it just didn't look for them in the temp location, only in data. I also made it so that temp textures use uncompressed formats so texconv doesn't complain about multiple of 4 This version should do the trick https://mega.nz/file/dAp1CDLS#tf55DHqIv8p6N5pjilTyVtY9fqbyk7UDtZ5a7O--3E4 See https://dyndolod.info/Changelog to see what changed between versions. >I'm not sure if something has changed You are changing settings. This is what changes. In your last post you said you set uLockedObjectMapLOD=8. Which means the map is obviously not using object LOD Level 32. https://dyndolod.info/Help/Ultra-Tree-LOD#Trees-on-the-Map
  5. The NIF is fine, it just that something falls apart when it tries to re-uv the trunk.
  6. The reason the first post does not say anything about posting screenshots of the the tools/settings because the debug log includes the settings. This thread is for testing and reporting about DynDOLOD 3 Alpha. No reason to post about xLODGen terrain LOD here. Nothing changed how DynDOLOD Alpha 99 generates LOD in comparison to the versions before. Read the changelog https://dyndolod.info/Changelog If something drastically changed/broke in DynDOLOD causing visual issues like in the video, people would already have posted about this. Changing resolutions in DynDOLOD does not change how the game works - loads/unloads LOD. Read "Object LOD shows in active exterior cells" at https://dyndolod.info/FAQ, It was already suggested to check the INIs for the uLockedObjectMapLOD setting.
  7. Read https://dyndolod.info/Help/Seasons#Grass-and-Grass-LOD and https://dyndolod.info/Help/Grass-LOD#No-Grass-LOD-Check-List There should 5 sets of grass cache, the default cache and the cache files for the 4 seasons.
  8. So far I have isolated it to this model jbtreepineforest05.nif - that's the first that triggered the exception anyways. The NIF is fine, it just that something falls apart when it tries to re-uv the trunk. That thing is way too complex for that (more triangle than the leafs) but not enough to be skipped. Still should not have any exception. It may not always CTD. In that case it might produce broken BTO. For general LOD generation I strongly recommend optimized 3D tree LOD models... just saying.
  9. Yes, but it most likely will only produce a diffuse and normal and not the specular textures. I will add that to the next version. 0 1 1 1 textures\input.dds r 270 0 0 DynDOLOD-temp\textures\outputrotated.dds 1 1 270 is the angle, use between 0 and 360 Then use the output as input for the stitched ... 0 1 1 1 DynDOLOD-temp\textures\outputrotated.dds 0.5 0.25 0 0.75 textures\awesome_lod.dds 1 1 ... Edit: Use this test version which should also do _s.dds https://mega.nz/file/xNwUUDBT#EQhIRLCeUtbbQtDhLQDdzmzQEaPYyRw-82EAE9m23Ac
  10. Read https://dyndolod.info/Changelog to see what changed between versions. There is no change how object LOD meshes and textures are generated. You determined that this is a problem with with a save file that has nothing to do with the DynDOLOD plugins. If I remember correctly you reported that the game shows object LOD fine with a new game or without other mods. The object LOD meshes and textures do not affect save files. They are just models the game engine loads at specific positions based on INI settings. LOD generation does not care about save files or the INI settings. I would would narrow done involved mods/plugins, check INI settings, check papyrus logs and maybe look into the save. All without any DynDOLOD/Occlusion plugins, since you reported they are irrelevant and narrowing down mods/plugins is about only keep the stuff in the load order that contributes to the problem.
  11. I get the same crash with the your files so I am able to debug this next days and see whats up. Also have 8GB peak, that nothing. At the time of crash it's 3GB.
  12. Oh boy "tree" full for LOD4. This going to take a while ... Any indication how much memory the LODGen process peaks at when you run that with grass LOD as well?
  13. Thanks for this. This constellation should properly try to fix in both (all) affected cells in the next versions. The moved large reference check did not see did see this as moved because the master record and the last overwrite both have the same position.
  14. Clean all plugins that contain deleted references. https://dyndolod.info/Generation-Instructions#Prerequisites Finalize the load order. Install mods and their requirements. Sort and resolve conflicts. Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean - ignore misinformation that cleaning any plugins is not needed or causes problems. The Batch Plugin Cleaner for Mod Organizer or the xEdit Cleaning Extension for Vortex help to automate some of that. https://dyndolod.info/Messages/Deleted-Reference That should fix that issue.
  15. Bring up the reference 000DDD36 in xEdit and check the last plugin / column to the right. There might be something going on with the EditorID having weird characters. Let me know what you find.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.