Jump to content

sheson

Mod Author
 View Profile  See their activity

  • Posts

    13,181

  • Joined

  • Last visited

  • Days Won

    431

 Content Type 

Everything posted by sheson

  1. sheson
    Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD log to upload when making posts. https://dyndolod.info/Help/Grass-LOD#Settings In case the grass LOD brightness or color seems off (it might depend on weathers or ENB settings), ... Especially the image based lighting effect from ENB has a big impact on the brightness and color tone of the grass LOD. Additional complex grass lighting and time of day settings will obviously not apply to object LOD, as they are separate meshes and shaders. Do not use them so full grass and grass LOD match better for all weathers/times. You might want to try different billboards for the LOD grass, see https://dyndolod.info/Help/Grass-LOD#Internal-Billboards-and-External-Billboards
  2. sheson
    The second link links to this forum instead of filebin.
  3. sheson
    https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Do not use CLA or posts logs from it. https://dyndolod.info/FAQ#ILS-or-CTD The DynDOLOD and Occlusion plugins might show up in crash logs a lot, since they are typically the plugins last to overwrite worldspace and cell records, so careful reading and interpretation of the stacks and registers etc. might be required to identify the actual cause of the problem. It is very unlikely for Occlusion.esp to cause crashes by itself. It is created by copying worldspace and cell records from the winning plugins before it, then update the TVDT Occlusion data which itself can not really cause crashes. Ignore nonsensical suggestions that autosaves need to be disabled because of papyrus scripts not completing or similar made up stories about plugins being "known to cause CTD" when fast traveling or changing locations because of scripting etc. This is not how anything works. If disabling autosaves would be required to prevent CTD, manual saves would have the same issue and it would actually be widely known, would have been reported, troubleshooted, analyzed, fixed, had known workarounds and/or be part of every modding guide since over a decade. The MCM already explains what to do before updating. Also https://dyndolod.info/Updating explains: 1. Before Updating Make a clean save. There is no ambiguity. A clean save is always required when generating a new LOD patch from scratch.
  4. sheson
    https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots "This" is not a problem description. See https://dyndolod.info/Help/TexGen-Configuration. If further help is needed ask specific question and provide the actual LOD resources, config files, logs, generated files etc. if needed.
  5. sheson
    Test if it is more consistent with this version https://mega.nz/file/xZAmQC5B#SHTVR46pUtfI1MW5S7NaLLKk5hJ2DLmgMjuCvHpKVpE
  6. sheson
    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.
  7. sheson
    Do you have specific cells where it happens always or do you always test the same area and it happens sometimes?
  8. sheson
    Skyrim INI settings like iMaxAllocatedMemoryBytes do not affect xEdit or DynDOLOD. I suggest to use BethINIs.
  9. sheson
    The Event log should have an entry for the tool being terminated or crashing. If a plugin/mod causes a problem, there should be an error message or a bugreport.txt etc. Run this test version https://mega.nz/file/VRxGQKyD#YbGqyCIal5-1Vf9Le2XcFg4eXQryuVxKiFVhVKn0uSA It will print a line for each cell is it is processing, then check whatever cell record is mentioned last in xEdit.
  10. sheson
    See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. Do not post screenshots of messages/text, use the Copy message to clipboard link and paste the text instead as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text See the Windows Event log for related entries with more information. This is typically an I/O problem of the OS loosing network or drive connection.
  11. sheson
    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.
  12. sheson
    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.
  13. sheson
    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.
  14. sheson
    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. sheson
    New test version https://mega.nz/file/dVgAwAoJ#GmQw40JxwOm3CSHB7AchNKUFDfE8OZieUNwilCDWC8Q Same procedure...
  16. sheson
    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
  17. sheson
    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
  18. sheson
    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.
  19. sheson
    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.
  20. sheson
    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
  21. sheson
    You are the one that will have to fix the problem. The screenshot from Windows Explorer shows files in the output folder. That needs to be installed as a mod with MO2 so they show up in the virtual data folder. If you want to show these files being installed, then check the MO2 right window Data tab that shows these required billboards actually being installed. You have not yet provided a TexGen log and debug log that show the actual generation of the required billboards. Object LOD textures and billboards are generated by TexGen after clicking Start in its interface while the corresponding checkboxes are checked.. While TexGen runs and generates texture, it print log messages to the Message log tab, which are then saved to the TexGen log when the tool is closed. See https://dyndolod.info/Generation-Instructions#1-Generate-The-Required-LOD-Assets-with-TexGen, https://dyndolod.info/Help/TexGen and https://dyndolod.info/Messages.
  22. sheson
    Copy and paste the message text instead of taking screenshots as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text The TexGen and DynDOLOD debug always only contains the last session and they both show the tools being started and then closed without doing anything. The TexGen log only contains several sessions that show the tool was started, the message about stitched object LOD was shown and then the tool was closed. You will have to actually generate object LOD textures and tree LOD billboards without error messages and then install that output. Those would be the logs to upload. The DynDOLOD log contains several sessions with the LOD billboards missing messages as expected. The screenshot of MO2 does not show anything useful. Change it to show the Data tab and drill down to ..\textures\terrain\lodgen\folkvangr - grass and landscape overhaul.esp\ folder and the file grass_tundra_wheat_00021a28.txt from the first LOD billboard not found log message for example.
  23. sheson
    Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD logs and debug logs to upload when making posts. Copy and past ethe message text instead of taking pictures of your monitor as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Learn how to make screenshots in Windows instead of taking photos of your monitor https://www.wikihow.com/Take-a-Screenshot-in-Microsoft-Windows Click the link "lick on this link for additional explanations and help for this message" as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open the page https://dyndolod.info/Help/Tree-Grass-LOD-Billboards for further help for the message. Scroll down to https://dyndolod.info/Help/Tree-Grass-LOD-Billboards#LOD-Billboard-s-Not-Found Make sure TexGen completed the generation of tree LOD billboards successfully. Make sure the latest TexGen output is installed as a mod in the current load order. The photo of the monitor shows a Windows Explorer window which shows the textures folder of the output folder of TexGen. That needs to be installed as a mod, so it shows up in the games data folder as any other mod. Make sure to activate the TexGen Output mod in MO2. We do not know if the TexGen generation was successful or what it generated. Check its log.
  24. sheson
    The LOD does unload when the cell attaches when you walk closer, right? When you tlc to see this, can you open console and pick any of the references, then disable it, close console, open console, enable it, close console. Repeat that a few times, does the LOD eventually unload? Upload ..\SKSE\plugins\DynDOLOD_Data\DynDOLOD_NG_Tamriel.txt from the DynDOLOD output.
  25. sheson
    xEdit - on which DynDOLOD is based - is a Windows program and uses DOS/Windows command line standards that enclose paths in double quotes as shown in the examples: https://dyndolod.info/Help/Command-Line-Argument -o:"[path to output folder]" for example -o:"c:\Output\" -m:"[path to INI folder]" for example -m:"c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition GOG\" -p:"[path to plugins.txt]" for example -p:"c:\Users\[USERNAME]\AppData\Local\Skyrim Special Edition GOG\plugins.txt" -d:"[path to Data folder]" for example -d:"c:\GOG Games\Skyrim Special Edition GOG\Data\" A path should always be enclosed between double quotes. Use copy and paste to avoid mistakes, like adding extraneous spaces between the command letter, colon and beginning double quotes.
×
×
  • Create New...

Important Information

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

  I accept