sheson
-
Posts
13,181 -
Joined
-
Last visited
-
Days Won
431
Everything posted by sheson
-
This should hopefully be fixed in Alpha 56
-
The out of memory message happens while testing the graphics card. This part did not really change in the past 10 alphas or so. If there is more than one graphics card, it is supposed to use the first / better one. See that the primary card is set correctly in the OS/driver. Make sure VRAM is not used up too much by other processes.
-
Read the first post which log files and bugreport.txt to upload when making posts.
-
Temporarily disabling plugins or mods is a troubleshooting step. It does not fix errors / invalid textures. The mod contains an invalid texture that needs to be updated. Either download the fix provided by the mod author (check the bug section) or remove the mod permanently.
-
Fixed. Thanks for reporting.
-
Uploaded a new DynDOLOD DLL version for Skyrim Special Edition 1.6.323 (Anniversary Edition). It requires SKSE64 2.1.3 or higher.
-
Read the DynDOLOD FAQ and the DynDOLOD Readme how to troubleshoot CTD. Pay attention to the log messages, especially warning and errors about textures. Read the first post what log files to upload when making reports. Include the LODGen log Tamriel, too. A load order includes all mods not just the list of plugins. Use modwatch if you want to provide that information. If I had to guess it's the invalid texture from RedBag's Rorikstead.esp as discussed before.
-
The second post / ..\DynDOLOD3\docs\help\GrassLOD.html ""Updating" section explains how to update / test different settings.
-
Problems can not be investigated or fixed if people do not upload log files and bugreport.txt as explained in the first post. LOD generation runs through without a problem with Beyond Bruma 1.5.1 installed and enabled in the load order.
-
DynDOLOD FAQ: Game: Out of place objects / floating objects / flickering full models A: If the problems is stuck object LOD in Whiterun after fast travel, change Distant Object Detail on the View Distance tab of the Advanced options of the games launcher from Ultra to High. Alternatively try just slightly changing the value fBlockLevel0Distance=60000 in SkyrimPrefs.ini to 57000. A: If the problem is stuck object LOD in loaded cells, it can be caused by uLockedObjectMapLOD=32 in Skyrim.ini. The problem with locked object LOD to 32 seems to have a higher (or maybe only?) chance of happening if there are no object LOD Level 32 files. It might also correlate to specific INI settings, like the stuck object LOD after fast travel. But I never really looked that long into it.
-
Read the first post and follow its suggestions.
-
Thanks. Enjoy.
-
Tree Pop-in and Billboard Issues with DynDOLOD
sheson replied to Brexin212's question in DynDOLOD & xLODGen Support
I am going to answer the original post anyways to point out a few things for future readers. If you follow and have problems with 3rd party guides you should ask their author/forum/discord for help. For DynDOLOD 2.x, for each tree that you want to have billboard tree LOD, a billboard needs to be installed. This is explained in the installation instructions. The log prints a list of found and not found billboard textures which helps to find which of the desired trees still needs a billboard. TexGen from DynDOLOD 3 Alpha generates all required billboards automatically. No more billboards need to be downloaded/installed or created manually. -
Sounds like the screenshot/problem I replied to here.
-
I would like to troubleshoot this a bit to see if I can find out what is happening. So if you could do a run that has the error and uploads its bugreport,txt and DynDOLOD debug so I can compare that to the files you already provided it might help me to better understand what is going on. If you just want to generate LOD and occlusion, generate everything in DynDOLOD just without checking Occlusion and then generate Occlusion.esp with xLODGen separately. The end result is about the same.
-
This error is repeatable and happens about at the same time/portion of the the log? Can you just run it again one time and upload that bugreport.txt and debug log too please. Checking occlusion generation should not affect the processing of base records as it only starts the occlusion generation way later after worldspaces have been processed and object LOD generated, so that is a bit of a mystery atm. As the first post and included documentation explains, TexGen automatically generates all required billboards for the load order. 3rd party billboards should not be installed anymore. The mesh mask rule are explained in the manual, but don't worry about that. Your method works, too and is fine for personal use.
-
Are you saying the error does not happen when you uncheck Occlusion data generation but keep the load order as is or are you saying it runs through without problem if the only mod you disable is Falskaar? Probably unrelated but you should run TexGen before DynDOLOD and install its output. You might also want to disable any third party billboards and use TexGen to generate all desired LOD billboards. Also it seems that there are (some?) full tree models copied to LOD model files names? For 3D Trees and Plants? That seems overly ambitious and unnecessary given that there are decent 3D tree LOD models. Instead of copying full model filename to LOD model filenames i t is recommended to use mesh mask rules to instruct the use of full models for LOD. I guess if you have 3090 that might work.
-
Well that is the point of the DynDOLOD DLL for 1.6.318
-
Read the first post. There is no release version of DynDOLOD 3. DynDOLOD 3 is an alpha for testing and to discover bugs. Always use the latest alpha version, so to not come across or report long fixed bugs or problems. The log shows the version you are using is from March, that is like Alpha 33. That is from before the crows mod even was released.
-
Why do you not just use the latest DynDOLOD 3 Alpha version?
-
Crows are not birds of prey. For references using the same base record / model not to be in sync the Random Animation Start flag has to be set. If there are animations in sync, you might not be looking up the correct base records. DynDOLOD create copies of the base records for the LOD. They typically should have the Random Animation Start flag set as well. Use DynDOLOD 3 alpha for this mod, I can not guarantee 2.x has all the required functionality for it.
-
Click the Help for this message link to open ..\DynDOLOD\docs\help\Unresolved.html, which explains in great detail what the error means and gives a few hints for their cause and how to fix it. Read the entire error message. Pay attention to "Update.esm might be the wrong version." Looks like the paid mod you are using expects a different Update.esm. Errors are never "normal".
-
Check if xLODGen in task manager still uses CPU or if it might be waiting for Texconvx64.exe running spawned in the background. Make sure no UAC, anti-vir is blocking access. Do not generate to the game data folder or mod manager folders. Use -o to set a dedicated output folder.
-
The instructions include all the steps that need to be done. The instructions do not include the infinite number of things not to do. Since there is no instruction to disable DynDOLOD Resource SE, it means that they should not be disabled. The DynDOLOD Resources SE includes assets that are required in game.
-
Uploaded a new DynDOLOD DLL version for Skyrim Special Edition 1.6.318 (Anniversary Edition). It requires SKSE64 2.1.2 or higher.
