Ardellian

Oh OK. I didn't know that was why they were greyed out. Thanks for helping me out.

I'm using Windows 10 and theme settings; background is harmony but I use Wallpaper Engine for my backgrounds, Color is Custom, Sound is Windows Default, Screensaver is Mystify. Font settings; Hide fonts based on language settings checked, and Allow fonts to be installed using a shortcut (advanced) unchecked. Here's a screenshot of my screen. Generate Tree LOD is greyed out because I'm using 3d Tree LODs, but everything else were already greyed out before I did that. https://mega.nz/#!VChASKjB!zWTSEf8rJoL8yRPXwtjPNp4pOf9NrmDepYJv8L4kdIs

No, I still can't click any of the options that aren't already checked.

Ok I used the updated version and there wasn't a noticeable difference. No userscripts or access violations like last time.

I fixed the tint layer errors and there's no more userscript errors.

For some reason TexGen worked the second time, but I still can't check any boxes in the DynDOLOD's advanced settings except for worlds. DynDOLOD - [00:00:16.250] Exception in unit userscript line 546: Access violation at address 0000000000BF537A in module 'DynDOLODx64.exe'. Read of address 0000000000000000

OK I deleted all the mods causing errors for some reason and fixed my bashed patch. However I am receiving a TexGen access violation pop up that prevents me from using the program. [00:00:00.280] Exception in unit userscript line 520: Access violation at address 0000000000BF537A in module 'TexGenx64.exe'. Read of address 0000000000000000

I found some more mods that created less errors when their esp is disabled. But I still am getting an error when I enabled my bashed patch.

Yeah it worked just fine. The top of the program says DynDOLOD TexGen 2.27 (1) by Sheson. I have one monitor and I only made a second profile with just vanilla billboards and dyndolod resources to see if any mods were the issue. Right now I disabled all of the quest/land mods in my load order and adding them back over time to see if any one of them is causing any issues. So far I found two mods that created errors when I activated them again. One mod just fixed shores and the other was just a quest mod. I am not certain why they would be causing any errors. It might be conflicting world spaces with another mod in my load order. I'm not a modder so I could be wrong and it could be something else.

Maybe there's conflicting LODs or something. For now I could activate one mod at a time and run dyndolod each time to see if that would tell me the culprit/s on what's causing the errors.

OK I checked antivirus and windows then started the programs again with added billboards. The only issue this time was that I couldn't check any boxes in DynDOLOD's advanced settings. After that I tested my main profile by disabling a tree mod for the vanilla billboards but that didn't solve anything. I'm just spit balling here but since it mostly worked with the second profile then it might be a mod/s that is causing the errors. But it still doesn't explain why I couldn't check anything in the advanced settings.

I tested with just vanilla files and DynDOLOD resources. TexGen worked fine but in DynDOLOD I couldn't check boxes that don't already came checked. After clicking OK an error came up and I had to use task manager to close DynDOLOD because it couldn't save. [00:00:02.156] Error: Can not find tree LOD billboards required to create tree LOD. See log or FAQ for more details. [00:01:41.860] [00:00] Error saving DynDOLOD.esp: Cannot create file "F:\DynDOLOD_SSE\DynDOLOD\DynDOLOD_Output\DynDOLOD.esp". The operation completed successfully [00:01:41.871] [00:00] Errors have occured. At least one file was not saved. Would verifying integrity of the game files fix this error and maybe allow me to use DynDOLOD without any more issues?

The error message is Error: Load order messed up! Tried to find a file id higher than files loaded. 0>-1. Try generating tree LOD for this load order. Stopping script. And the userscript line was Exception in unit userscript line 458

The test version didn't fix the problem. Here's the xEdit logs after applying that script. https://mega.nz/#!YTREnCqC!fnKcrYsHGMFaY3yV_r2Kb0x4UYzwiUAt0jhG6e5viqY I hope this issue can be resolved soon and thanks for taking the time to help me.

SSEEdit logs: https://mega.nz/#!ND4SCIgB!Wowqo-UV3zb0onbscqx5zhPHPe7kbrXpC-wLie2r1k0 DynDOLOD logs: https://mega.nz/#!dHhVHS7a!etVmRABg1lJt0_QuyiFxJ43jzzzwKsSyL4H7O_-c41A I shorten them but if that's not enough information I can give the full logs.