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/11/2025 at 8:06 AM, Jaques said:

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.

Expand  

Could you test what happens if you actually hide  textures\landscape\grass\IvyDrJ.dds so it can not be found and is substituted with red default?

[Jaques]

  On 2/11/2025 at 8:54 AM, sheson said:

Could you test what happens if you actually hide  textures\landscape\grass\IvyDrJ.dds so it can not be found and is substituted with red default?

Expand  

I hid IvyDrJ.dds in MO2 (and also IvyDrJ_D.dds), but it failed on freak's floral fields.esp\ivydrj_000008ff. I then opened freak's floral fields.esp in SSEEdit and found freak's 000008ff which was pointing to IvyDrJ.dds, so I removed it and ran TexGen again. This time it failed on freak's floral fields.esp\ivydrj_000009db_1, which also pointed to IvyDrJ.dds, so I removed that and, just to save some time because xEdit is slow in Linux, I removed two other references to anything starting with IvyDrJ. This time TexGen completed with no additional flags in TexGen_SSE.ini

I don't have any idea what exactly is malformed about IvyDrJ.dds, but it's clearly something. I also don't know what the consequences of removing those references from the esp will be, I may just restore the original and use the edited one only to run TexGen for now until that texture can be fixed.

Thank you so much for your help, I am truly impressed by the scope and longevity of this undertaking.

Edit: here are the logs if you wanted to see them

Edited February 11 by Jaques

[sheson]

  On 2/11/2025 at 8:14 PM, Jaques said:

I hid IvyDrJ.dds in MO2 (and also IvyDrJ_D.dds), but it failed on freak's floral fields.esp\ivydrj_000008ff. I then opened freak's floral fields.esp in SSEEdit and found freak's 000008ff which was pointing to IvyDrJ.dds, so I removed it and ran TexGen again. This time it failed on freak's floral fields.esp\ivydrj_000009db_1, which also pointed to IvyDrJ.dds, so I removed that and, just to save some time because xEdit is slow in Linux, I removed two other references to anything starting with IvyDrJ. This time TexGen completed with no additional flags in TexGen_SSE.ini

I don't have any idea what exactly is malformed about IvyDrJ.dds, but it's clearly something. I also don't know what the consequences of removing those references from the esp will be, I may just restore the original and use the edited one only to run TexGen for now until that texture can be fixed.

Thank you so much for your help, I am truly impressed by the scope and longevity of this undertaking.

Edit: here are the logs if you wanted to see them

Expand  

Well, remember my mantra, removing something is just a troubleshooting step. We haven't found out the actual issue, yet. if the result works for you without visual issues it is OK to move on.

If I am reading this right you removed the grass records with xEdit. I was initially thinking to only hide the texture being used, so it report it as file not find. Doesn't matter, if everything else ran through without a problem that narrowed it down close enough for now.

If you could upload the winning textures\landscape\grass\IvyDrJ.dds and meshes\landscape\grass\IvyDrJ.nif you currently have so I can compare them to what I have. Maybe they are not the same that I have.

[Jaques]

  On 2/11/2025 at 8:58 PM, sheson said:

Well, remember my mantra, removing something is just a troubleshooting step. We haven't found out the actual issue, yet. if the result works for you without visual issues it is OK to move on.

If I am reading this right you removed the grass records with xEdit. I was initially thinking to only hide the texture being used, so it report it as file not find. Doesn't matter, if everything else ran through without a problem that narrowed it down close enough for now.

If you could upload the winning textures\landscape\grass\IvyDrJ.dds and meshes\landscape\grass\IvyDrJ.nif you currently have so I can compare them to what I have. Maybe they are not the same that I have.

Expand  

I did initially run it with them hidden in MO2, but it still failed reporting freak's floral fields.esp\ivydrj_000008ff as the issue, which is what lead me to removing that and the other records. Would this indicate there might be something wrong with the esp rather than the texture? Here are the winning files I saved from Explorer++ in the vfs.

[sheson]

  On 2/11/2025 at 9:18 PM, Jaques said:

I did initially run it with them hidden in MO2, but it still failed reporting freak's floral fields.esp\ivydrj_000008ff as the issue, which is what lead me to removing that and the other records. Would this indicate there might be something wrong with the esp rather than the texture? Here are the winning files I saved from Explorer++ in the vfs.

Expand  

Good to know and thanks. I'll have look.
The used data from the plugin is just the NIF and the form id for the filename to create. OpenGL should only be affected by the NIF and texture directly.

[sheson]

  On 2/11/2025 at 9:22 PM, sheson said:

Good to know and thanks. I'll have look.
The used data from the plugin is just the NIF and the form id for the filename to create. OpenGL should only be affected by the NIF and texture directly.

Expand  

The assets are fine, just the same I have when installing the 4K option which just run through regardless of TexGen INI being default or using any of the settings so far. I might have another test version some time in the future, with probably more debug message for me to analyze. So check back in a couple days.

If you like you could try to test what happens if you install the 2K option, it might mean less stress, time, different order of things.

[Jaques]

  On 2/12/2025 at 9:31 AM, sheson said:

The assets are fine, just the same I have when installing the 4K option which just run through regardless of TexGen INI being default or using any of the settings so far. I might have another test version some time in the future, with probably more debug message for me to analyze. So check back in a couple days.

If you like you could try to test what happens if you install the 2K option, it might mean less stress, time, different order of things.

Expand  

Ok, that's good to know, I switched to WIldlands Renewal from FFF to test, but I kept having issues where Texconvx64 would hang in seemingly random spots. I've started Dyndolod maybe 20 times without a success, so I don't think I'm just going to get lucky once, although I have in the past. I think it might just be an issue with TexConvx64 running in MO2's USVFS emulated through Proton/Wine because I switched to DXT5/DXT1 from BC7 as you suggested here and it completed first time, no problem. xEdit's background loader is probably also slowed down by USVFS performance in Proton/Wine. You also suggested to use LockTexconv=1, which I didn't try, but could also be more stable. It could also be my VCRedist was too old, it was 14.38.33135 from March 2024 and the current version is 14.42.34438.

[sheson]

  On 2/13/2025 at 8:06 AM, Jaques said:

Ok, that's good to know, I switched to WIldlands Renewal from FFF to test, but I kept having issues where Texconvx64 would hang in seemingly random spots. I've started Dyndolod maybe 20 times without a success, so I don't think I'm just going to get lucky once, although I have in the past. I think it might just be an issue with TexConvx64 running in MO2's USVFS emulated through Proton/Wine because I switched to DXT5/DXT1 from BC7 as you suggested here and it completed first time, no problem. xEdit's background loader is probably also slowed down by USVFS performance in Proton/Wine. You also suggested to use LockTexconv=1, which I didn't try, but could also be more stable. It could also be my VCRedist was too old, it was 14.38.33135 from March 2024 and the current version is 14.42.34438.

Expand  

Maybe the slow disk is due to not using the noatime mounting option or maybe because of compression, though that should not be affecting just reading data that much.

I would also test what happens if texconv uses CPU instead of GPU with TexconvAdapterIndex=-1. It will be slower when compressing to BC7, though.

Edit: Test with latest Alpha version.

[Shiho]

I consistently get the following error trying to run TexGen.

 

Error: OpenGl: Invalid operation
...\floral fields.esp\ ivydrj_d_00000abc_1
while processing
...\floral fields.esp\ivydrj_d_00000abc

 

Freaks Floral Fields author said I should come here for help, even tho I'm sure its a problem with that Texture from that Mod.

If I disable grass on the Textgen UI it runs fine.

Other people in the Nexus discussion report similar Problems and "just keep trying" until the Error magically does not not appear anymore.

Some of the even report success.

I tried 20+ times, every time failing on this texture, removing it from the mod didn't help.

 

Tried everything in the  https://dyndolod.info/Help

Used to operate Dyndolod and Textgen fine for years, just since the new modlist this with FFF appears.

 

 

Bugreport.txt https://ufile.io/92fwzn4e

 

Debug Log: https://ufile.io/sjq9wi4m

 

Log: https://ufile.io/pihvhxgd

[sheson]

  On 4/10/2025 at 3:01 PM, Shiho said:

I consistently get the following error trying to run TexGen.

 

Error: OpenGl: Invalid operation
...\floral fields.esp\ ivydrj_d_00000abc_1
while processing
...\floral fields.esp\ivydrj_d_00000abc

 

Freaks Floral Fields author said I should come here for help, even tho I'm sure its a problem with that Texture from that Mod.

If I disable grass on the Textgen UI it runs fine.

Other people in the Nexus discussion report similar Problems and "just keep trying" until the Error magically does not not appear anymore.

Some of the even report success.

I tried 20+ times, every time failing on this texture, removing it from the mod didn't help.

 

Tried everything in the  https://dyndolod.info/Help

Used to operate Dyndolod and Textgen fine for years, just since the new modlist this with FFF appears.

 

 

Bugreport.txt https://ufile.io/92fwzn4e

 

Debug Log: https://ufile.io/sjq9wi4m

 

Log: https://ufile.io/pihvhxgd

Expand  

I suggest to ignore everything posted by random people on third party forums.
I suggest to first investigate and fix whatever is causing xEdit to take 15 minutes to load.

If you removed the texture, wasn't there a different error, like for a different texture?

See posts above. Start by testing with adding RenderSingle=1 under [TexGen] in Z:\home\shiho\Games\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini
If the same error still happens also add RenderBillboardsSingleThread=1. If there still is an error add GLDebug=1 and upload new logs.

[Shiho]

The Error still persists.

Here are the new logs: https://www.mediafire.com/file/bwluqqhtau3hscm/Logs.zip/file

 

 

 

[sheson]

  On 4/11/2025 at 12:18 AM, Shiho said:

The Error still persists.

Here are the new logs: https://www.mediafire.com/file/bwluqqhtau3hscm/Logs.zip/file

Expand  

Download this test version https://mega.nz/file/9Eo0ADga#qlf_rWNmTzRlMVtMs04lmcBQCb_RvEyT40jShtMrUX0
Delete all old logs and bugreport.txt. Run test version. Only check to generate grass HD and nothing else. Upload new logs if problem persists.

[Shiho]

Unfortunately, still the same error.

 

https://www.mediafire.com/file/fq8xec78n8yk8r5/NewLogs.zip/file

[sheson]

  On 4/15/2025 at 1:02 AM, Shiho said:

Unfortunately, still the same error.

https://www.mediafire.com/file/fq8xec78n8yk8r5/NewLogs.zip/file

Expand  

Please run this test version https://mega.nz/file/9QRCWKhT#Oa7KmQjKNXkjPIZd_wWDQv2uYPkP0Rvjx5reKquJJQI and upload new logs.

[Shiho]

Here you go, same error:

https://www.mediafire.com/file/a866emmjxcs0sav/NewNewlogs.zip/file