sheson
-
Posts
13,181 -
Joined
-
Last visited
-
Days Won
431
Everything posted by sheson
-
Do not post screenshots of text. Copy paste the text instead. Read the explanations for this message https://dyndolod.info/Messages/File-Not-Found-Meshes
-
The log message and Summary lists overwritten large references and other problematic records triggering these bugs with brief explanations and links to the website for the details including possible workarounds of the large reference bugs. Checking the cell coordinates in the log messages should help finding the problematic records for this area and deal with them specifically.
-
From the https://dyndolod.info/FAQ Object LOD model and full model show at the same time causing texture flicker Known as large reference engine bug in Skyrim Special Edition and Skyrim VR that happens just outside the active exterior cells in the uLargeRefLODGridSize area. Move the slider Large Object Distance on the View Distance tab of the Advanced options of the games launcher to the very left. Alternatively set [General] uLargeRefLODGridSize=5 in SkyrimPrefs.ini. If this does not affect the issue see the answers for Out of place or floating objects below. DynDOLOD does not change how the engine works. When new cells attach, first it loads the full models, then unloads object LOD. For that brief time both models show and there can be texture flicker. The more things the game has to load when new cells attach and the more system resources are strained the longer it takes to load full models and to unload object LOD.
-
Need to change Skyrim game path for Texgen and DynDoLod
sheson replied to TectonicLeader's question in DynDOLOD & xLODGen Support
The game launcher to start directly (with a file manager like Windows Explorer) from the new directory to update the Windows registry with the current location without Steam running is ..\Skyrim Special Edition\SkyrimSELauncher.exe There is no need to manually edit the registry. If the launcher can not update the registry, then there is a more serious problem, like the OS, antivir or some 3rd party crapware denying access that needs to be addressed first. The registry should contain the correct path to the game regardless of adding a command line to tools or not. Everything uses it to automatically discover the game location. -
Need to change Skyrim game path for Texgen and DynDoLod
sheson replied to TectonicLeader's question in DynDOLOD & xLODGen Support
Start the games launcher from the new directory to update the Windows registry with the current location. The launcher can be started directly without Steam running. -
Thanks for all the help. That's all I need. Keep using the last version (#4) that worked.
-
Great! Good to know that test version #4 works as it is based on beta 87. Now if you could also run test version #3. I expect it to fail. Upload SSELODGen and bugreport please to conclude the troubleshooting.
-
The SSELODGen_log.txt is saved when xLODGen is closed.
-
Again, there is no point in uploading the log from LODGen generating terrain LOD meshes. Upload the SSELODGen log. Then run this test version and upload its SSELODGen log and bugreport - if it exists.
-
The test version from the last post is beta 86. As expected it makes no difference. The terrain LOD generation code did not change between beta 86 and beta 87. Upload the bugreport and SSELODGen log. Troubleshooting is about finding the cause of the problem and fix it. Not ignoring problems. Then test with this test version and upload bugreport and SSELODGen log of that as well.
-
There is no need to upload the discreet log from the LODGen.exe meshes generation. Do not install the game into special Windows folder like Program Files x86 to avoid problems with UAC and antivir. Do not generate into mod manager folders. Especially while the mod manager is running. Remove the dedicated output folder to make sure it is really empty and there are no hidden blocked files or folder accessed by other processes. See what happens when using this test version. Upload bugreport and SSLODGen_log.txt
-
Upload bugreport.txt and answer the question if the error happens at the same part of the process, e.g. check the if the error message "Error saving textures" is for the same LOD level and coordinates / same filename. If it is make sure the output folder is empty, best delete it so it is create anew and that OS anti virus do not interfere with writing files.
-
Run this test version, which should print the LOD Level and coordinates for the error message. Check if this is a repeatable error happening at the same part of the process.
-
Upload the SSELODGen log.
-
Since there are no NGIO and .NetFramework versions for 1.6 out it is not possible. You would need to (temporarily) downgrade
-
Do not post screenshots of text. Copy and paste/upload the text/log instead as explained on the first post. You either selected ridiculously too high resolution/settings or there is crapware running the background hindering normal operation. https://stepmodifications.org/forum/topic/15606-dyndolod-300-alpha-65/?do=findComment&comment=254612
-
The English version of the error message from the OS is "The system cannot find the path specified". If you search for it you will find that, the OS, Antivirus or some other third party program is preventing write access. If disabling a plugin actually has an effect on antivirus it must mean the generated texture is different - e.g. the content of the file is actually different and that is what triggers the anti virus. As the first post explains, use the -o command line parameter to generate into a dedicated output folder that is not inside game or mod manager folders.
-
If there are no NGIO grass cache files then the optional grass LOD can not be generated.
-
As explained again and again and at https://dyndolod.info/How-LOD-Works and https://dyndolod.info/Help/Terrain-LOD, DynDOLOD generates tree and object LOD and does not do generate or change terrain or water LOD. Water LOD as part of terrain LOD generation / BTR meshes only defines where water LOD is. How water LOD looks depends entirely on the water LOD record defined on the worldspace record. LOD generation does not change this record and vice versa the record does not affect LOD generation. Because of this single record for the entire worldspace, all water LOD looks the same, unlike water in the active cells, which can each define their specific water record. Read the first post of the DynDOLOD 3 Alpha thread where to make posts. I moved your post to the thread. https://dyndolod.info/Help/Tree-LOD explains tree LOD. It says this: While this is commonly referred to as tree LOD, it might also be referred to as standard tree LOD or traditional tree LOD when trying to distinguish between similar tree LOD with tree LOD billboards done in object LOD, e.g. ultra tree LOD. Read the documentation https://dyndolod.info/Help/Ultra-Tree-LOD. It happens to explain how to generate ultra tree LOD, how to have ultra tree LOD in all object LOD levels and on the map, which happens automatically because the map uses object LOD level 16.
-
Good to know. There should be no more missing overriden record and no more warning with the next alpha version.
-
Users not following or using bad instructions breaks games. Cleaning is safe and fixing known sources of problems in the load order is good modding practice. Deleted references are a known cause of CTD. Especially when not cleaning the paid mods since they are now the uncertainty what the DLCs were back then when they came out for Skyrim. There are mods made before they came out, unaware of the changes made in the vanilla files or the paid mods or a mod author does not have them. BTW, I checked, I spend 20 minutes to manually clean 41 CC plugins initially. The last update did not change any paid mods. The update before that changed 4 paid mods of which 3 needed to be cleaned, which took me 2 minutes. Just saying... A fixed load order with known mods and plugins based on a guide is probably fine until it is customized - until a user installs this one mod from 1 years ago. If a guide does not instruct users to clean a plugin, I suggest to provide the cleaned plugin for download. DynDOLOD is a multipurpose tool. In cases like this, it does not know if a problem requires action or not, it does not know if the current load order accidentally happens to be "safe" or not and if a reported issue requires action or not. Hence the nicely sorted summary with the explanations. This is off topic.
-
Put in a feature request with xEdit for an command line option to replace logfiles. Otherwise simply delete the log folder before doing such a run or truncate the log file in notepad to last meaningful generation as explained on the first post. Simply search for "starting session" to jump to a start of a session. Typically it is easier for people to simply upload the logfile without having to worry about the session with the messages of interest being already replaced. If you load the generated DynDOLOD.esm into xEdit afterwards, does xEdit still show the message or is it corrected once it has been saved?
-
Yes, updating the RNAM data in the vanilla plugins to make reference not large will work. Burying all large references in a cell (at least the once that have visual flicker) and add new non large reference works, too. That is how DynDOLOD creates the workaround for one vanilla issue for the College of Winterhold bridge. xLODGen terrain LOD beta (used in edit mode) shows RNAM data on Skyrim.esm. Or rename Skyrim.esm. Its a lot of data. I purposefully refrained from considering patching RNAM data in plugins to address the bugs. A better solution in this direction would be a DLL plugin that skips loading the data. Aers and I looked at it for a bit a couple years back (which let to reference cap explanations) but we couldn't easily make it work at the time. Also I do not do any serious reverse engineering while there are still updates to the game. "missing an overriden record" is a message from xEdit that should not happen with a DynDOLOD plugin in any normal operation. Read the first post which entire log files to upload when making posts. If this happens while trying to update existing DynDOLOD plugins, generate from scratch instead.
-
Typically if an error is logged for an item, no further processing is done for it since it is being discarded, unavailable etc.
-
Check if the event id 1000 is preceded by other events with the similar timestamp. For example like event id 1005 like shown in the screenshots of from this post https://stepmodifications.org/forum/topic/15606-dyndolod-300-alpha-65/?do=findComment&comment=256156 Make sure Antivir or other 3rd party tools are not interfering. Check the used filesystems/disks for errors. The second event seems unrelated.
