sheson

See https://dyndolod.info/Help/Grass-LOD#Performance Use Skyrim Performance Monitor and/or the task manager to track usage of memory.

Try this version https://mega.nz/file/MNxWGIwI#bBVIqiC-nP9SSG9SPmvSFqGJtqiLtEhEUI-xhi4f96I

Compare the text files. For example with a Notepad++ plugin. Or just check the file dates...

Really read error messages and their explanations. Temporarily disabling plugins to not see error messages is not fixing the error. The game is only "working fine" until it doesn't. Use the xEdit error to check plugins for errors. To fix unresolved large references in the ESM, use the xEdit script https://github.com/TES5Edit/TES5Edit/blob/dev-4.1.5/Build/Edit Scripts/Skyrim SE - Generate Large References.pas To see the large reference data on a worldspace record in xEdit, uncheck 'Hide "never shown" in the options. Remove the RNAM data so the script can add the new data. Generating LOD while temporarily disabling plugins despite all the warnings to not do that, means that their worldspace and cell changes are not being carried forward into the DynDOLOD/Occlusion plugins.

Is this error repeatable? Always the same base record? Replace DynDOLODx64.exe with this version, see if it makes a difference.

That is just the bugreport.txt. Also upload the log and debug log.

No. Files are simply overwritten as needed. LODGen is targeted to /using .NET Framework 4.8. If the .NET 6 update changes anything I do not know. Maybe test by uninstalling it. I keep running "Execute LODGen" in expert mode on your export files for the four seasons for Tamriel over and over again with no failures. Since it is random I doubt it has anything to do with specific NIFs for which you might have different versions. Check which mods overwrite DynDOLOD Resources. Also see https://dyndolod.info/Help/Load-Overwrite-Orders. Read the first post or https://dyndolod.info/Official-DynDOLOD-Support-Forum which log and debug log and bugreport.txt (if it exists) to upload when making posts.

No problem! It is such an obscure problem. So this is a good reminder to really check such details in the logs as well.

You did not say which DynDOLOD version you are using. Do not paraphrase message. Upload the log instead. See https://dyndolod.info/Messages/Wrong-Billboard-Path. If you are using DynDOLOD 3 Alpha and thus participate in the alpha test, also read the first post of https://stepmodifications.org/forum/topic/16796-dyndolod-3-alpha-88/ and https://dyndolod.info/Generation-Instructions

As explained at https://dyndolod.info/Help/Ultra-Tree-LOD, ultra tree LOD means that LOD for trees is done is done in object LOD with billboards and optional 3D tree LOD models. HD billboards with Billboard4 are visually the best LOD billboard option. Always generate HD billboard if using ultra tree LOD. Obviously 3D tree LOD requires more resources than billboards. Billboard4 requires a bit more resources than Billboard1/2 but it is nothing compared to 3D tree LOD or especially grass LOD.

When you add a line realtimelog=1 under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini the there should be a DynDOLOD_SSE_realtime_log.txt in the log folder. Also check the Windows event log. You might want to update MO2 to the latest version.

If the content of the object LOD atlas texture changed, then there probably will be visuals issues. You would need to update all BTO for the new atlas. You also should update LOD Level 8 and 16.

The log and debug you are uploading seem to show DynDOLOD was started and then cancel was clicked. Do not start the program again after there was an error, so the debug log is not being replaced.

That was LODGenx64.exe from Alpha-87. Honestly, none of this makes any sense right now. Upload contents of ..\DynDOLOD\Edit Scripts\Export\

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log and debug log to upload when making posts. I have no such error message after installed Point The Way 2.0.6 from https://www.nexusmods.com/skyrimspecialedition/mods/352 No idea what file "Dawnstar" refers to.

For objects to have LOD a LOD asset needs to be installed/created in the load order or use mesh rules to set the full model for LOD. The base record does not define LOD models / there is no LOD model that matches the full model filename. See https://dyndolod.info/Mod-Authors and https://dyndolod.info/Help/Mesh-Mask-Reference-Rules

The log files seems to be from newer sessions that do show the error from the bugreport.txt. Delete the entire log folder and bugreport.txt and then run again. Upload new bugreport.txt and logs. Then delete those files again. Replace DynDOLODx64.exe with this version and test if runs through.

What happens if you use this version? https://mega.nz/file/AdYjEbiD#2WfMfnr-YNlvIL49KCocuLk_uUmyLm_se3T2qu7KFVA

See the first post of the DynDOLOD 3 Alpha thread where to make posts. I moved your post to the thread. See the first post which log, debug and bugreport.txt to upload when making post. If none of them exist because the OS, antivir or whatever just killed the program, check the Windows event log for related messages and post that. Set realtimelog=1 in ..\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and try again. Upload the log from the logs folder. Make sure the hardware (CPU, memory in particular), BIOS setting, OS etc. are stable.

Did you also unpack the *.pdb to Edit Scripts? What alpha version were you using before 88?

Try with this version https://mega.nz/file/sZx3RA6a#VG_SIq43RyOiz3E1flddHOGqOVLbLjkXNCAV5izWt_8 Hopefully that writes the needed info to the log file.

Unfortunately the logs are incomplete and do not contain the error message or the trace log. Did you also copy the LODGenx64.pdb with the LODGenx64.exe into the Edit Scripts? Can you check the Windows Event log what it says? Check the c:\Windows\Minidump\ if it contains files with the timestamp.

Upload the log, debug log and bugreport.txt if it exists as explained in the first post when making reports. Occlusion calculations (that is what the bugreport.txt you uploaded a while ago showed) do not work any differently if the program is in focus or not. Such randomness often means there could be a problem with the hardware, BIOS setting etc. for example memory related. By the time the summary is created or the browser is opened, the occlusion calculations are long done. It could be an entirely different problem or just a secondary problem as the result of another. Needs logs and bugreport.txt using the latest version.

I am not able to replicate this. You have the right mesh from DynDOLOD Resources and it is does not seem to have any season replacement. What is odd that the mesh only sporadically causes a problem. It should always be processed exactly the same for all seasons. Download https://mega.nz/file/oMBlAAaa#y6nXWUwL6L9rlfKV_5jUhksPmYgJQMLaTqH8q_J5xnE and replace LODGenx64.exe in the Edit Scripts folder. It will print a stack trace to the log. Then run again, upload the LODGen log for whatever season the error happened.

xLODGen can only overwrite grass LOD which is part of object LOD, if you generated object LOD with xLODGen. Use xLODGen to generate terrain LOD only. Happy Little Trees Add-On - DynDOLOD 3 contains 3D tree LOD assets. If you do not install it, then ultra tree LOD will always use the billboards instead. If the intention is to only use billboards, then 3D tree LOD assets do not need to be installed. https://dyndolod.info/Help/Ultra-Tree-LOD "Billboard1 has 4 triangles per tree, while billboard 4 has 8 triangles per tree." This is negligibly if the game runs well above 60 FPS and has headroom or when using grass LOD. If there is a problem generating LOD, carefully check the error message.