Jump to content

All Activity

This stream auto-updates

  1. Today
  2. 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.
  3. 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. 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.
  4. Make sure d:\documents is not defined as a special Windows folder for documents - it is not what opens if clicking "Documents" in Windows Explorer left Check the Windows Event log for related messages. Make sure the PC is stable with prime95, OCCT etc.
  5. See out INI guide on iShadowMapResolution. Use values divisible by 8, or that match common texture sizes. Are you using BethINI Pie? If not, then try that and then get back into the ENB stuff you were tweaking. Here's our recommended settings guide for BethINI. I recommend setting the BethINI Ultra preset if you have a powerful PC, but otherwise, follow that BethINI guide exactly. It will ensure you have sane settings. Manually managing the game INI settings can cause strange GFX anomalies if even one or two specific settings are not kosher. Environment, Shadows, Visuals, and View Distance sections are particularly important, but so are the others, especially if running ENB.
  6. Unfortunately, the only solution I have found so far is setting shadow resolution to 8192, luckily I can run it but it is not ideal.
  7. I'm not so sure, when I disable "UseEffect" under the global tab, the problem still persists.
  8. Yesterday
  9. Tried to reproduce bug 5 times, seems like it fixed.
  10. https://ufile.io/q6j28bsx - Here is the realtime log
  11. Okay, here are the logs from following those instructions. It failed almost immediately upon starting.
  12. 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.
  13. 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
  14. 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.
  15. 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
  16. New test version https://mega.nz/file/dVgAwAoJ#GmQw40JxwOm3CSHB7AchNKUFDfE8OZieUNwilCDWC8Q Same procedure...
  17. No difference https://drive.google.com/file/d/1oRqOvlz73BB1BlcZiL9qiSsUKo-xO_1m/view?usp=sharing
  18. Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts. See https://dyndolod.info/Messages/Textures-Do-Not-Match There are outdated LOD models in the load order or full models have been replaced without providing updated LOD models. Outdated or not properly made LOD models might still work fine in many cases ... If and only if there are obvious differences of the textures between full models and LOD models, the log messages can aid in quickly finding the reason... If there are no obvious differences of the textures between full models and LOD models, then nothing else needs to be done. Also see https://dyndolod.info/Mods/Majestic-Mountains
  19. Hello. I have a long modlist among which I use Majestic Mountains, Simplicity of Snow, and wizkid's Snowy Surfaces Sound Collision and Aesthetics. When I run DynDoLOD I see lots of warning messages about wizkid's mod, like this: [00:30] <Warning: Textures do not match for "RockAnimalDen01:0 - L2_RockAnimalDen:0": textures\landscape\snow01.dds in rockanimalden01.nif -> textures\landscape\dirt02.dds in rockanimalden01_lod_0.nif for WIZ_FoscsF.esp WIZ_RockAnimalDenSnow01_HeavySN [STAT:FE0E1830]> [00:30] <Warning: Textures do not match for "MountainTrim03:4": textures\landscape\snow01.dds in mountaintrim03.nif -> textures\landscape\dirt02.dds in mountaintrim03_lod_0.nif for WIZ_FoscsF.esp WIZ_MountainTrim03_LightSN [STAT:FE0E1834]> [00:30] <Warning: Textures do not match for "MountainTrim03:4": textures\landscape\snow01.dds in mountaintrim03.nif -> textures\landscape\dirt02.dds in mountaintrim03_lod_1.nif for WIZ_FoscsF.esp WIZ_MountainTrim03_LightSN [STAT:FE0E1834]> [00:30] <Warning: Textures do not match for "MountainTrim03:4": textures\landscape\snow01.dds in mountaintrim03.nif -> textures\landscape\dirt02.dds in mountaintrim03_lod_2.nif for WIZ_FoscsF.esp WIZ_MountainTrim03_LightSN [STAT:FE0E1834]> [00:30] <Warning: Textures do not match for "RockPileL04:0": textures\landscape\snow01.dds in rockpilel04.nif -> textures\landscape\dirt02.dds in rockpilel04_lod_0.nif for WIZ_FoscsF.esp WIZ_RockPileL04DirtSnowPath [STAT:FE0E183C]> [00:31] <Warning: Textures do not match for "RockCliff02:0": textures\landscape\snow01.dds in rockcliff02.nif -> textures\landscape\dirt02.dds in rockcliff02_lod_1.nif for WIZ_FoscsF.esp WIZ_RockCliff02Snow01 [STAT:FE0E180F]> I'm not sure I understand what this means (the mod is using a dirt texture instead of the right one?). It is harmless or should I uninstall that mod?
  20. No time to confirm on my end right now, but this seems like an ENB-specific issue, so I would post your example on the ENB Discord. It seems like as total shadows increase (due to setting max distance), shadow quality reduces. Please let us know what you learn.
  21. Download this test version of DynDOLOD.DLL NG https://mega.nz/file/hFZlmTra#TqWZmPc4g4dvs1WXz3oPxb0VVdZyNPrgjjN1u3HD1pU Replace the one in the ..\SKSE\Plugins\ folder. Check if it makes a difference in the game. Upload c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log
  22. 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.
  23. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to enable the realtime log and how to check the Windows Event log for hints in case DynDOLOD is being terminated prematurely.
  24. Using PI-CHO ENB, Azurite weathers, evlas, with or without soft shadows, default soft shadows ini or edited. 4096 shadow resolution, with first slice at ~2200. I followed STEPs guide on shadow ini settings. I seem to have narrowed it down to being a problem with shadow distance as seen in video, but I can't imagine other people also have the same problem as it ONLY occurs when the camera is near the shadow:
  25. Hello, I have been using Dyndolod for my new mod list for the past week, after adding some miscellaneous mods, Dyndolod has started doing a weird thing where once it gets to start gathering references, it just closes itself, no log is generated except for a couple that I will attach, no output is generated either. Using MO2 as a mod manager. Modlist(NSFW): https://docs.google.com/spreadsheets/d/1T4VXMKHpKsgX1B3L-3umq_BsBAvWiz2Ep5RUugmDJf8/edit?usp=sharing Logs(everything but normal and debug logs since those are not up to date with the latest run): https://ufile.io/f/gyh5x Sorry if this feels very vague, I will try to upload more logs if needed and follow the tips given on the website while I try to fix the issue.
  26. Last week
  27. 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.
  28. Is "what" installed correctly? If you have questions about third party mods, then refer to their installation instructions, ask their author. The right Window data tab seems to show resources for 3D tree LOD generation from Happy Little Trees Add-On - DynDOLOD 3. They are supposed to be installed as any other mod, so that seems to be the case. To generate TexGen output, click the Start button to the lower right as shown in the already linked page https://dyndolod.info/Help/TexGen and section https://dyndolod.info/Help/TexGen#Start. The log files will be in the the ..\DynDOLOD\Logs\ folder after closing the tool as explained in the already linked section https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
  1. Load more activity
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.