sheson

Download and install the DynDOLOD Resources SE Core Files. Also , the game should not be installed to Program FIles x86 to avoid problem with Windows permission, UAC, antir vir etc. Best to follow any modding guide.

You are asking for a assumed solution for a problem, instead of reporting the problem. Read the first post what log files to upload when making posts.

That is the usual procedure.

Great! Added dedicated release of texture memory above a certain threshold.

Replace TexGenx64 with this test version and see if it runs through without issues.

Can you check VRAM usage with a tool and then start TexGen and use the Preview button for the rendered object LOD textures and scroll through the drop down list and check if VRAM usage keeps continuously rising or also falls when switching from a busy city texture like slod3.nif to a simple dlc01icewalllod.nif for example?

I do not really know much about ATI /AMD cards and their software. Is that the driver included in the Adrenalin 21.5.2 download from June 2021?

The "latest standalone archive" refers to "DynDOLOD Standalone 3.00 Alpha-44" from the first post right now, obviously. Sounds a bit like a OpenGL memory release/free function is not working properly with the ATI hardware/driver. What card do you have? What driver version?

The mod itself is most likely not the problem. What version of EVT did you have installed exactly? Unfortunately you have not uploaded any of the requested log files. Removing files is a troubleshooting step and not a fix. Obviously the rendered object LOD texture these files are for are not going to be updated. Try to reinstall the files from the latest Standalone archive. See if starting TexGen and then using preview for the rendered object LOD textures works for any of these files.

Somehow the OpenGL render crashes in some ATI driver DLL it seems without returning an error back to TexGen. Remove C:\Lexy's LotDB\DynDOLOD Special Edition\Edit Scripts\DynDOLOD\Render\Objects\lod\rtbuildingslod01.nif from the folder, see if it runs through then or the next/another NIF has problems too.

Read the first post what log files to upload when making posts. in addition to the log files also upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Tree_Report.txt Follow the instructions in the read me to write debug messages to the papyrus and then post the papyrus log. There is a problem with srg_treepineforest05_01617CAEpassthru_lod.nif. The file is most likely fine by itself. The problem is, that it shouldn't be used directly where it could ever be enabled/disabled by dynamic LOD scripts.

Well, as you can see yourself TexGen does not end with the message "TexGen completed successfully" as explained in the included manual. Very unusual that it ends silently in the middle of things. Is there no bugreport.txt?

Post the TexGen log and debug log. Read the first post what log files to upload when making posts. Read the DynDOLOD FAQ: Game: ILS or CTD. Read DynDOLOD-README.txt as also suggested by the FAQ how to troubleshoot CTD. Upload the .Net Framework crash log if further help with it is required. The most likely cause is an invalid mesh or texture from a third party mod.

I can guarantee that the script does not cause CTD. Zero information was provided.

Yes, it is explained in the documentation and dozens of forum posts for ages. Crap ware blocking access is nothing new. Adding an exception for all tools involved - mod manager, TexGen/DynDOLOD, Texconv, LODGen - should be sufficient.

Click the Help for this message link to open https://dyndolod.info/Messages/Can-Not-Copy-Resource A problem happened while trying to copy an asset from an BSA or the data folder. Obviously check that the source file exists, can be read and that the target path can be written to. For example, use the xEdit Asset Browser to filter for the source file and use right click save as to write the file. The fist mentioned container is the one with the highest priority. The last part of the message contains the error message from the OS. The system cannot find the path specified typically means the OS, UAC, antivir or some other 3rd party crap ware is blocking write access to the mentioned destination path. Add an exception to whatever it is that is blocking access. Remove old files from the destination/output path, which might prevent creating the new files because they are blocked by other programs etc. Use forum search for find similar posts and answers.

From the DynDOLOD FAQ Q: Game: Rectangular holes in LOD A: Caused by vanilla pre-computed occlusion. Has nothing to do with the LOD data itself. Either use xLODGen or DynDOLOD to update the data. See the 'TVDT - Occlusion Data' section in ..DynDOLOD\Docs\DynDOLOD_Manual.html and https://stepmodifications.org/forum/topic/14250-skyrim-tvdt-occlusion-culling-data/ Read the DynDOLOD FAQ answers for Q: Game: Out of place objects / floating objects / flickering full models Read the first post what log files to upload when making posts. You will need to look up the references of the LOD windows in xEdit to check their EditorID to know for which plugin/form id they were added. Then check which plugin was the last to modify the source reference and its base record.

The system cannot find the path specified. Read the linked help files. Use forum search. The answer is always the same: This is caused by the OS preventing writing the destination file. Either because of UAC, antivir, 3rd party crap ware or other process/programs blocking folders/files. The last one can be cleared by a reboot. https://stepmodifications.org/forum/topic/15612-error-copying-textures-the-system-cannot-find-the-path-specified https://stepmodifications.org/forum/topic/15604-texgen-error-cannot-copy-resource-the-system-can-not-find-the-path-specified/ https://stepmodifications.org/forum/topic/15606-dyndolod-300-alpha-44/page/131/?tab=comments#comment-250819 https://stepmodifications.org/forum/topic/15606-dyndolod-300-alpha-44/page/127/?tab=comments#comment-250663 https://stepmodifications.org/forum/topic/15606-dyndolod-300-alpha-44/page/110/?tab=comments#comment-249789 https://stepmodifications.org/forum/topic/15606-dyndolod-300-alpha-44/page/91/?tab=comments#comment-249043

Something seemingly "working" does not mean it doesn't have errors. Run xEdit's error check on the load order. It will check all records. If you want to use mods/plugins made for SSE with VR without problems, then VR needs to contain all the records and assets from SSE. -TES5VR is a game mode identifier for the tools. It most importantly defines which Windows registry key and INI paths and filenames to use. It does not change records in plugins.

The mod manager download directory is where DynDOLOD Resources are supposed to be downloaded to so they can be installed as any other mod. If you want to make it more complicated use the mega link or go to the Nexus file page.

That is a rather cryptic way of saying that the FOMOD xml in DynDOLOD Resource SE Alpha 3 has a wrong file source for the holy cow. Fixed in DynDOLOD Resources SE 3.00 Alpha-13

Use modwat.ch instead of posting screenshots of load orders. Installing mods made for a different game version and hoping for the best is not going to work. Either install versions made for the game version you are using or install/create the required patches to make it compatible. I suggest to follow a basic modding guide, also to learn about these basic modding requirements. The Unofficial Skyrim Special Edition Patch is not compatible with other game versions than Skyrim Special Edition, obviously. It requires a patch like Skyrim VR - USSEP 4.2.2 and SSE 1.5.97 Compatibility Patch for example. With Skyrim VR patched with SSE updates, most plugins and mods made for Skyrim Special Edition should work fine/better and not have unresolved errors anymore related to Skyrim Special Edition updates.

Try disabling or tuning down image based lighting settings in ENB. Typically the reason why a shape does not use the texture atlas is because its UV is outside of 0.0 and 1.0. There is no blending between LOD models, LOD Levels or LOD assets types. Read the DynDOLOD manual how to generate LOD for Open Cities in two passes. First pass without it for object and tree LOD. Second part with it for dynamic LOD. If help is required to solve the cause of errors, provide necessary information and ask for help how to solve them.

Stop errors stop the process because LOD generation can not be successfully completed. Errors are problems that need to be fixed. Warnings are problems that should be fixed. No information was provided. So it is unclear what error message or problem is talked about. Read the first post.

DynDOLOD adjusts the alpha threshold and mipmaps when adding textures to the tree or object LOD atlas. LOD has a fixed alpha threshold of 128. If a LOD model is added to an object LOD mesh and it uses a source texture directly instead of the texture atlas for whatever reason, then in fact it uses that unmodified source texture in all its glory with the fixed alpha threshold of 128.