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 2/8/2025 at 5:17 PM, dreadflopp said:

It is an integrated card but it doesn't seem possible to dedicate more memory to it than what it currently has, 8.1 GB. I added -memory parameter, changed compression type as suggested and added TextureCache=10. Same error. I checked the memory when generating textures, and TextGen uses up all available vram (8 GB) which causes the driver to reset and TextGen to crash. I tried with the version from Nexus, it never uses more than 1.6 GB vram so there seems to be a problem with your test version. I still had -memory and TextureCache=10 but had changed back the compression type to default when i used the Nexus version.

Expand  

Upload the log and debug log from the all the generations..

Is VRAM slowly rising or is it a spike?

Test with KeepRenderer=1

[dreadflopp]

You have some logs above with different parameters. I am attaching 2 sets of logs. One is for the nexus version of TextGen64.exe, which completed successfully while using at most 1.6 GB of vram. The other log is a realtime log with the test version that you linked in a few posts above. It uses up all available vram, 8.1 GB and then crashes when the display driver restarts. No other log is created by TextGen because of the crash.

TextGen_nexusVersion.zipFetching info... TextGen_testVersion.zipFetching info...

[dreadflopp]

  On 2/8/2025 at 6:40 PM, sheson said:

Upload the log and debug log from the all the generations..

Is VRAM slowly rising or is it a spike?

Test with KeepRenderer=1

Expand  

Sorry, missed the last two rows of your message. It slowly rises, no spike. I'll try with KeepRenderer=1 .

 

[dreadflopp]

Here you go, log with KeepRenderer=1. TextGen crashed soonly a realtime log was available.

TexGen_SSE_realtime_log.zipFetching info...

[sheson]

  On 2/8/2025 at 7:55 PM, dreadflopp said:

Here you go, log with KeepRenderer=1. TextGen crashed soonly a realtime log was available.

TexGen_SSE_realtime_log.zip 1.03 MB · 0 downloads

Expand  

Try new test version from https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/#findComment-282545
Restore default INI, delete old logs.

[dreadflopp]

This new test version completed successfully. It used at most about 2 GB of vram.

Log: https://paste.ee/p/SlxEzt8U

I'll continue with Dyndolod to see this fixes my initial problem, the red colored lods.

TexGen_SSE_Debug_log.zipFetching info...

[Jaques]

  On 2/7/2025 at 7:34 AM, sheson said:

You don't seem to be running the latest version from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/#findComment-282545

It should report as TexGen 3.0 Alpha-182 x64 - Skyrim Special Edition (SSE) (D0555D55) for the first log line.

Expand  

Oh, my bad, I wasn't aware that these links were being updated. I downloaded the current one, which is apparently (7BBE1DF2), not (D0555D55) based on my linked log files.

[sheson]

  On 2/8/2025 at 10:44 PM, Jaques said:

Oh, my bad, I wasn't aware that these links were being updated. I downloaded the current one, which is apparently (7BBE1DF2), not (D0555D55) based on my linked log files.

Expand  

Yeah it kind of constantly gets updated. See recent posts where I ask users to download latest test version.

Does it run through with just RenderBillboardsSingleThread=1?

[Jaques]

  On 2/9/2025 at 5:23 PM, sheson said:

Yeah it kind of constantly gets updated. See recent posts where I ask users to download latest test version.

Does it run through with just RenderBillboardsSingleThread=1?

Expand  

No, it still crashes during billboard generation, logs are here

[sheson]

  On 2/10/2025 at 9:54 AM, Jaques said:

No, it still crashes during billboard generation, logs are here

Expand  

The textures\landscape\grass\IvyDrJ.dds is from Freaks' Floral Fields and the meshes\landscape\grass\IvyDrJ.nif is from  Cathedral - 3D Landscapes and Grass Library right?

[yakmods]

@shesonwas the texgen test version removed? I wanted to test the latest since I noticed some more red windows and wanted to collect some data/logs.

[Jaques]

  On 2/10/2025 at 10:02 AM, sheson said:

The textures\landscape\grass\IvyDrJ.dds is from Freaks' Floral Fields and the meshes\landscape\grass\IvyDrJ.nif is from  Cathedral - 3D Landscapes and Grass Library right?

Expand  

Correct, I have the meshes only version of Cathedral - 3D Landscapes and Grass Library as specified in Freak's Floral Fields. I noticed there was an update a couple days ago to Cathedral - 3D Landscapes and Grass Library, so I downloaded it and ran it again, but it crashed on that same texture.

[sheson]

  On 2/10/2025 at 10:20 PM, yakmods said:

@shesonwas the texgen test version removed? I wanted to test the latest since I noticed some more red windows and wanted to collect some data/logs.

Expand  

Use latest Alpha-184 for now. That TexGen is what the last test version was. Potential new test version will be based on that release.

[sheson]

  On 2/11/2025 at 5:35 AM, Jaques said:

Correct, I have the meshes only version of Cathedral - 3D Landscapes and Grass Library as specified in Freak's Floral Fields. I noticed there was an update a couple days ago to Cathedral - 3D Landscapes and Grass Library, so I downloaded it and ran it again, but it crashed on that same texture.

Expand  

Does the error also happen with RenderSingle=1 and RenderBillboardsSingleThread=1?

What Linux are you using? I am just not able to brute for the issue here in Windows and my Linux. The used version itself is probably not really relevant, just curious.

[Jaques]

  On 2/11/2025 at 7:17 AM, sheson said:

Does the error also happen with RenderSingle=1 and RenderBillboardsSingleThread=1?

What Linux are you using? I am just not able to brute for the issue here in Windows and my Linux. The used version itself is probably not really relevant, just curious.

Expand  

Yes, I just ran again with both of those, here are the logs. I'm using Fedora 41, currently kernel 6.12, with the Mesa 24.3.4 driver, pretty standard, hopefully it can be useful.