Kattmandu Posted October 10, 2024 Posted October 10, 2024 (edited) 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.txt TexGen_SSE_Debug_log.txt Edited October 10, 2024 by Kattmandu
0 sheson Posted December 29, 2024 Posted December 29, 2024 53 minutes ago, 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. 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
0 Link01000 Posted Friday at 05:23 PM Posted Friday at 05:23 PM 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.
0 sheson Posted Saturday at 08:09 AM Posted Saturday at 08:09 AM 14 hours ago, 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. 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.
0 foxnne Posted Saturday at 03:23 PM Posted Saturday at 03:23 PM 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
0 sheson Posted Saturday at 04:28 PM Posted Saturday at 04:28 PM 1 hour ago, 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 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.
0 foxnne Posted Saturday at 05:39 PM Posted Saturday at 05:39 PM 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
0 foxnne Posted Saturday at 06:08 PM Posted Saturday at 06:08 PM 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.
0 Link01000 Posted Saturday at 08:54 PM Posted Saturday at 08:54 PM 12 hours ago, 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. Okay, here are the logs from following those instructions. It failed almost immediately upon starting.
0 sheson Posted Sunday at 09:30 AM Posted Sunday at 09:30 AM 15 hours ago, 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 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. 15 hours ago, 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. 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.
0 sheson Posted Sunday at 11:15 AM Posted Sunday at 11:15 AM 12 hours ago, Link01000 said: Okay, here are the logs from following those instructions. It failed almost immediately upon starting. 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.
0 Link01000 Posted Sunday at 10:05 PM Posted Sunday at 10:05 PM 10 hours ago, 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. 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.
0 sheson Posted Monday at 09:40 AM Posted Monday at 09:40 AM 11 hours ago, 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. 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.
0 Link01000 Posted yesterday at 12:22 AM Posted yesterday at 12:22 AM 14 hours ago, 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. 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
0 sheson Posted yesterday at 07:06 AM Posted yesterday at 07:06 AM 6 hours ago, 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 The second link links to this forum instead of filebin.
0 Link01000 Posted 10 hours ago Posted 10 hours ago 16 hours ago, sheson said: The second link links to this forum instead of filebin. Sorry about that, here is the correct link for the run with RenderBillboardsSingleThread=1
Question
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.txt
TexGen_SSE_Debug_log.txt
Edited by KattmanduTop Posters For This Question
47
5
5
4
Popular Days
Oct 14
13
Dec 16
9
Oct 10
7
Jan 4
6
Top Posters For This Question
sheson 47 posts
Coffee2a 5 posts
Link01000 5 posts
Kattmandu 4 posts
Popular Days
Oct 14 2024
13 posts
Dec 16 2024
9 posts
Oct 10 2024
7 posts
Jan 4 2025
6 posts
Popular Posts
sheson
If you do not select tree LOD billboards it runs through? Add GLListDebug=1 to the TexGen INI and upload new logs. I wonder if using driver version 561.09 makes a difference.
sheson
Both debugs logs show that both RenderSingle=0 and RenderTexturesSingleThread=0 are set. You do not seem to be using the test version from https://stepmodifications.org/forum/topic/20153-error-op
sheson
Moved to the appropriate thread for the error message. Use search as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search. See posts above. Try the test version from http
Posted Images
106 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now