sheson
-
Posts
13,181 -
Joined
-
Last visited
-
Days Won
431
Everything posted by sheson
-
No xLODGen_log.txt was provided. Do not post screenshots of text. Copy and paste the text when possible instead The xLODGen archive does not contain LODGenx64Win.exe. xLODGen does not use the .Net versions of LODGen. xLODGen does not use any files in DynDOLOD directories. .NET Framework and .NET are different things. I suggest to read and believe messages from the OS or programs.
-
Keep RenderSingle=1 and add both GLDebug=1 and RealTimeLog=1 under [DynDOLOD] Upload new log, debug log and bugreport.txt if it exists or DynDOLOD_SSE_realtime_log.txt in case it wasn't able to save the log and debug log.
-
Moved to the DynDOLOD 3 Alpha thread. See the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD debug log and log to upload. Also see https://dyndolod.info/Installation-Instructions Refer to the manual of the mod manager how to add the DynDOLOD/TexGen executables, for example Mod Organizer, Vortex. If the tools are started without setting a Game Mode with a command line argument, a message window will prompt for the desired Game Mode. For Steam versions of the game, use the game launcher to set the current location of the game in the Windows Registry. See Windows Registry Key for more. See Skyrim Special Edition GOG / Skyrim Anniversary Edition GOG in case the GOG version of the game is used. Check the reported game Data Path in the TexGen/DynDOLOD log is the correct one and the same MO2 uses. If not see https://dyndolod.info/Messages/Windows-Registry-Key
-
Is this error repeatable if you only generate SIworld for a test? If problem persists check if adding RenderSingle=1 under [DynDOLOD] in E:\Mod Tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini makes a difference.
-
The base record has show in worldmap flagged, which together with the IsFullLOD flag of the reference can cause CTD. Unset the IsFullLOD flag on the reference or create an overwrite for the base record into a new or existing plugin of your choice and unset the Show in Worldmap flag. That should stop the game from crashing when opening the map.
-
An incomplete log was provided. Post the entire log. Does "the mod" refer to the mod that contains ACatsLife.esp? Provide a link to "the mod". Provide the modified plugin. Best to use DynDOLOD 3 Alpha.
-
https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting In case of issues in the game, test if the problem persists without any DynDOLOD output. If the problem only happens with DynDOLOD output being active, test if problem is repeatable and the reported records are consistent. Check the mentioned references and base records in xEdit for obvious problems. xx0BCC43 in DynDOLOD.esp and xx0165E0 in DynDOLOD.esm in this case. If the base record links a material record check that one, too. If nothing sticks out, post screenshots of them. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#xEdit-Screenshots The winning overwrite in DynDOLOD.esp for the base record should be a copy of xx006A1D in Prometheus_No_snow_Under_the_roof.esp. The used base record seems to be the original from the mod No snow under the roof, however the plugin seems to be a different version. Report which mod it comes from or if you modified it yourself.
-
This sounds like a problem with whatever tool was used to unpack not keeping the actual folder structure from the download archive. As explained in https://dyndolod.info/Installation-Instructions, use official https://www.7-zip.org to unpack.
-
Try this test version https://mega.nz/file/gVQTgCCS#D5p_Kra4dnlM9-8w7Tj0woPXSZX22mjL86KOjxoQOdQ Look out for warning messages about not finding INIs, which are part of the download archives and thus should exist.
-
This should be fixed in DynDOLOD DLL NG and Scripts 3 Alpha-30. Just replace the old version and play a while to see if it happens again.
-
Check if there is anything different with this test version https://mega.nz/file/1VAgHJ6J#Ejhao_JjMxKCfHjrGmHsEUFQ9Tr0iQkrbkgcYBqr4CA If not, upload new TexGen log, debug log and bugreport.txt
-
The FNVLODGen_log.txt you provided, shows output being generated to c:\fnvlodgenoutput\ and not the game folder? Always set a dedicated output folder with the -o command line as explained in the first post and the readme included in the download archive.
-
Moved to the appropriate thread for the message. See posts and discussions above. As also explained in https://dyndolod.info/Help/Texconv, check the windows event log for related messages. This could also be unstable memory, BIOS or OS settings.
-
Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD log and debug to upload when making posts. As explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages, click the Click on this link for additional explanations and help for this message link to open https://dyndolod.info/Messages/LOD-Billboard-Not-Found, which then links again to https://dyndolod.info/Help/Tree-Grass-LOD-Billboards#LOD-Billboard-s-Not-Found, go through the check list. Messages from programs state facts. The video shows you are purposefully not deploying the changes after installing the TexGen output. Learn how the mod manager you are using works, or consider using an easier to use mod manager like MO2.
-
Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which bugreport.txt to also upload. https://dyndolod.info/Messages/Exceptions#Item-not-found
-
Toggle all LOD off/on with tll in console. Whatever remains is not LOD., if it went away it was LOD. xLODGen generates LOD meshes and textures. The engine decide how to load and display them. Meshes and textures do not change how the engine works. The settings seem typical and changing them is unlikely to change whatever the issue is. There are no serious problems that stick out in the LOD generation. There is that - unrelated - overriden record reported by the background load that warrants being looked at.
-
If you just want it to work, then the update is achieving just that. Regardless if you install DynDOLOD DLL VR or DynDOLOD DLL NG and whatever the IgnoreLargeReferences is set to, the generated LOD patch should work in the game without error message. You do not need to make assumptions about setting. You can hover the mouse pointer over them for hints and/or read their explanations that open by clicking the help button. You can also leave them as is, as the defaults are the same regardless what DLL is used or what IgnoreLargeReferences is set to.
-
https://dyndolod.info/Help/Clean-Save The DynDOLOD plugins or the Occlusion.esp itself are very simple and mostly self contained. That means removing and/or updating does not have any known ill-effects, if following the below procedure. The clean procedure only needs to be done if generating new DynDOLOD output from scratch (in case a 3rd party plugin that is a master in a DynDOLOD plugin has been removed for example) or when switching from PapyrusUtil to DynDOLOD DLL or vice versa for an existing save game. There is no need for a clean save when updating existing DynDOLOD plugins and/or Occlusion.esp.
-
If you have issues following a third party guide, you need to ask its author(s), forum, discord etc. for help. No FNVLODGen_log.txt was uploaded. The actual used settings were not provided. It is assumed "this" refers to terrain LOD showing in the active cells. LOD not unloading in the active cells is typically an engine or game INI setting problem and unrelated to the LOD meshes/textures or which tool was used to generate them. Test with default INIs, without other mods, etc.
-
Updating, especially across versions changes is not guaranteed to work. Is there an error updating output that was generated with the same version?
-
Thanks. It will take a me a bit to analyze this.
-
As already explained, use DynDOLOD DLL VR instead of DynDOLOD DLL NG if you want to generate a LOD patch with IgnoreLargeReferences=1
-
If the load order changes, automatically generated patch plugins may become out of date and need to be generated again.
-
Moved to the DynDOLOD 3 thread. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Links which entire TexGen log and debug log to upload when making posts. Was there not a link Click on this link for additional explanations and help for this message with the message that opens https://dyndolod.info/Messages/Exceptions#Item-not-found https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-the-Latest-Versions
-
https://dyndolod.info/Generation-Instructions Select a dedicated output path. The dedicated output path should be outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game or any mod manager folders.
