sheson

This does not show if the latest alpha-111 was used or not. Upload the accompanying TexGen/DynDOLOD logs and debug logs for which the checks have been done. "Grass mapping not found" means that those grasses found in the cgid will not have grass LOD. This is expected for underwater grasses and grasses that do not have billboards generated. If some BTOs have no grass LOD, it means there should be corresponding no "mapping not found" or "no grass data" messages. The first tells you which grass LOD billboards are missing, which you can then double check for creation in the ..\textures\terrain\lodgen\TexGen_[GAME MODE]_[Tree|Grass]_Billboards.txt log file as explained at https://dyndolod.info/Help/TexGen-Configuration#Tree-Grass-LOD-Billboards. Use expert mode to only generate a specific BTO again, so you only have log message for those 16 cells it covers. https://dyndolod.info/Help/Expert-Mode#Specific-Chunk Use the DynDOLOD SkyUI MCM - You Are Here to know the coordinates for a BTO.

Third party guides are categorically outdated, especially when it comes to ALPHA version and experimental features. Read and use the official documentation that I already linked instead. https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds The updated DynDOLOD DLL NG version does not affect LOD generation, though. As I already wrote, if problem persists, also enable and check/upload papyrus log and also upload all files from DynDOLOD Output ..\skse\plugins\DynDOLOD_Data\

Update DynDOLOD DLL NG and Scripts to the latest version From your log: DynDOLOD DLL: F:\Games\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD.dll, Version: 3.0.1.0, Game Version: SE/AE 1.5.x/1.6.x, VR 1.4.15, Date: 2023-01-06 21:00:00 Latest version of the DLL is Version: 3.0.2.0

Random success or not is the question...

Read the first post which DynDOLOD debug log to also upload when making posts. However, judging by the DynDOLOD log, you started DynDOLOD and quit it again with generating LOD, which will have replaced the debug from the generation in question, which is unfortunate. Install the latest version of DynDOLOD NG and scripts from https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds If problem persists, also enable and check/upload papyrus log and all files from DynDOLOD Output ..\skse\plugins\DynDOLOD_Data\

Read the first post which DynDOLOD log and debug log to upload when making posts.

Let me know what happens with this test version https://mega.nz/file/UdRFDRBD#jeSA6FBQyzoJKPmfvMHU_IrOF_wV34kXKsIocBdfguQ

I thought the current problem was that it crashed? Upload the log and debug log.

Do not select the Solitude Exterior patch (..\DynDOLOD\SolitudeExterior_Tamriel.patch) when installing DynDOLOD Resources.

The vanilla game does not have the plume in Tamriel worldspace. No information was provided. DynDOLOD does not add the plume to the Tamriel worldspace. This forum is for DynDOLOD/xLODGen/LOD support . If you have issues with a specific mod doing things you do not like, you could ask the mod author or use its comment section for help or ask for help on a generic modding/public forum. Yes, xEdit can be used to quickly remove unwanted records/references from plugins.

No. Read/Write functions do not care how long it takes. They either return an error or are successful when they are done.

Yes.

It is that your setup for some reason sometimes fails with the OpenGL command to generate mipmaps, even on textures for which it worked fine earlier in the same process. The heap crash is most likely caused by not properly recovering from that error in order to keep going instead of stopping the process. This test version should do it without heap crash now https://mega.nz/file/ZJ4VWDLb#SGyHh8rgHYORc1WqdwzvrjJWnihDonkJMwL6AuHDKIM Test with default INIs.

Always use the latest alpha version. Do not waste time using older versions or reporting problems with older versions. Go through every step of the No Grass LOD Check List and not only mention the outcome/result of a couple.

Ii happens because the very last worldspace that is processed does not have suitable cells.

https://dyndolod.info/Mod-Authors#How-to-ignore-all-references-of-a-child-worldspace-for-copying-to-parent-worldspace-and-LOD If this does not address the problem, then make a more specific report.

This will be fixed in the next version.

Those logs do not help. Add RealTimeLog=1 to DynDOLOD_SSE.ini, then upload the realtime log from the log folder.

Just run it a few more times, see if it happens again.

So you don't know what it was doing when the exception c0000374 happened? Can you reproduce it?

Do you know what it was doing when the exception c0000374 happened? If we assume that the AMD driver is stable, how certain are you about the hardware (memory, power supply), related BIOS settings. The issue(s) just seems very random/all over the place.

Check the Windows Event log for related entries. The others indeed went through without any failures.

So far so good. If you find the time, do a couple more runs to be sure and upload the log/debug log even if they always run through.

Test what happens with this test version https://mega.nz/file/YJgXSJLA#9YpgdccTNnjRu5YwqPWrhwwN8mbwJoxfOrmXcDmMha0 If this happen to run through upload log and debug log anyway. No other logs are needed.

Let me know what happens with this test version. https://mega.nz/file/wAJAlaRC#CZ3lzXWBMlpHwd1Eg2xodOJo1tvcXjF0sQ2bXDhHsSI