Jump to content

sheson

Mod Author
  • Posts

    13,181
  • Joined

  • Last visited

  • Days Won

    431

Everything posted by sheson

  1. Open the entire load order in xEdit. Start the xEdit Asset browser with CTRL+F3, type the filename into the Filter field top left. The first container mentioned is the winning one. Data means loose file. Right click, Save As from the winning container to test if it works. Report result. The game is installed into Program Files x86 which can cause issues with UAC, antivir etc. Make sure that none of the programs, xLODGen, LODGen and Texconv are denied files access.
  2. Doublecheck your merges and sysnthsis are up-to-date for the new load order. D:\Game Mod Working Folders\Skyrim SE\LOD WORKING\DynDOLOD 3.00-68518-Alpha-182-1728598274\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Export_Tamriel.txt D:\Game Mod Working Folders\Skyrim SE\LOD WORKING\DynDOLOD 3.00-68518-Alpha-182-1728598274\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt Upload Tamriel.4.0.0.bto, Tamriel.8.0.0.bto, Tamriel.16.0.0.bto and Tamriel.32.0.0.bto from the Meshes\Terrain\Tamriel\Objects\ folder. Post an in-game screenshot showing the issue. Post a screenshot of the DynDOLOD SkyUI MCM Settings page. Post a screenshot of xEdit showing all of the Tamriel worldspace record 0000003C most right column in Occlusion.esp
  3. The DynDOLOD log is from a different generation than the debug log uploaded earlier. No matching debug log for that generation was provided. It is unclear what settings were used for that generation and if you set Level32 in the DynDOLOD INI this time and/or if uLockedObjectMapLOD=16 or 32 is set. I suggest to not randomly disable or accuse grass or landscape plugins that most likely do not have anything to do with the issue. If the map does not show any object LOD it is typically because the object LOD files for the uLockedObjectMapLOD level do not exist, or are entirely empty.
  4. You only uploaded the DynDOLOD debug log. Also upload the DynDOLOD log when making posts as explained https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs DynDOLOD typically only generates textures in Textures\terrain\[Worldspace]\Trees\ folders for standard tree LOD. You have checked ultra tree LOD generation, so the tree LOD textures are part of the object LOD atlas in Textures\DynDOLOD\LOD\ You have not set Level32=1 in the DynDOLOD_SSE.ini despite using A Clear Map of Skyrim. Make sure to follow its instructions properly. https://dyndolod.info/FAQ#Entire-LOD-missing Can be caused by [MapMenu] uLockedObjectMapLOD=32 in Skyrim.ini (or SkyrimCustom.INI or a mod INI), especially if there are no object LOD level 32 meshes (which is the vanilla/default). See Trees on the Map for further explanations.
  5. https://dyndolod.info/FAQ#Enire-LOD-missing Increase terrain LOD, object LOD or tree LOD distances in the DynDOLOD SkyUI MCM Settings. Can be caused by [MapMenu] uLockedObjectMapLOD=32 in Skyrim.ini (or SkyrimCustom.INI or a mod INI), especially if there are no object LOD level 32 meshes (which is the vanilla/default). See Trees on the Map for further explanations. Make sure to follow the LOD generation instructions of A Clear Map of Skyrim properly.
  6. Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD logs and debug logs to upload when making posts. https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD Wait for all processes including all spawned LODGen command prompt windows to complete successfully. Pay attention to all log messages. It should end with the log message 'DynDOLOD plugins generated successfully' and lines like 'LODGen generated object LOD for [WORLDSPACE] successfully' for each selected worldspace. Do not use the output if there were errors that stopped the process prematurely.
  7. Moved to the appropriate thread for the error message. Use search as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search. Do not post screenshots of messages. Use the Copy message to clipboard and paste the message instead as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Post the TexGen log and debug log as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs See posts above. You probably want to start testing with setting RenderTexturesSingleThread=1 in TexGen_SSE.ini.
  8. You can select a single worldspace and select a single or more seasons and then Execute LODGen and wait for it to complete. Then select another worldspace and check different seasons and click Execute LODGen again.
  9. From bugreport: -o:"C:\Users\rgome\AppData\Local\ModOrganizer\Skyrim Special Edition\mods\Step SkyrimSE - xLODGen Output exception message: Unable to create directory. First post: Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder. Then install output as a mod. Do not generate into any game, any mod manager folders or special Windows folder like Program Files x86, Users, Desktop, Documents, Downloads etc. Readme.txt: Always set -o:"c:\OutputPath\" command line argument to change where files are generated to. The default is the game folder which risks replacing existing files and is problematic with mod managers, especially if they use some kind of virtualization. Do not generate into any game or any mod manager folders that are part (direct or indirect) of the virtual file system. Do not generate into the Overwrite folder of MO2. Delete old logs and bugreport.txt. Set a proper output folder, like C:\Modding\xLODGen_Output\ If problem persists upload new SSELODGen_log.txt and bugreport.txt and report if you use a spinning disk or if you might have installed a high resolution landscape texture pack.
  10. Only select the worldspaces and seasons that failed before clicking Execute LODGen. You can repeat that as often as needed with different selections until it completed all world spaces successfully. Do not Execute LODGen again for worldspaces and seasons that already completed successfully. You can also copy/move already completed worldspaces and seasons *.BTO to whereever to make sure they are not accidently overwritten with incomplete generations that get interrupted. IN the end you can merge all the *.BTOs that generated successfully into one complete output.
  11. Restore CreateMod=0. It is for mod authors and not for users to generate LOD for load orders full of mods (that also have lots of errors and warnings) and seasons etc. Upload new bugreport.txt and logs if issue persists.
  12. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to also upload when making posts.
  13. The actual occlusion calculation code did not change in a long time. The last notable change was with Alpha-129 in regards to the preparation part importing the heightmap ..\meshes\Terrain\[worldspace]\Objects\[worldspace].objects.heightmap.dat created by LODGen when generating object LOD instead of having to read all BTO. I suggest to restore the default OcclusionMaxThreadsObjectLOD=4 for whatever BTO it might still have to load. If the CPU actually overheats, then there is a problem with cooling.
  14. There might be changes to the load order that increased CPU, memory demand to higher levels than before and you were just lucky so far. Other reasons might be OS update, drivers, loose cables, BIOS settings resetting to default, hardware going bad, cooling being affected because of dust (dead mouse not unheard of) etc. It is possible the issue is storage/disk related.
  15. The PC shutting down, BSOD is a hardware, BIOS or OS problem. I suggest to stress test the PC with designated tools like prime95/OCCT and query an appropriate hardware forum. Occlusion generation uses the CPU and not the GPU/OpenGL. If you want to "troubleshoot" by reducing the CPU workload, use a lower quality setting or change process priority/core affinity with task manager or 3rd party tool. If using lots of memory is the problem see https://dyndolod.info/Help/Occlusion-Data#Out-of-Memory-while-Generating-Occlusion-Data
  16. If you use the PC as delivered, it wouldn't be the first time that the factory or the default BIOS settings are the cause of problems. I suggest to google the make of the PC or mainboard and learn about its BIOS settings, especially how to change/select different memory XMP/EXPO settings. I would also check if some kind of auto overclock is enabled, CPU temps, etc. This obviously requires some experience, so best to find a related hardware forum that disucsses your specific hardware - typically based on the mainboard.
  17. Run this test version https://mega.nz/file/8ZoHgQoA#O0hBLHwcuc3_GyNfiqV6eCZOX8YOTZzKP93KAgxpuyU I still suggest to do a thorough stability/stress test of the system.
  18. No question was asked. You did not explain what it is you are doing. See image at https://dyndolod.info/Help/Mod-Configuration-Menu-NG The DynDOLOD MCM simply shows update instructions in the MCM right part of the Window, since they are important to remember. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts.
  19. I can not give any tips regarding OneDrive as I do not use it and do not have it installed. xLODGen is able to read the INIs fine per the log. Special Windows folders, UAC, OneDrive, AntiVir etc. can be often a problem when writing files (sometimes when reading). However, there are no other obvious file access errors reported, so that all seems to work atm.
  20. The please wait message appears when bugreport.txt is written to. You can just let it sit until its all done, which can take a while if there were many threads running at the time. Use the latest xLODGen beta from the first post instead of whatever older version you are using. Install into a new and empty folder. Upload new bugreport.txt and SSELODGen_log.txt if there is still an error. There should be no need to run anything as admin in a proper setup outside of special Windows folders. It would be best to ensure there is no OneDrive for any related folders. If there are no obvious errors reported by xEdit for a plugin/record, there should be no need to edit or remove anything. Tools using the standard temp folder as defined by the OS should not be a problem. See https://tes5edit.github.io/docs/2-overview.html#CommandLineSwitches for the -t command line argument. Make sure the system, CPU, memory etc. is stable, cooling, settings in BIOS etc.
  21. No question was asked. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts. As explained in the first post and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages, actually read the message. It explains the problem and the solution. Also use the "Click on this link for additional explanations and help for this message" to open https://dyndolod.info/Help/DynDOLOD-DLL for further help as explained: Installation Install the contents of the archive(s) as any other mod with the mod manager. The DynDOLOD DLL and its papyrus scripts need to overwrite DynDOLOD Resources. https://dyndolod.info/Installation-Instructions Install DynDOLOD DLL NG and Scripts for Skyrim SE/AE, Skyrim VR, Enderal SE or Enderal VR. Overwrite DynDOLOD Resources. See https://dyndolod.info/Downloads for the download links to all required files. if you install DynDOLOD DLL 2.x for DynDOLOD 2.x there will large reference bugs https://dyndolod.info/Help/Large-References#Large-Reference-Bugs. Install DynDOLOD DLL NG and Scripts instead as explained by the instructions. I suggest to follow a proper modding guide to learn the basics of modding and how to properly setup the game.
  22. I am not going to watch a 3rd party video trying to find out what your problem is with it. If you have problems following third party advice, you need to ask its author/forum etc. I suggest to read https://dyndolod.info/Downloads for the links to all required downloads. Then follow https://dyndolod.info/Installation-Instructions and https://dyndolod.info/Generation-Instructions and watch the embedded videos.
  23. No question was asked. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search For example, use parts of the log messages or error message to search for posts containing the same messages. Moved to the appropriate thread for the message. See posts above. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages If there is an error prompt, read the entire message carefully. Many of them describe the problem in detail and offer hints for for a solution. Read additional explanations and help for a message by clicking on the Click on this link for additional explanations and help for this message link of the message. That will open a corresponding page on this website with further explanations and help for the message. The message explains what the problem in the load order is: Deleted references found. The message provides the solution for the problem in the load order: The following plugins need to be cleaned: Update.esm, Dawnguard.esm, HearthFires.esm The message has a link "Click on this link for additional explanations and help for this message" which opens https://dyndolod.info/Help/DynDOLOD-DLL, which says: Every plugin containing deleted references needs to be cleaned. See the Prerequisites section of the Generation Instructions for more. https://dyndolod.info/Generation-Instructions#Prerequisites Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean - ... Cleaning of plugins that contain deleted large references is mandatory for the DynDOLOD DLL NG that includes the large reference bugs workarounds. See https://tes5edit.github.io/docs/7-mod-cleaning-and-error-checking.html I suggest to follow a proper modding guide to learn the basics how to setup a stable load order and how to mod.
  24. Run this test version https://mega.nz/file/4UpmDTLI#Z2W1dVK6HGYULq-gw-KU0E7SbyOo1LCXgqpPFAj6Tas
  25. https://dyndolod.info/Mods/Community-Shaders Note that ultra tree LOD with BillboardX already utilizes HD tree LOD billboards that have normal map textures and typically has better visual results. https://dyndolod.info/Help/Ultra-Tree-LOD#Requirements Consider generating HD Tree LOD billboards with normal map textures for better looking tree LOD that reacts more naturally to lighting than standard tree LOD. https://dyndolod.info/Help/Ultra-Tree-LOD#Generating While Billboard1 is suitable for standard tree LOD billboards and HD tree LOD billboards, consider using Billboard4 with HD tree LOD billboards for even better visuals.
×
×
  • Create New...

Important Information

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