sheson
-
Posts
11,236 -
Joined
-
Last visited
-
Days Won
347
7 Followers
sheson's Achievements
-
If it runs through now, then it is hard to pinpoint a specific reason. As I suggested in an earlier post, check memory usage of DynDOLOD in Windows task manager and check if it has sub processes like LODGenx64.exe or Texconvx64.exe that might be using lots of memory. The task manager can show both main and video memory usage. When you have to generate again in the future, see the answers for https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory first to test different settings and without enabling the real time log, in particular: If DynDOLOD runs out of memory while generating atlas textures, add a line TextureCache=10 to ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI. If there are still problems, set MaxTextureSize=8192 in the same INI file. If too many concurrent LODGen processes running at the same time consume all available memory, limit their total number by changing the MaxLODGen setting in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI. So next time, try setting TextureCache=10 and MaxLODGen=2 to see if it makes a difference.
-
Upload a crash log from Crash Logger. No crash logs were provided. If it doesn't crash anymore, then that's great and I do not need crash logs anymore.
-
We do not really need users to tell us about game updates or changes. ElminsterAU just pushed the upate to the xEdit github like 5 minutes ago.
-
The DynDOLOD log and debug are the same as from this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-169/?do=findComment&comment=278595 which show that LOD billboards were not found and then no LOD generation was started. Check the dates and content of the log files are the ones from the last generation. The DynDOLOD_SSE.ini shows that ; RealTimeLog=1 is commented out. Remove the semicolon and any spaces in order to have the setting take effect.
-
This archive does not seem to contain a DynDOLOD_SSE_realtime_log.txt or a new DynDOLOD log and debug log.
-
Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. Whatever ever it is you are doing, this is not how modding or usingxEdit, xLODGen, TexGen or DynDOLOD work at all. They load plugins like the game does. There is no need to rename plugins. Renaming plugins is going to result in issues. Use a mod manager. Install these tools properly and start them from the mod manager. See https://dyndolod.info/Installation-Instructions See https://dyndolod.info/Generation-Instructions how to run TexGen and DynDOLOD. Notice that there are no instructions to rename any plugins but it says to finalize the load order. Do not invent unnecessary steps. Report the actual problem instead. Replacing plugins with another means, that whatever the replaced did, will be missing from the load order at generation time and plugin requiring it as a master will have unresolved form ID errors. LOD is made for the load order at generation time, if the load order changes afterwards, then LOD might not match or work correctly. See https://dyndolod.info/Help/Ultra-Tree-LOD how to generate 3D tree LOD. Under Requirements is says: Skyrim 3D Trees and Plants - Install Skyrim3DTrees and Plants 3dLOD Resources. There is no need to rename 3D tree LOD model files. DynDOLOD automatically falls back to the standard object LOD filename convention. I suggest to to learn basic modding practice by following a modding guide.
-
Still no DynDOLOD log or debug, which are saved, when you close DynDOLOD via clicking X top right. Only kill it via task manager if closing via X top right does not work for a minute. In that case, edit ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini with notepad and add RealTimeLog=1 under [DynDOLOD] at the top. Then start DynDOLOD. Once it shows the options window, check the ..\DynDOLOD\Logs\ folder that DynDOLOD_SSE_realtime_log.txt is being created. Upload the realtime log. If there is no realtime log, reboot and try again. If it still does not work, upload your version of DynDOLOD_SSE.ini. With the log we have a good chance to troubleshoot this more quickly.
-
No crash logs were provided. Without generating and installing DynDOLOD output there are obviously no data files in the game data folder for the DLL to load. Could you test if there is anything different with DynDOLOD DLL NG and Scripts Alpha-18 that uses the "old" commonlibsse-ng? You can get it from https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds
-
https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD Ignore wrong 3rd party advice to temporarily disable plugins, mods, meshes or textures. Such advice is categorically wrong or outdated. In case of issues, solve the cause or use appropriate mesh mask rules or settings for desired results. One main purpose of LOD generation is to improve the performance (by reducing resource usage), which includes generating object LOD or dynamic LOD for lazily IsFullLOD flagged full models. If the replacement with automatically created (HD) tree LOD billboards has no good visual results, a proper 3D LOD assets should be created as is being practiced by or for most tree mods since years. https://dyndolod.info/Help/3D-Tree-LOD-Model It is also possible to use mesh mask rules to either use the full model for object LOD and/or dynamic LOD or to do nothing to a reference (keep things as they are). https://dyndolod.info/Help/Mesh-Mask-Reference-Rules Mod authors can include proper LOD assets and/or mesh mask rules in their mod so things work automatically for users as intended and practiced since a decade https://dyndolod.info/Mod-Authors If help is needed with creating LOD assets or mesh mask rules to achieve the desired results, then provide a link to the mod and if possible useful screenshots as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots LOD assets and mesh mask rules can also be included with future releases of DynDOLOD.
-
Read the actual error message and click on the "Click on this link for additional explanations and help for this message" as explained on the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages. That should open https://dyndolod.info/Help/Tree-Grass-LOD-Billboards, scroll down to "LOD Billboard(s) Not Found". Based on the logs I can see TexGen generated those billboards and it completed successfully. So, the TexGen output or parts of it are probably not installed (virtually) in the data folder C:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\Data\ that DynDOLOD looks at. The game is installed into C:\Program Files (x86)\ which can cause issue with UAC or antivir. Follow a modding guide, that explains how to install the game properly outside of C:\Program Files (x86)
-
Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD debug log to also upload. Is it always reporting the same image textures\architecture\windhelm\whwindowmaps.dds? Memory does seem lowish at the time since there on seems to be 8GB main memory. Double check overall usage in task manager. Maybe one of the tips from https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory can help to reduce how much is used at the time.
-
Read https://dyndolod.info/Mods/Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG Do not link to files or folders in mod manager profiles. Link to the files and folders used by the game. Make sure folders end in slash \. Make sure the paths to folders or files are enclosed in double quotes " Do not link to MO2 profile folders. Link to the actual paths or files the game uses. This works if the commands line arguments are set correctly. There is not need to set the save folder with -g for TexGen or DynDOLOD. If there are still problems, copy and paste the actual line from the arguments field in MO2 without editing it.
-
Moved to the DynDOLOD DLL thread. Upload a crash log from Crash Logger. Upload c:\Users\[USERNAME]\Documents\My Games\[Skyrim Special Edition|Skyrim VR]\SKSE\DynDOLOD.log Use a file upload service or text sharing service as explained in my signature or at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Nothing from DynDOLOD needs to be installed while generating grass cache. I can generate grass cache with NGIO NG 1.0.11 and DynDOLOD DLLB NG 3.0.22.1130+ without issue. Are there any issues starting the game normally with DynDOLOD DLL NG and with or without DynDOLOD output?
-
Thanks. Will be fixed in the next version of DynDOLOD Resources.
-
Still not DynDOLOD log or debug, which are written, when you close DynDOLOD via clicking X top right. Only kill it via task manager if that closing does not work for a minute. In that case, edit ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini with notepad and add RealTimeLog=1 under [DynDOLOD] at the top. Then start DynDOLOD. Once it shows the options window, check the ..\DynDOLOD\Logs\ folder that DynDOLOD_SSE_realtime_log.txt is being created. If that does not work, reboot and try again. If it still does not work, upload your version of DynDOLOD_SSE.ini. With the log we have a good chance to troubleshoot this more quickly. I assume high memory usage means that DynDOLODx64.exe shows high memory usage in task manager? Check if it has sub processes like LODGenx64.exe or Texconvx64.exe that might be using lots of memory.
