sheson

MO2 Menu Tools -> Settings -> Plugins tab -> left treeview unfold [+] Preview, select Preview BSA, then top right check [ ] Enabled Then MO2 right window Data tab, unfold [+] Grass , bottom right, enter the filename in question - tamrielX-005y0010.gid The winning source BSA/mod will be shown in the "Mod" column - enable the column if necessary. If it shows Skyrim - Misc.BSA and not Grass Cache Fixes.bsa or a loose file from whatever mod, then the vanilla file not being overwritten is the cause of the error message. Otherwise the winning file is corrupt and needs to be deleted/replace by a valid one. You can also use the xEdit Asset Browser (started after loading everything into xEdit with CTRL+F3) to see all containers (BSA, loose file) for a file, not just the winning one.

TexGen completed successfully without error. You uploaded the log from DynDOLOD but not the debug log from DynDOLOD. https://dyndolod.info/Messages/Exceptions#Unknown-grass-data-file-format Find the file in the ..\Data\Grass\ folder and delete it, or in case it is a vanilla *.GID file make sure it is being overwritten with a valid file. It is unclear if the tool is looking for *.cgid or *.gid files, since you did not upload the DynDOLOD debug log and did not mention it. If the grass cache file for the coordinates can not be found as a loose file, we have to assume that this means you instructed the tool to use *.gid files and it is reading the vanilla *.gid file from the BSA. As explained, in that case make sure it is being overwritten by a *.gid that is valid for Skyrim SE.

Is this supposed to be a joke?

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs ..\DynDOLOD\Logs\[DynDOLOD|TexGen]_[GAME MODE]_Debug_log.txt Logs provide information. Information that can help to have more specific responses/answers. https://dyndolod.info/Official-DynDOLOD-Support-Forum Always use the latest DynDOLOD Standalone and DynDOLOD Resources version. Bugs and other problems may already be fixed or addressed.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs https://dyndolod.info/Messages/Exceptions#Unknown-grass-data-file-format Find the file in the ..\Data\Grass\ folder and delete it, or in case it is a vanilla *.GID file make sure it is being overwritten with a valid file. The mod Grass Cache Fixes comes with a BSA that overwrites the vanilla grass *.GID files which are typically not generated by grass cache generation, since they are in areas that have been removed from Skyrim.esm.

You might want to try terminating the crapware and then running the tool(s) and using the linked test version etc. first. How to best to do a clean driver installation would be something to ask on a AMD/Windows etc. support forum. There seems to be an influx of new issues potentially caused either by changes with drivers, unneeded software or changes in the OS, while the way the tools work is still the same as it was a couple years ago.

Terminate whatever crapware installed with the graphics card driver before running any of the tools or do a clean reinstall of the graphic card driver without any of the crapware.

Read the first post which debug log to also upload when making posts. Get the test version from this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-122/?do=findComment&comment=270483 and follow the instructions. If the problem still happens follow the instructions from this post https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-122/?do=findComment&comment=270485

See what happens with this test version https://mega.nz/file/RUQlla5T#3dsJH7Ec5qPTRb-DYghY2srcoC1yRAm0rTzEkc8EKGg If there are still issues, add GLListDebug=1 and GLDebug=1 under [TexGen] to ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI. Only enable the RealTimeLog in case the program is terminated without having the chance to writes its own bugreport, log and debug log.

Something must be happening to the render context between making it current for the current thread and then immediately requesting a new texture ID when using shared contexts between threads. The workaround uses one context for rendering, models and textures instead of 3 shared ones. The question is why it isn't a problem when running TexGen, which does what DynDOLOD does a hundreds times over.

I am that lazy that I didn't update them with the new method.

Error reading grass Tamriel [x,y] <Unknown grass data file format> Use the "Click on this link for additional explanations and help for this message" to open https://dyndolod.info/Messages/Exceptions. Scroll down to "Error reading grass [worldspace] [x,y]" and to "Unknown grass data file format". Read both the explanations. Searching the official DynDOLOD website: https://dyndolod.info/search/node?keys="Error+reading+grass" https://dyndolod.info/search/node?keys="Unknown+grass+data+file+format" Searching the official DynDOLOD support forum: https://stepmodifications.org/forum/search/?q="Error reading grass"&quick=1&type=forums_topic&nodes=223 https://stepmodifications.org/forum/search/?q="Unknown grass data file format"&quick=1&type=forums_topic&nodes=223 Searching the internet: https://www.google.com/search?q="Error+reading+grass" https://www.google.com/search?q="Unknown+grass+data+file+format"

Add RenderSingle=1 under [DynDOLOD] in the ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini, delete old logs etc, run again, upload new logs.

Remove old bugreport and logs and keep the changed INI settings, then see if there is anything different with this test version https://mega.nz/file/8dgERZDB#KmxMDvHOeToIPrWeE8e0aasvf1AeWJ3u6B2KJ3RRtOk, upload new bugreportr, log and debug log. Since the error only happens in DynDOLOD, no need to rerun or upload logs from TexGen.

https://dyndolod.info/Help/Advanced-Mode#Mesh-Mask-and-Reference-Rules To edit, add or delete rules, right click a row. https://dyndolod.info/Help/Mesh-Mask-Reference-Rules The order of rules matters. Rules at the top match before rules at bottom. Reference Form ID rules always take precedence over Mesh Mask rules which target base records. The last default rule for '\' defines that any reference using a base record that there is a LOD mesh for will have object LOD, unless the reference is dynamic or animated. Then it will be a dynamic LOD. https://dyndolod.info/Help/Mesh-Mask-Reference-Rules#Mesh-Mask The mesh mask is any part of the path/to/model.nif of a full model defined on a base record. It does not use wildcards and simply matches any part of the entire path. https://dyndolod.info/Mods/Replaced-Full-Model-Example-Azura-Statue In these cases creating a custom mesh mask rule...

Edit ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini in notepad and add GLListDebug=1 and GLDebug=1 right under [DynDOLOD]. Remove old logs and bugreport.txt and run again. Upload new log, debug log and bugreport.txt if it exists.

Read the first post which debug logs to also upload. Check the task manager for background Texconv processes. See if terminating it makes the tool continue with an related error message. Make a clean install of the latest driver release version only, do not install any of the crapware, clean out the log folder and remove old bugreport.txt and generate again. If problem persists upload new log, debug log and bugreport.txt if it exists.

Thanks. Edit ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and add RenderTexturesSingleThread=1 under [TexGen] Keep the GLListDebug=1 and GLDebug=1 as well. Clean out the log folder and run again. Upload new log and debug log. I would also be interested in the results of a clean install of the latest release driver version and in case there are issues with no logs or bugreport.txt to add RealTimeLog=1 under [TexGen] to the TexGen_SSE.INI and upload that and whatever related entries you can find in the Windows Event log.

What you are providing is a problem description. What you are not providing is information like meaningful screenshots, logs (or checking them), load order information or mentioning potential mods might be modifying the bridge / Sanctuary. If you have problem following a third party guide you should ask the author. I suggest to ignore guides that neglect to instruct to set a dedicated output folder with -o and lets users generate files into the data folder or that have you set wrong compression format for object LOD atlas normal map and specular textures etc. LOD generation does not change or affect full models or previs data in active cells.

That means there must be a problem with DirectX (DirectCompute), which Texconv uses for BC7 compressions. BC1/BC3 are done with the CPU. If you edit ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and change to these values for the object and tree LOD atlas they will be done with the BC1/BC3 compression as well: ObjectLODDiffuseFormat=200 ObjectLODAlphaDiffuseFormat=202 ObjectLODNormalFormat=200 TreeLODDiffuseFormat=202 See if you can update or repair DirectX or try a clean install of the latest release driver again.

Zero information. No question was asked. Check the first post. Check the included readmes. Check https://stepmodifications.org/forum/topic/17508-fo4lodgen/. Check the log messages.

HD LOD shaders (or rather the shape name and flag) are typically not applied to shapes that use LOD textures (*lod.dss or object LOD atlas) but full textures only. There is quite a bit more automatic stuff with DynDOLOD It is possible to force "HD" on what is not seen as HD LOD, but I'll need a practical setup to test/address this. If you have a test plugin with just the necessary records and full/LOD assets etc. that would help. PM me the download details if you do not want to share publicly.

The texture(s) shown in the are ones that have just been generated and saved uncompressed by TexGen. Which texture Texconv currently tries to compress or uncompress may be different. TexGen is generating stitched object LOD textures from full textures when Texconv seems to stall. Open ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and add LockTexconv=1 under [TexGen] then test if there is anything different. If not, set change the compression formats at the bottom of TexGen to BC3 (DXT5) for Diffuse alpha and Normal specular on the left and to BC1 (DXT1) for Diffuse and Normal on the right.

Check the Windows event log for related messages to crashes without log. It typically means the tool is being terminated. In that case also add RealTimeLog=1 to the INI. In any case, run this test version of TexGenx64.exe https://mega.nz/file/xBATGDxT#09spFHG99r0lPVz9DRrQ_UBuzheFe1pWgeZkeezS7wk with GLListDebug=1 and GLDebug=1. Clear out the log folder first. Upload the new log, debug log and bugreport.txt if it exists.

Upload the new log and debug log and bugreport.txt (if it exists) for the updated driver. Let us know what setting you changed in the Geforce control panel. Edit ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI in Notepad and add GLListDebug=1 and GLDebug=1 under [TexGen]. Delete old logs and bugreport.txt and then run again. Upload that log and debug and bugreport.txt if it exists as well.