-
Posts
13,181 -
Joined
-
Last visited
-
Days Won
431
Everything posted by sheson
-
From the log: Error: Could not execute "Z:\mnt\nvme0n1p3\skyrimmodlists\STEP\Tools\xLODGen\Edit Scripts\Texconvx64.exe" -nologo -y -m 1 -sepalpha -aw 256 -srgb -f R8G8B8A8_UNORM -w 8 -h 8 -o "C:\users\steamuser\Temp\SSEEdit" "C:\users\steamuser\Temp\SSEEdit\39F9011240394BBAA77C9EFA8D9F385F.dds"> <Error creating textures for cell [-14,32] Could not create alpha layer with LDirtPath01 [LTEX:000B424C] (Textures\Landscape\DirtPath01.dds, Textures\Landscape\DirtPath01_N.dds) for [LAND:00004DAA]: A call to an OS function failed>. Error converting textures: A call to an OS function failed Search the forum for the error message finds this relevant thread: https://stepmodifications.org/forum/topic/19354-linuxproton-a-call-to-an-os-function-failed/ Check that thread. The hover hints for Bake normal-maps explains: Bake blended normal-maps of landscape textures onto terrain model-space normals. Automatically applied to all LOD levels.
-
Replace TexGenx64.exe/DynDOLODx64.exe with this version https://mega.nz/file/RIpyBSTI#syE9VR5Go08P11mVunPgabmWJQk7l7jBpMz-ENUxDt4 That should hopefully run through.
- 165 replies
-
Also upload bugreport.txt. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
- 165 replies
-
Also upload bugreport.txt and the normal TexGen log. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Did you change the load order or is the texture random?
- 165 replies
-
Also upload bugreport.txt and the normal TexGen log. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
- 165 replies
-
Just press ESC to continue.
- 165 replies
-
Test version of TexGen/DynDOLOD https://mega.nz/file/hNJ2ULbB#CUl8Eu_8TzRwZWj7x31SqMgwQ-BwMR8JwawWRyevKJ added sRGB to linear conversion to (hopefully) all texture paths OpenGL shader gamma value set with sRGBGamma in TexGen/DynDOLOD INIs use specular channel from _rmaos.dds for rendered textures, todo for stitched added the texture set automatic replacements that were missing
- 165 replies
-
Moved to the appropriate thread for the message. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search Messages state facts. The mentioned plugins need to be cleaned because they contain deleted references. Make sure the cleaned plugins are installed, active, deployed and overwriting the vanilla plugins with their same name filenames. Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when mkaing posts. Read the message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages If there is an error prompt, read the entire message carefully. Many of them describe the problem in detail and offer hints for for a solution. Click the Click on this link for additional explanations and help for this message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open further help: Every plugin containing deleted references needs to be cleaned. See the Prerequisites section of the Generation Instructions for more. https://dyndolod.info/Generation-Instructions#Prerequisites Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean - ... Cleaning of plugins that contain deleted large references is mandatory for the DynDOLOD DLL NG that includes the large reference bugs workarounds. See https://tes5edit.github.io/docs/7-mod-cleaning-and-error-checking.html
-
Moved to the appropriate thread for the message. See above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search Read and follow the actual instructions at https://dyndolod.info/Generation-Instructions#1-Generate-The-Required-LOD-Assets-with-TexGen and watch the embedded video below them. Install the contents of the output path or the *.zip archive as a mod. It should overwrite everything. Consider moving the zip archive to the mod managers download folder for later re-use. Do not forget to deploy. The message window should have a link Click on this link for additional explanations and help for this message that open https://dyndolod.info/Messages/TexGen-Output as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search#Read-Log-and-Error-Messages. Scroll down to the section No TexGen output detected and read everything and go through the check list. If problem persists, read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD logs and debug logs to upload.
-
xLODGen terrain LOD beta 117 should now convert sRGB textures to linear. It is using Texconv for that which is hardcoded to 2.2. In case that is not good enough we can check for alternative methods or adding an option to Texconv. Post screenshots of terrain LOD in that case.
- 165 replies
-
See https://dyndolod.info/Messages/File-Not-Found-Textures dlc1treewinteraspensnow01_4eaf2dff_trunk.nif ships with Happy Little Trees Add-On - DynDOLOD 3. It requires Happy Little Trees to be installed. landscape\trees\northern hemispheres\aspenbark.dds ships with Happy Little Trees. Make sure the mod with all its assets is installed. The texture needs to be installed, so the trunk for the LOD assets using them can be rendered. Do not modify the LOD assets included Happy Little Trees Add-On - DynDOLOD 3. For future reference see https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs You can not link local files, you would need to upload them.
- 165 replies
-
See https://dyndolod.info/FAQ#Entire-LOD-missing Can be caused by [MapMenu] uLockedObjectMapLOD=32 in Skyrim.ini (or SkyrimCustom.INI or a mod INI), especially if there are no object LOD level 32 meshes (which is the vanilla/default). See Trees on the Map for further explanations. You have a clear map overhaul. You probably installed the option which requires LOD Level 32 object LOD meshes for the map. Level32=1 was not set C:\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini Follow the instructions of the mod or set uLockedObjectMapLOD=16
-
Moved to the post to the appropriate thread. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search See answers above. Read the message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages If there is an error prompt, read the entire message carefully. Many of them describe the problem in detail and offer hints for for a solution. The fix that is part of the message you posted. The mentioned plugins need to be cleaned. Click the Click on this link for additional explanations and help for this message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open further help. Every plugin containing deleted references needs to be cleaned. See the Prerequisites section of the Generation Instructions for more. https://dyndolod.info/Generation-Instructions#Prerequisites Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean - ... Cleaning of plugins that contain deleted large references is mandatory for the DynDOLOD DLL NG that includes the large reference bugs workarounds. See https://tes5edit.github.io/docs/7-mod-cleaning-and-error-checking.html
-
Will be fixed next Alpha version I am going to release shortly.
-
The file service linked in the explanations and in my signature does not require a registration. You also seem to have ignored my suggestion to verify LOD distances in the MCM. Post a screenshot of it. Also post a screenshot of whatever issue you have in the game. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots Since Alpha-179 was just posted like 2 hours ago, it seems likely the generation taking 6 or 4 hours was with an older version. https://dyndolod.info/Changelog Version 3.00 Alpha 179 DynDOLODx64.exe - fixed sometimes spending a long time testing for manual statics config files
-
Upload the SSELODGen_log.txt What do you believe updating DynDOLOD or DynDOLOD Resources have to with xLODGen and terrain LOD generation in particular? Generate terrain LOD before running TexGen and DynDOLOD. Make sure to use the latest xLODGen terrain LOD beta version linked from first post. Error check the load order with xEdit.
-
https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts. Zip and upload large log files to a file service as explained. See https://dyndolod.info/FAQ#Long-running-time-or-output-several-GB-in-file-size Check LOD distances and their explanations in https://dyndolod.info/Help/Mod-Configuration-Menu-NG#Settings All initial values for object, tree and terrain LOD are defined in SkyrimPrefs.INI. See all answers for https://dyndolod.info/FAQ#Entire-LOD-missing.
-
Please test with Alpha-179 that object LOD is matching better now. If there are issues, post screenshot of LOD and full model with more informative console information showing and upload the TexGen/DynDOLOD log and debug log. It is possible that texture-set replacements may not yet be recognized properly. Still testing. I'll look into updating xLODGen support next.
- 165 replies
-
That's great! Thanks for letting us know.
-
Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD debug log to also upload when making posts. Do not wait 8 hours... when there is obviously a problem. https://dyndolod.info/Official-DynDOLOD-Support-Forum If it takes time to first gather information, logs etc. it is fine to just take it and then post when ready.
-
That's great! Thanks for letting us know.
-
There are no fatal ITM warnings in DynDOLOD whatsoever. DynDOLOD does not check or cares for ITMs in 3rd party plugins. https://dyndolod.info/Generation-Instructions#Prerequisites 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, does not do anything or causes problems. Cleaning of plugins that contain deleted large references is mandatory for the DynDOLOD DLL NG that includes the large reference bugs workarounds. ITMs are irrelevant in this context, see There are no intentional ITMs. Cleaning dirty plugins is a rudimentary modding step to build a properly working load order since decades. Cleaning dirty plugins is a requirement of DynDOLOD since a decade. The large reference bugs workarounds now really require deleted large references to be undeleted. LOD patch generation is not possible otherwise, the process will eventually stop with an error message. Cleaning ITMs from vanilla DLC while undeleting deleted references is not going to affect the game. If you believe there is a problem with removing ITMs from the vanilla DLC or the cleaning process, then you should report to and discuss that with the xEdit devs. Nobody forces you to use DynDOLOD. However, do not blame anything/anybody else for the consequences of your choices.
-
You will not need to do anything about that right now, if ever. For now I will have this for the next alpha release for you to test: The tools now support using signed DXT1 (BC1), DXT3 (BC2), DXT5 (BC3) textures. BC7 signed was already supported, in case there was a bug that caused them to have wrong brightness, it should be resolved. ATM, there is no additional brightness changes. The textures will look the same as the game shows the sRGB textures natively without community shaders. TexGen will automatically generate pbr versions for stitched and rendered object LOD textures if any of the used full textures have a pbr version. Since billboards are rendered from full models there should be nothing else needed to be done. DynDOLOD will automatically use the pbr textures for the LOD models in case the full model uses pbr textures. DynDOLOD should also properly create any of the on-demand pbr versions for texture sets. Will have too see if we can do something automatic about 3D tree LOD assets.
- 165 replies
-
Thanks. Delete old logs, then run this test version https://mega.nz/file/VVISVLwZ#BUNV8tCRdhURTDrThZWpePgGxACYOHivoCkBV8SYC9k Upload new logs if the issue persists.
-
It was moved to the appropriate thread. Check your post history.

