Error: OpenGL: from TwbRender.DeleteID

[strangelyliteral]

Okay, I clearly screwed something up here.

Running a modified, lower-end version of the default STEP loadout (which means I'm not using the STEP patches, since I didn't want to use Odin or Vrokii for magic/perks, if that's at all relevant). Everything up to this point is running fine. I cleaned dirty mods and sorted everything in LOOT. I skipped the post-processing step for performance reasons, but I got the grass precached, painted my roads, and ran TexGEN successfully. I open DynDOLOD and set it to run, but it fails. This is the error I receive:

Quote

Error: OpenGL: from TwbRender.DeleteID while processing textures\dungeons\ridgedstone08.dds.

It's not always that file it hangs on (if anything it's usually one of the High Hrothgar textures), but it's generally something in the Realistic Skyrim Overhaul.

I have completed a clean update of my video drivers, as recommended by the error notice. I've tried to research and troubleshoot this on my own, but everything is now melting into gibberish (because frankly that log looks like dogshit), so clearly it's time to ask for help. Here is the sselodgen_log upload and here is bugreport.txt, I believe these are the correct logs but as this process has been driving me slowly mad, I am well aware something crucial might be missing. Please let me know what else might be needed (may have to ELI5 for me to locate it) and I'll provide it.

Thank you in advance to anyone willing to help. I'm so close to done, but this is proving beyond my ability to solve via RTFM and google.

[sheson]

7 hours ago, strangelyliteral said:

Okay, I clearly screwed something up here.

Running a modified, lower-end version of the default STEP loadout (which means I'm not using the STEP patches, since I didn't want to use Odin or Vrokii for magic/perks, if that's at all relevant). Everything up to this point is running fine. I cleaned dirty mods and sorted everything in LOOT. I skipped the post-processing step for performance reasons, but I got the grass precached, painted my roads, and ran TexGEN successfully. I open DynDOLOD and set it to run, but it fails. This is the error I receive:

It's not always that file it hangs on (if anything it's usually one of the High Hrothgar textures), but it's generally something in the Realistic Skyrim Overhaul.

I have completed a clean update of my video drivers, as recommended by the error notice. I've tried to research and troubleshoot this on my own, but everything is now melting into gibberish (because frankly that log looks like dogshit), so clearly it's time to ask for help. Here is the sselodgen_log upload and here is bugreport.txt, I believe these are the correct logs but as this process has been driving me slowly mad, I am well aware something crucial might be missing. Please let me know what else might be needed (may have to ELI5 for me to locate it) and I'll provide it.

Thank you in advance to anyone willing to help. I'm so close to done, but this is proving beyond my ability to solve via RTFM and google.

The provided links both show SSELODGen being started without any generation log messages. SSELODGen, which is typically used to generate terrain LOD, is not relevant in this context.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log, debug log and bugreport.txt (if it exists) to upload when making posts.

The error message should have a link Click on this link for additional explanations and help for this message of the message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages that opens https://dyndolod.info/Messages/Exceptions and scroll to the OpenGL section:
This can be also a bug with the tools encountering unexpected situations. Add GLDebug=1 under [TexGen|DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\[TexGen|DynDOLOD]_[GAME MODE].INI and make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

Delete old logs. Add GLDebug=1 to DynDOLOD_SSE.ini, then run again and also upload the new log, debug and bugreport.txt please.

[strangelyliteral]

Okay, I think I have the correct logs this time. For some reason DynDOLOD ran for nearly three hours straight before crashing. Previously it had done me the courtesy of crashing within about 15 minutes. So the main log is 116MB post-truncation and the debug log is 273MB pre-zip. Anyway, here are the logs plus the bug report in a zip file. I lost the exact error message while originally trying to put this up on paste.ee but everything else should be there.

Let me know if you need anything else, thanks.

[sheson]

8 hours ago, strangelyliteral said:

Okay, I think I have the correct logs this time. For some reason DynDOLOD ran for nearly three hours straight before crashing. Previously it had done me the courtesy of crashing within about 15 minutes. So the main log is 116MB post-truncation and the debug log is 273MB pre-zip. Anyway, here are the logs plus the bug report in a zip file. I lost the exact error message while originally trying to put this up on paste.ee but everything else should be there.

Let me know if you need anything else, thanks.

Unfortunately there is no bugreport.txt in the DynDOLOD Logs.zip

You changed Debug=1 instead of adding GLDebug=1 in C:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini
The driver version is reported as 582.16. Is there no newer for you card? I doubt it makes a difference, but update to 591.74 if possible just to be sure if nothing else speaks against it.

Download the latest test version from https://dyndolod.info/Downloads/Test-Versions
Set Debug=0 and add GLDebug=1 under [DynDOLOD] in C:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini
Delete all old logs and old bugreport.txt. Then run the test version and upload new logs and bugreport.txt (if it exists).

[strangelyliteral]

The bug report was supposed to have been added to that folder, but I guess it didn't make it into the file after all. Paste.ee keeps rejecting the text, so here it is separately.

In the meantime, I'll try the other fixes you suggested. Thanks for your patience.

[strangelyliteral]

Back again, and thanks for everything so far. The good news is the advice you gave me worked the first time: I upgraded the drivers, added GLDebug=1, and updated to the test version of DynDOLOD, and it ran successfully.

The bad news is I had to re-run DynDOLOD again tonight when I made some tweaks and also realized I hadn't set some of the settings correctly, and now I'm getting a framebuffer error.

Quote

Error: OpenGL: 4AB1255E framebuffer objects unsupported.

Click on this link for additional explanations and help for this message
https://dyndolod.info/Messages/Exceptions

Try clean installing the latest recommended/WHQL (not optional and not beta) graphics drivers only without any bloatware, diable/terminate the bloatware or try to add exceptions to it.

If the issue persists, posts a problem report on the official DynDOLOD support forum.

The advice is the same as the OpenGL error, but I already did all that. I did not generate a bug report this time, but I uploaded the other logs here.

[sheson]

On 1/18/2026 at 8:08 AM, strangelyliteral said:

Back again, and thanks for everything so far. The good news is the advice you gave me worked the first time: I upgraded the drivers, added GLDebug=1, and updated to the test version of DynDOLOD, and it ran successfully.

The bad news is I had to re-run DynDOLOD again tonight when I made some tweaks and also realized I hadn't set some of the settings correctly, and now I'm getting a framebuffer error.

The advice is the same as the OpenGL error, but I already did all that. I did not generate a bug report this time, but I uploaded the other logs here.

GLDebug=1 is ti addsadditional information to the debug log and not some kind of fix.
Unfortunately you didn't upload the logs with it where it ran through.

I uploaded a new test version to https://dyndolod.info/Downloads/Test-Versions
Delete all old logs and old bugreport.txt. Then run the new test version and upload new logs and bugreport.txt (if it exists) in any case.
Still keep GLDebug=1 under [DynDOLOD] in C:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

If the issue still happens, add CPUMipMaps=1 under [DynDOLOD] in C:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini
That should always run through. Upload those logs too.

[strangelyliteral]

When I tried to run DynDOLOD, I got this error: 

Quote

DynDOLOD
Error: Item not found.

Click on this link for additional explanations and help for this message
https://dyndolod.info/Messages/Exceptions
Read this URL to learn what the message means and for hints what to do about it before asking for help with it or before providing help for it.</a>

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

Log and bug report should be properly attached for once.

DynDOLOD_SSE_log.txt bugreport.txt

[sheson]

1 hour ago, strangelyliteral said:

When I tried to run DynDOLOD, I got this error: 

Log and bug report should be properly attached for once.

DynDOLOD_SSE_log.txt 400.94 kB · 0 downloads bugreport.txt 105.39 kB · 0 downloads

You have an outdated test version from several days ago. Download the latest one from https://dyndolod.info/Downloads/Test-Versions

[strangelyliteral]

That fixed it, thanks!

[sheson]

8 hours ago, strangelyliteral said:

That fixed it, thanks!

Great! It would be helpful if you could upload the DynDOLOD log and debug log from the successful run.

[strangelyliteral]

Sure! I suppose you get a lot more buggy logs than successful ones to study once people get their issues fixed. I'm probably going to run it again tonight to make some environmental changes, I'll let you know if there were any issues with that run.

DynDOLOD_SSE_log.txt DynDOLOD_SSE_Debug_log.txt

Edited January 24 by strangelyliteral

[DemonDomain]

Getting the following message with texgen, i have latest gpu drivers, latest dyndolod things and even tried the testversions provided in another post, yet the problem persists

TexGen
Error: OpenGL: 00000500 invalid enumerant from TwbRender.DeleteID while processing D:\TES Tools\DynDOLOD\TexGen_Output\textures\dyndolod\lod\trees\treepineforestbroken06_09e933e6_trunk.

texgen sse and debug logs here

[sheson]

7 hours ago, DemonDomain said:

Getting the following message with texgen, i have latest gpu drivers, latest dyndolod things and even tried the testversions provided in another post, yet the problem persists

TexGen
Error: OpenGL: 00000500 invalid enumerant from TwbRender.DeleteID while processing D:\TES Tools\DynDOLOD\TexGen_Output\textures\dyndolod\lod\trees\treepineforestbroken06_09e933e6_trunk.

texgen sse and debug logs here

Moved to the appropriate thread. See above.

See https://dyndolod.info/Messages/Exceptions#OpenGL

Get the latest test version from https://dyndolod.info/Downloads/Test-Versions.
Delete all old logs.
Add the GLDebug=1 under [TexGen] to D:\TES Tools\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini.
Run again and upload new log, debug log and bugreport.txt if it exists.

[DemonDomain]

the logs i've included should already be ones that had that process done to them, but ill generate new logs in a moment

latest logs here https://drive.google.com/file/d/1pi4wrO-_rSbbN7UMRVAJm4hriIXfwnl-/view?usp=sharing

Edited Wednesday at 09:35 AM by DemonDomain
new link, included bugreport.txt

[DemonDomain]

2 hours ago, sheson said:

Moved to the appropriate thread. See above.

See https://dyndolod.info/Messages/Exceptions#OpenGL

Get the latest test version from https://dyndolod.info/Downloads/Test-Versions.
Delete all old logs.
Add the GLDebug=1 under [TexGen] to D:\TES Tools\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini.
Run again and upload new log, debug log and bugreport.txt if it exists.

ran DDU and installed latest driver with "Driver only" option, i had the same testversion executables prior to my first post, had the GLDebug in TexGen_SSE.ini, but the issue persists.
from what i noticed, it has changed from DeleteID to LoadScene, possibly after running ddu and installing drivers with the driver only-option
First error was as follows:
Error: OpenGL: 00000500 invalid enumerant from TwbRender.DeleteID while processing D:\TES Tools\DynDOLOD\TexGen_Output\textures\dyndolod\lod\trees\treepineforestbroken06_09e933e6_trunk.

Latest one is
Error: OpenGL: 00000500 invalid enumerant from TwbRender.LoadScene for TreePineForestBroken06:3 while processing D:\Outputit\TexGen\textures\dyndolod\lod\trees\treepineforestbroken06_09e933e6_trunk.

newest logs and bugreport here https://drive.google.com/file/d/1xJLpHQZezt7aWeBw8MSws7bkWy4okfIG/view?usp=sharing