sheson

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log, debug log and bugreport.txt to upload when making posts. https://dyndolod.info/Help/Texconv 80070020 - The file can not be read or written to. Another process or thread is blocking access. If closing all DynDOLODx64.exe/Texconvx64.exe in task manager and then restarting MO2 afterwards does not help, try rebooting Windows to clear it up.

https://dyndolod.info/Generation-Instructions#Prerequisites Finalize the load order. Clean every plugin that LOOT suggests to clean Watch this video The Batch Plugin Cleaner for Mod Organizer or the xEdit Cleaning Extension for Vortex help to automate some of that. Despite expecting users to have rudimentary modding knowledge as explained on https://dyndolod.info, the basics of cleaning are explained/linked, also with a video and additional tools in the prerequisites of the generation instructions. The LOOT tool listing plugins that need cleaning exists longer than DynDOLOD and is explained in every decent modding guide. Refer to its linked manual. The linked GamerPoets video also explains that LOOT lists plugins that need to be cleaned at timestamp 1:14 Additional tools are linked to help speed up the process. If you only started to clean dirty plugins because tools like DynDOLOD require it in order to work, then I suggest to learn the basics of modding by following a decent modding guide.

Since you want to combine LOD from BSHeartland, you will need to uncomment that worldspace in DynDOLOD_SSE_worldspace_ignore.txt. I also uploaded a new test version, that does not require this edit for combining, so give this a test and report results.

Cleaning is done after installing the patch. I have been using this patch with cleaned DLCs for a couple years for testing DynDOLOD DLL NG and Scripts. If you believe cleaning plugins causes issues, then get the latest xEdit version and if troubleshoot/report your issue to the xEdit Discord. Recent mods require the latest Skyrim SE/AE game plugins, so following a modern modding guide is suggested: https://dyndolod.info/Mods/Skyrim-VR It is suggested to refer to modding guides how to setup the base game properly. For example, the Skyrim Initial Setup (VR) guide also has explanations how to use the latest Skyrim SE or Skyrim AE game files and the latest Unofficial Skyrim Special Edition Patch for best compatibility with the latest mods.

Moved to the DynDOLOD Alpha thread. The DynDOLOD log seems to ask for a login. The bugreport.txt and the debug log can be accessed OK. Upload any ..\LODSettings\LODGen\*_Combine.ini files found in the data folder. Check with MO2 right window data tab and archive parsing enabled. If there are none, then report that. Download the latest test version from https://dyndolod.info/Downloads/Test-Version. Delete all old logs and bugreport.txt. Then run the test version. It should run through. Upload new DynDOLOD log and debug log.

Moved to the DynDOLOD 3 Alpha thread. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. Use the Copy message to clipboard link to copy/paste the error as text instead of posting a screenshot as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Error: Expected value but found "]" (5,4) https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search: https://stepmodifications.org/forum/search/?q="Error: Expected value but found"&quick=1&type=forums_topic&item=21292 finds similar error message https://stepmodifications.org/forum/topic/19903-dyndolod-300-alpha-198/page/716/#comment-288542 and this solution https://stepmodifications.org/forum/topic/19903-dyndolod-300-alpha-198/page/716/#comment-288542

Install DynDOLOD DLL NG and Scripts instead and make sure it is not being overwritten by anything. Generate anew LOD patch from scratch. See https://dyndolod.info/Downloads, https://dyndolod.info/Installation-Instructions and https://dyndolod.info/Generation-Instructions. If the problem persists upload new logs.

Thanks for letting us know. The change is part of the new alpha version.

Thanks. Get the latest test version of DynDOLODx64.exe from https://dyndolod.info/Downloads/Test-Versions Delete old logs and then run again without GLDebug=1 to see if there is any change. Upload new log, debug log and bugreport.txt if it exists.

It is unclear what guide the thread title refers to. If you have a problem following a third party guide (like STEP for example), you need to ask on their forum (section) or discord about that particular issue. https://dyndolod.info/Official-DynDOLOD-Support-Forum Report the actual problem or error message without making unverified assumptions or asking leading questions. Read the explanations and tips below, especially about what information and logs to provide and how. I suggest to really read the entire error message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages and click its links to further help and information about the reported problem. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text When having done so, point to the exact words or phrase that make you believe you are being scolded and what makes you believe it refers to Solitaire as being problematic. Once having read the actual message, see https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs. Post the DynDOLOD log and debug log as explained. MS did indeed recently change and rename the latest Visual C++ Redistributable download. Simply install the "Latest supported redistributable version" x64 https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-supported-redistributable-version. As explained on https://dyndolod.info/Downloads, the Visual C++ Redistributable is required by Texconvx64 and DynDOLOD DLL NG and Scripts. DynDOLOD itself is a compiled Delphi program based on xEdit and its xLODGen tool mode that does not require additional libraries. It seems likely the error message is unrelated to the installed Visual C++ Redistributable, unless it mentions Texconv.

Increase the already mentioned MaxTextureSize setting in E:\Skyrim VR jepster\tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini to 16384 or add TreeLODMaxAtlasSize=16384 to it. I suggest to read the information in https://dyndolod.info/Help/Texture-Resolution how to test/find sensible texture resolutions. increasing by one step should be sufficient. Also see https://dyndolod.info/Updating how to keep the content of the preset folder to automatically keep the settings of the last generation. Upload new DynDOLOD log, debug log and bugreport.txt if it exists.

Debug=1 just prints the debug messages to the normal log in addition to the debug log. https://dyndolod.info/Messages/Exceptions OpenGL section: This can be also a bug with the tools encountering unexpected situations. Add GLDebug=1 under [TexGen|DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\[TexGen|DynDOLOD]_[GAME MODE].INI and make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum. Delete old logs. Add GLDebug=1 to the D:\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini, then run again and upload new log, debug and bugreport.txt if it exists please.

The DynDOLOD Standalone folder is the one where you unzipped the DynDOLOD Standalone to when following the second step of the https://dyndolod.info/Installation-Instructions/: Use 7-Zip to unpack the entire DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\. Since the crash seems to be object LOD mesh related and you seems to be able to 100% reproduce it, do a binary search to narrow it down to a single BTO that is required the game to crash: In the DynDOLOD output folder, go into the meshes\terrain\tamriel\objects\ folder where you will find lots of Tamriel.*.*.*.bto files. 1. Hide/Move half the files. 2. Test if you can reproduce the crash 3. If it crashes repeat step 1. 4. if it does not crash, restore the just removed half of files and instead remove the other half and continue with step 2. Repeat until only one file remains. It should be about 8 or 9 iterations. Upload the *.BTO file you found.

Check one of the generated BTOs, like Tamriel.4.8.0.bto in NifSkope. Select a grass LOD block and check its BSLightingShaderProperty sets Shader Flag 2 Back_Lighting. Check that its BSShaderTextureSet defines 3 textures, with the second to last (8th with array index 7) sets textures\DynDOLOD\maps\gray_25.dds. Check that textures\DynDOLOD\maps\gray_25.dds exists in the DynDOLOD output. If all that is the case, you could test if changing that texture to textures\white.dds makes a noticeable difference for that grass block in the game. If not, test in the game without CS to verify it works as expected with the default shader. You could use https://www.nexusmods.com/skyrimspecialedition/mods/68640 so the generated normal maps have a bit more definition.

The debug log shows that Level32 was not set. If you installed ACMOS with the uLockedObjectMapLOD=32 INI setting option, that might be the reason. For quick test, you could change the INI setting back to 16. If that make object LOD appear again, then generate new output with the Level32 checkbox checked.

See the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which normal log of DynDOLOD to also upload when making posts. Click on the Click on this link for additional explanations and help for this message of the message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Messages/Exceptions and scroll to the OpenGL section: This can be also a bug with the tools encountering unexpected situations. Add GLDebug=1 under [TexGen|DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\[TexGen|DynDOLOD]_[GAME MODE].INI and make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum. Delete old logs. Add GLDebug=1 to the DynDOLOD_SSE.ini, then run again and upload new log, debug and bugreport.txt (if it exists) please.

Thanks. Based on the logs, the LOD generation looks it was successful and can be used as is. Once there is a test version or new alpha version in the near future, test again without the GLDebug setting.

Click on the link Click on this link for additional explanations and help for this message about billboards not fitting as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Help/Texture-Resolution: The maximum possible resolution of textures generated by DynDOLOD can be set by changing the setting MaxTextureSize at the ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].ini. Typically the size of textures added to the object LOD atlas textures or tree LOD atlas textures should be controlled in the advanced mode. Standard tree LOD only supports a single tree LOD atlas texture per worldspace and a maximum of 256 billboards. In case there is not enough space for all the tree LOD billboard textures to fit onto the tree LOD texture atlas, resize some tree LOD billboards (use lower settings in TexGen) or lower the max tile size billboard in the advanced mode. Alternatively use ultra tree LOD. I suggest to not change the stitched/object and max billboard size to insane values and instead leave the defaults of 256, 256 and 1024 based on the screen resolution of 1080. Maybe increase one step. There is typically no use for 4k LOD textures/billboards. That is just a waste of VRAM. Having to create several object LOD atlas textures means more draw calls.

Disabling a mod is a troubleshooting step and not fixing the invalid *.JSON file. I suggest to simply fix the *.JSON file (with notepad for example) and remove the comma, so that the file validates and the mod works as expected.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs The log and debug log are saved when the program shuts down. Do not interrupt the shut down process so it can write the log files. While the new log is appended to older logs, the debug log is replaced every time. Keep a copy somewhere else for future references if required. Upload the DynDOLOD log and debug log from the log folder as explained.

Thanks for letting us know!

If the base record defines a *[l|h].nif (or whatever other indicators make it select those versions) it is supposed to use *_[0|1|2|3|4][l|h].nif now instead of just using *_0[h|l].nif as it did before. Verify and report if something does not work as expected.

Is there no bugreport.txt? See first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Check that F:\games\steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\FireHurtsRE\Solitude Braziers.json is a valid json file. For example with https://jsonlint.com/ It seems to have an extraneous comma at the end of the second entry. In notepad it should look like this instead: { "Solitude Braziers.esp": [ { "id" : 2048, "offset" : [0, 0, 60], "bounds" : [30, 30, 30], "angle" : [0, 0, 0], "type" : 0}, { "id" : 2050, "offset" : [0, 0, 25], "bounds" : [50, 50, 50], "angle" : [0, 0, 0], "type" : 0} ] }

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log, debug log and bugreport.txt to upload when making posts. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search Before making "me too" posts, read the posts and answers to see if a similar problem was already sufficiently reported and/or an issue was already solved. If the answers or solutions do not seem to apply or do not have the desired result, report the problem or ask for help for an issue with the logs and information as explained below. Always provide logs. "Me too" posts without required logs and information might be ignored or removed. Click on the Click on this link for additional explanations and help for this message of the message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Messages/Exceptions and scroll to the OpenGL section: This can be also a bug with the tools encountering unexpected situations. Add GLDebug=1 under [TexGen|DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\[TexGen|DynDOLOD]_[GAME MODE].INI and make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum. Delete old logs. Add GLDebug=1 to the DynDOLOD_SSE.ini, then run again and upload new log, debug and bugreport.txt please.

The drive link is asking for a login. Provide a working link for the DynDOLOD debug log. Do not install DynDOLOD over older versions. See https://dyndolod.info/Installation-Instructions Use 7-Zip to unpack the entire DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\. Ensure that the directory structure is preserved. See Updating how to update existing installation and save games. See https://dyndolod.info/Updating See answers for https://dyndolod.info/FAQ#Entire-LOD-missing. Start with checking object LOD distances in https://dyndolod.info/Help/Mod-Configuration-Menu-NG#Settings and since you are using ACMOS, make sure you checked the Level32 checkbox in the advanced mode. See https://dyndolod.info/Help/Advanced-Mode