Error: OpenGL: framebuffer objects unsupported

[Kattmandu]

Persistent OpenGL error.  Not always on the same file however.

[02:04] Error: OpenGL: F:\Tools\DynDOLOD\TexGen_Output\textures\lod\largeimperialtentlod framebuffer objects unsupported.

[02:06] Error: OpenGL: F:\Tools\DynDOLOD\TexGen_Output\textures\lod\whtrimstone1lod framebuffer objects unsupported.

Clicking on links in error message window does not open anything.

Clean installed Nvidia graphics driver v565.90 (WHQL) without any "bloatware".

Restarted computer twice.

Using:

DynDOLOD DLL NG and Scripts 3.00 Alpha 33

DynDOLOD Resources SE 3.00 Alpha 53

DynDOLOD 3.00 Alpha 181

 

Log files:

TexGen_SSE_log.txtFetching info...

TexGen_SSE_Debug_log.txtFetching info...

Edited October 10, 2024 by Kattmandu

[sheson]

  On 12/29/2024 at 11:02 AM, Fiery said:

Hello, I am getting an error when generating TexGen and I have no clue how to fix. This is with 3.0.182

"Error: OpenGL:F:\GameTools\DynDOLOD\TexGen_Output\textures\lod\sdragontile01lodframebufferobjects unsupported." Also it talks about doing a clean install of WHQL, which I have no idea what that is and doing a google of that was useless. Can anyone tell me what this is in regards to? I have had this problem for 3 months so been back on an older version but now when I try to launch the problem free older version it warns me its out of date and all I can do is close it down. So now Tex Gen and Dyndolod is utterly broken for me. 

Expand  

Moved to the related thread.

Use the "Copy this message to clipboard" to copy and paste the text of a message instead of posting a screenshot of text. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text

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

Use the test version from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/2/#findComment-282545 and check if it works.

"not optional and not beta" means the latest official driver release.
"Recommended" would be the latest release driver directly from the Hardware Vender.
"WHQL" is generally what installs with Windows Update.

https://learn.microsoft.com/en-us/windows-hardware/drivers/install/whql-release-signature
"Windows Hardware Quality Labs"

https://www.google.com/search?q=whql

[Link01000]

Apologies if this is the wrong place to post, but I am also having OpenGL issues with Texgen. I'm on Linux. I've added the latest version of Texgen and Texconv64 listed in previous posts, and have also added RenderSingle=1 and RenderTexturesSingleThread=1 to my ini file.  When I add RenderBillboardsSingleThread=1 Texgen just ends abruptly and says that it completed successfully when it really hasn't. I'll upload logs for all of them.

Here is the message I get with RenderSingle=1 and RenderTexturesSingleThread=1 added to my ini (the same message I was getting before adding those lines and before trying the newer versions linked in previous posts).

Error: OpenGL: invalid operation while processing Z:\media\zach\External-Storage\Modding\Skyrim SE\tools\DynDOLOD\TexGen_Output\textures\terrain\lodgen\blubbos_cities_seasonsofskyrim.esp\blubbo_riverwood_birch_variation_a02_green2_win_00000862.

logs/bug report files when RenderBillboardsSingleThread=1 is NOT on 

logs when RenderBillboardsSingleThread=1 is turned on. No bug report file is generated.

[sheson]

  On 1/3/2025 at 5:23 PM, Link01000 said:

Apologies if this is the wrong place to post, but I am also having OpenGL issues with Texgen. I'm on Linux. I've added the latest version of Texgen and Texconv64 listed in previous posts, and have also added RenderSingle=1 and RenderTexturesSingleThread=1 to my ini file.  When I add RenderBillboardsSingleThread=1 Texgen just ends abruptly and says that it completed successfully when it really hasn't. I'll upload logs for all of them.

Here is the message I get with RenderSingle=1 and RenderTexturesSingleThread=1 added to my ini (the same message I was getting before adding those lines and before trying the newer versions linked in previous posts).

Error: OpenGL: invalid operation while processing Z:\media\zach\External-Storage\Modding\Skyrim SE\tools\DynDOLOD\TexGen_Output\textures\terrain\lodgen\blubbos_cities_seasonsofskyrim.esp\blubbo_riverwood_birch_variation_a02_green2_win_00000862.

logs/bug report files when RenderBillboardsSingleThread=1 is NOT on 

logs when RenderBillboardsSingleThread=1 is turned on. No bug report file is generated.

Expand  

Delete old logs. Run the test version with only adding GLListDebug=1 and GLDebug=1 and none of the other settings to the TexGen_SSE.IN. Upload the new logs.

[foxnne]

Hello!

I have been using Dyndolod for years now without issue but I just hit an error I can't seem to get around with the latest alpha 182.

The error I get is during running TexGen64 on my modlist and after 2-3 minutes I get the following error:

Error: OpenGL: D:\Games\Skyrim Special Edition Modding\Tools\DynDOLOD\TexGe...\mrkstoneblocks3lod
framebuffer objects unsupported.

I've tried updating drivers and removing crapware as suggested, but I can't seem to get around this one.

This is the TexGen_SSE_log.txt

This is the TexGen_SSE_Debug_log.txt

[sheson]

  On 1/4/2025 at 3:23 PM, foxnne said:

Hello!

I have been using Dyndolod for years now without issue but I just hit an error I can't seem to get around with the latest alpha 182.

The error I get is during running TexGen64 on my modlist and after 2-3 minutes I get the following error:

Error: OpenGL: D:\Games\Skyrim Special Edition Modding\Tools\DynDOLOD\TexGe...\mrkstoneblocks3lod
framebuffer objects unsupported.

I've tried updating drivers and removing crapware as suggested, but I can't seem to get around this one.

This is the TexGen_SSE_log.txt

This is the TexGen_SSE_Debug_log.txt

Expand  

Moved to the appropriate thread for the message. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search

Use the test version from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/2/#findComment-282545 and check if it works.

[foxnne]

With the test version I got this error:

Error: OpenGL: invalid operation for D:\Games\Skyrim Special Edition Modding\Tools\DynDOLOD\DynDOLOD\TexGen_Output\textures\terrain\lodgen\gray fox flora overhaul.esp\gkbjungletreenew19v2tropical_00000a46_1 while processing D:\Games\Skyrim Special Edition Modding\Tools\DynDOLOD\DynDOLOD\TexGen_Output\textures\terrain\lodgen\gray fox flora overhaul.esp\gkbjungletreenew19v2tropical_00000a46.

Logs

[foxnne]

LockTexconv=1
RenderSingle=1
RenderTexturesSingleThread=1
GLDebug=1
RenderBillboardsSingleThread=1

With the above in the ini it finished successfully with the test version, attempting to run DynDOLOD now.

[Link01000]

  On 1/4/2025 at 8:09 AM, sheson said:

Delete old logs. Run the test version with only adding GLListDebug=1 and GLDebug=1 and none of the other settings to the TexGen_SSE.IN. Upload the new logs.

Expand  

Okay, here are the logs from following those instructions. It failed almost immediately upon starting.

[sheson]

  On 1/4/2025 at 5:39 PM, foxnne said:

With the test version I got this error:

Error: OpenGL: invalid operation for D:\Games\Skyrim Special Edition Modding\Tools\DynDOLOD\DynDOLOD\TexGen_Output\textures\terrain\lodgen\gray fox flora overhaul.esp\gkbjungletreenew19v2tropical_00000a46_1 while processing D:\Games\Skyrim Special Edition Modding\Tools\DynDOLOD\DynDOLOD\TexGen_Output\textures\terrain\lodgen\gray fox flora overhaul.esp\gkbjungletreenew19v2tropical_00000a46.

Logs

Expand  

The uploaded logs only show TexGen being started, the message about old TexGen output still being active shown and then TexGen being closed.

Delete old logs.
Download and run the latest test version from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/2/#findComment-282545.
Only set GLDebug=1 in case there is still an error and then upload the new logs.

  On 1/4/2025 at 6:08 PM, foxnne said:

LockTexconv=1
RenderSingle=1
RenderTexturesSingleThread=1
GLDebug=1
RenderBillboardsSingleThread=1

With the above in the ini it finished successfully with the test version, attempting to run DynDOLOD now.

Expand  

Use one setting at a time to see which one actually has an effect. Typically start with RenderSingle=1. If there still is an error, the next setting depends on the error.

[sheson]

  On 1/4/2025 at 8:54 PM, Link01000 said:

Okay, here are the logs from following those instructions. It failed almost immediately upon starting.

Expand  

Test what happens with the latest test version from https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/2/#findComment-282545.
Upload new logs with GLDebug=1.
If the problem still happens, check and report if setting RenderSingle=1 makes a difference.

 

[Link01000]

  On 1/5/2025 at 11:15 AM, sheson said:

Test what happens with the latest test version from https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/page/2/#findComment-282545.
Upload new logs with GLDebug=1.
If the problem still happens, check and report if setting RenderSingle=1 makes a difference.

 

Expand  

I'm pretty sure I am already on the latest version you linked, but I redownloaded it just to be sure. Here are the logs for that run.

bugreport.txt      Texgen_SSE_log.txt

------------------------------------------------------------

Here are the logs from the run with RenderSingle=1 on. I still ran it with GLDebug=1 on, wasn't sure if you wanted me to turn that one off or not.

bugreport.txt       https://paste.ee/p/701Ic

------------------------------------------------------------

 

Texgen_SSE_Debug_Log.txt was to large for pastee, and ufile is not working for me right now, but I still have the log file if you need it.

 

[sheson]

  On 1/5/2025 at 10:05 PM, Link01000 said:

I'm pretty sure I am already on the latest version you linked, but I redownloaded it just to be sure. Here are the logs for that run.

bugreport.txt      Texgen_SSE_log.txt

------------------------------------------------------------

Here are the logs from the run with RenderSingle=1 on. I still ran it with GLDebug=1 on, wasn't sure if you wanted me to turn that one off or not.

bugreport.txt       https://paste.ee/p/701Ic

------------------------------------------------------------

Texgen_SSE_Debug_Log.txt was to large for pastee, and ufile is not working for me right now, but I still have the log file if you need it.

Expand  

The version in the post is updated every now and then.

The message "Unable to read VR Path Registry" seems odd. Not sure if related or what to do about it, as I do not have VR equipment to test in that environment. Try running MO2 and tools without Steam client running maybe check or reinstall Steam VR etc.

Add GLListDebug=1 to the TexGen_SSE.INi and upload new bugreport.txt and logs, including the debug please.

Then test if adding RenderBillboardsSingleThread=1 makes a difference.

[Link01000]

  On 1/6/2025 at 9:40 AM, sheson said:

The version in the post is updated every now and then.

The message "Unable to read VR Path Registry" seems odd. Not sure if related or what to do about it, as I do not have VR equipment to test in that environment. Try running MO2 and tools without Steam client running maybe check or reinstall Steam VR etc.

Add GLListDebug=1 to the TexGen_SSE.INi and upload new bugreport.txt and logs, including the debug please.

Then test if adding RenderBillboardsSingleThread=1 makes a difference.

Expand  

I ran these runs in a vanilla setup to make it faster, but the errors were the same so I don't think that should make a difference. 

I agree that the VR path message is odd, considering I have never used a VR headset with this computer and am using Skyrim SSE, not VR. I closed steam nontheless on both runs.

Here are the logs from the run with GLListDebug=1 added

Here are the logs from the run with RenderBillboardsSingleThread=1 added

[sheson]

  On 1/7/2025 at 12:22 AM, Link01000 said:

I ran these runs in a vanilla setup to make it faster, but the errors were the same so I don't think that should make a difference. 

I agree that the VR path message is odd, considering I have never used a VR headset with this computer and am using Skyrim SSE, not VR. I closed steam nontheless on both runs.

Here are the logs from the run with GLListDebug=1 added

Here are the logs from the run with RenderBillboardsSingleThread=1 added

Expand  

The second link links to this forum instead of filebin.

[Link01000]

  On 1/7/2025 at 7:06 AM, sheson said:

The second link links to this forum instead of filebin.

Expand  

Sorry about that, here is the correct link for the run with RenderBillboardsSingleThread=1