Jump to content

sheson

Mod Author
  • Posts

    13,377
  • Joined

  • Last visited

  • Days Won

    445

Everything posted by sheson

  1. Yes. It should. If not, make a bug report.
  2. For future reference, also upload the normal DynDOLOD log in addition to the debug log. Is this exact error repeatable? It seems a bit random, like there might be hardware issues, like unstable CPU or memory, BIOS settings for example. Test PC with prime95/OCCT. Delete old bugreport.txt, old logs and run the test version from this post https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-183/page/689/#findComment-284419 and upload new log, debug log and bugreport.txt if it still happens.
  3. The check exists to make sure there is nothing bad happening when updating existing DynDOLOD output. You are asking for a feature for a check that should not really report more than one file in the first place. So my guess is, it is because of mod(s). Which means somebody tries to patch an automatic patch, which is really not how any of this is supposed to work. The log would tell me the filename of the INI. It would help me understand the actual cause of issue that prompts your request. Try this test version https://mega.nz/file/RdYVzZLa#v4pkdc0g1swy2wedljhMb3lP-yZ0QPebSJ3e1pnXhYU
  4. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. Just one example session that shows such an error, so I can determine the source for it.
  5. 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?
  6. 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?
  7. So far all logs have been of the same old version. Unless you upload the requested logs and bugreport.txt from the new test version and if the issue is not caused by something on your end, you are probably going to wait forever. Problems rarely fix themselves randomly. Keep getting newer test version from https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/#findComment-282545 and upload new log, debug log, bugreport.txt.
  8. Try new test version from https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/#findComment-282545 Restore default INI, delete old logs.
  9. Great! Thanks for letting us know.
  10. Upload the log and debug log from the all the generations.. Is VRAM slowly rising or is it a spike? Test with KeepRenderer=1
  11. Among the driver going away and resetting, I also found Error: OpenGL: out of memory Test adding TextureCache=10 to C:\MO2\ModOrganizer2\Tools\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini If this is an integrated graphics card, try to set more resources/memory for it if that is possible. It looks like there still is half? main memory left of 16GB? Track memory usage with task manager etc. You can try adding the -memory command line argument when starting TexGenx64.exe to try to reduce its memory usage a little. You can also try using DXT1 and DXT5 compression so there is less Texconvx64 GPU usage.
  12. Could you try to update to the latest graphics driver only installation? Or try to disable/terminate all the extra crapware that is running before running TexGen. amdfendrsr.exe, AMDRSServ.exe, AMDRSSrcExt.exe, atieclxx.exe, atiesrxx.exe, cncmd.exe, RadeonSoftware.exe for example.
  13. Delete all old logs in E:\DOWNLOAD\DynDOLOD\Logs\ and E:\DOWNLOAD\DynDOLOD\bugreport.txt Download this test version of TexGenx64.exe from https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/#findComment-282545 Run the test version as usual. Upload new log, debug log and bugreport.txt if issue persists.
  14. This seems to indicate a problem with the PC, like an hardware issue, CPU, Memory, BIOS settings etc. Make sure the PC is stable with prime95, OCCT etc. test and verify memory settings in the BIOS.
  15. That's an odd one - not the item not found itself of course - but where it happens. Is this reproducible a second time if you run again? In that case check if still happens with the test version from this post https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-182/page/684/#findComment-284087
  16. https://dyndolod.info/Messages/Exceptions#Assertion-failure If the assertion happens while the xEdit Background Loader loads all plugins, the plugin mentioned in the line above the error has most likely a problem that needs to be fixed. Check that you have the correct version of the plugin for the load order. Redownload and reinstall the mod/plugin. That problematic plugin would be sprigganhagsset.esp The plugin maybe corrupt or contain invalid records. Check if redownloading/getting the latest version fixes it. If nothing helps, upload it.
  17. So it looks like all the red textures and OpenGL issues are fixed without the next to use any TexGen_SSE.ini settings?
  18. While this is a different bugreport.txt it still reports the date of the TexGen to be from 2024-10-11, which would be form the DynDOLOD 3 Alpha 182 release. Close all open TexGen processes so it can be replaced. Make sure to download the test version and to replace the TexGenx64.exe in the DynDOLOD folder. It should have then a recent file date, typically from the time you downloaded. The log and debug log are typically saved when the tool close. No need to change INI settings. Just leave default for now as the error is currently different to that in the other thread. Delete old bugreport.txt before running again. If there is still no logs saved next time, enable the real time log as explained https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
  19. Delete all old logs and bug report. Get and run the test version of TexGen from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/#findComment-282545 Upload new log, debug log and bugreport.txt if there still is an issue.
  20. Based on the provided logs it seem you are using a old test version. Get and test with the latest test version from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/#findComment-282545 For future reference see https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which debug logs to also upload when making posts.
  21. Moved to the appropriate thread from which you got the test version. Try the latest test version from https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/#findComment-282545
  22. 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.
  23. Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen debug log and bugreport.txt to also upload when making posts.
  24. Also upload the TexGen debug log. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Make sure the texture is not accidently left over from an older generation. Compare its file date. Make sure all older TexGen output is really disabled before running TexGen. Check the same texture path in the data folder before running TexGen looks properly.
  25. Do not post logs. Uploaded the as attachment or provide link to external sources. See my texture. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Moved to the appropriate for the message shown in the log. See posts, questions and answers above. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search No questions were asked.
×
×
  • Create New...

Important Information

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