sheson
-
Posts
13,122 -
Joined
-
Last visited
-
Days Won
429
Everything posted by sheson
-
Report which mod the SHESON_DynDOLOD_MCM.pex script comes from. It should be from DynDOLOD DLL NG and Scripts. Is the game struggling with FPS or is it maybe unlocked? Upload the DynDOLOD.esm and DynDOLOD.esp.
-
Edit ..\SKSE\plugins\DynDOLOD_Data\DynDOLOD_NG_Worlds.txt in notepad and change debug=true and also add another line under it with debuglevel=5. Do the minimal steps required to reproduce the issue. For example load the game to a location, fast travel to problematic the location, check that the issue happend and close the game to keep the logs as short as possible. Also upload the corresponding papyrus log.
-
Read the first post and or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. If the giant shows without DynDOLOD output, it should also show with DynDOLOD output. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting Make a useful screenshot of the full model with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots Use the latest Alpha version and just generate LOD as usual with just Dac0da installed. Dac0da defines the giant full model reference as full LOD and with an enable parent. It should activate when entering Solitude while meeting the requirements to start the quest and then should be seen from everywhere. DynDOLOD has a rule to leave that refrence alone to not interfere with anything. If you are using the advanced or export mode, you need to click low, medium or high to make sure the rule is being loaded. Doublecheck or increase the fSkyCellRefFadeDistance in the DynDOLOD SkyUI MCM and/or SkyrimPrefs.INI. See https://dyndolod.info/Help/Mod-Configuration-Menu-NG#Settings
-
This looks like doing the disable/enable in console made it eventually unload the LOD for the large references in that cell. Do you recall how often you needed to do the disable/enable? If you like, try a second or third time to see if the number seems consistent. Check and report if this test version makes a difference https://mega.nz/file/FVgEULLa#EPHiZF40HLOIRah5ezMcTao5Z--jksQ0LRast4DZLBE
-
Repeat the test with this version https://mega.nz/file/AIo0gbBb#ifaHKbxlXv4EXd-usPsU7oxewujZIMVSDmu5pdd0E8I and report results.
-
Note that the test DLL is not fully functional in regards to large reference bugs workarounds as I just disabled something as a troubleshooting step. Repeat with this test version https://mega.nz/file/dNZXza4B#5-dSniz7v1Z-8DmbFpNkzovvv4Wrg7Lu9WMIJYEfRzI and report results.
-
After you fast traveled, open console and type prid 0004F112 to select the one if the rocks to the right of the last boat. Type disable (which will hide it) and the enable again. Close console for it to appear again. Repeat this a couple times to see of the large reference LOD for that cell eventually unloads. Maybe also try with prid 0009A53D which is the one huge Windhelm wall piece. Report results.
-
Oh no, I didn't actually paste a link in that post... You were supposed to get this other test version https://mega.nz/file/dNZXza4B#5-dSniz7v1Z-8DmbFpNkzovvv4Wrg7Lu9WMIJYEfRzI - it should report as 3.0.37.0. Sorry about that. Let us know if that one makes a difference...
-
IIRC it has an enable parent, thus it gets dynamic LOD.
-
Report if this versions makes a difference or not https://mega.nz/file/MMoVBALb#hh9JAE9NwZWN9AvdH2GikQnsnqxPeI5JOLRkAjFtcuk
-
DynDOLOD Resources SE version information not found
sheson replied to jjensson's question in DynDOLOD & xLODGen Support
Moved to the appropriate thread for the message. See posts above, see https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search Click the link Click on this link for additional explanations and help for this message link of the message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Help/DynDOLOD-Resources and scroll down to the Troubleshooting section: Install the latest version of DynDOLOD Resources or DynDOLOD Resource SE and the latest version of the DynDOLOD Standalone. See Downloads for links. If the version information or a required resource file can not be found, it means that the file with the version information or the resource file which are installed with the DynDOLOD Resources can not be found in the data folder (the standard OS functions which are used to check if a file exists returns a file not found error). Verify that the correct game data folder is being used for the checks. Check the top of the log messages that the tools are started in the desired game mode and check that the correct game data path was found in the Windows registry key. For example: Using Skyrim Special Edition Data Path: C:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\ Your log reports the data folder as: D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\ Install DynDOLOD Resources SE 3 with MO2 as any other mod. Make sure MO2 uses the same data folder as DynDOLOD. -
Replace DynDOLOD.DLL and PDB with this test version, then start game and repeat your steps. Report if this changes anything or not. If it does run around a bit and do some additional fast travel etc. to make sure everything is fine.
-
Remove/disable fixLOD.esp as it should not be needed when using dynamic LOD. Upload a useful screenshot of the windmil full model with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots Lets try to verify if what the video shows is related to large references by temporaliy disabling the large ref system. Set [General] uLargeRefLODGridSize=5 in SkyrimPrefs.ini, then repeat the fast travel routine to see if whatever flickers still happens. In either case, when it flickers, use tlc in console to fly closer and make a screenshot of that. Test if you can click it and get a form ID, again wirh more formative console, or type tll to toggle LOD off to see if whatever it is goes away.
-
Also upload the DynDOLOD log and debug log as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs. The ObjectEnabler script is used by the terrain underside references. The error indicates some kind of problem with the script properties of the reference or the form list in DynDOLOD.esp The papyrus logs show that some of the scripts from DynDOLOD DLL NG and Scripts might be overwritten or missing. The windmill building not showing might be a separate issue. What are the steps required to reproduce the problem? For example, you are starting the game, loading an existing save that already has DynDOLOD activated, then fast travel to the windmill?
-
Thanks for testing and letting us know.
-
If add those lines to DynDOLOD_SSE_aclearmapofskyrimesp_high.ini then they should work. Remember to load them by pressing the High preset button.
-
I suggest to actually do all the things suggested and then make a single post with all the reports. Temporality disabling a DLL that is listed high in the stack to see if that changes anything is not the same as getting rid of a something. Of course that may cause other problems. Check its logs for hints. Report results. The latest version seems to fix the crashes reported earlier in this thread. Alpha-34 fixed crashes that were reported by someone using Alpha-33. This seems to be a different crash. It may have to do with the used NIFs. Temporarily test with Alpha-33 to see if that makes a difference and report results as well.
-
This is a different crash that looks like a problem with animations. Verify that the crash does not happen with DynDOLOD output disabled. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting. Report which mod Meshes\architecture\farmhouse\farmhousewindmill\farmhousewindmillfan.nif comes from. I looks like SMIM, but check in MO2 right window data tab. It is also possible that Meshes\effects\fxwaterfallskirttallfrontslope.nif or meshes\effects\fxsplashlargechurnnorapids.nif are involved, so look those up as well. Test replacing/hiding them so that the vanilla versions of the models are used to see if that makes a difference. Test what happens if you hide OpenAnimationReplacer.dll. Disable the crash logs of NetScriptFramework (Debug.CrashLog.Enabled = 0 in NetScriptFramework.config.txt) and install Crash Logger SSE AE VR - PDB support instead. Upload one of those if problem persists.
-
Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log for the last LOD generation for the currrent load order to upload. Even if the output is not required, it will contain some information about the load order. Upload the DynDOLOD.log from DynDOLOD.DLL both with and without DynDOLOD output as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs. Make a useful screenshot of an affected full model with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game Screenshots. Provide links to the mods. What about Alpha-34? If possible do a binary search or a minimal test setup with only the mods that are required for the issue to happen. That also means do everything without DynDOLOD output and without DynDOLOD Resources. Also remove the scripts from DynDOLOD DLL NG and Scripts, so it is just the dll and pdb.
-
Unfortunately, the last session in the DynDOLOD debug log just shows the tool being opened and closed and no generation. Do you mean https://www.nexusmods.com/skyrimspecialedition/mods/82469? Which install option(s)? Make a useful screenshot of a tree full model that does not seem to have LOD representation with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots Upload E:\Skyrim VR jepster\tools\DynDOLOD\Logs\DynDOLOD_TES5VR_Object_Report.txt and E:\Skyrim VR jepster\tools\DynDOLOD\Logs\DynDOLOD_TES5VR_Tree_LOD.txt Which version of BOS do yo have installed? Test if generating with the test version from this post https://stepmodifications.org/forum/topic/21108-gigantic-wall-shaped-lod/#findComment-287058 makes a difference.
-
Thanks for letting us know.
-
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. Uninstall and remove the old DynDOLOD Resources SE for DynDOLOD 2.x and instead install the latest DynDOLOD Resources SE 3 for DynDOLOD 3 Alpha.
-
Moved to the appropriate thread based on "Giant Tower appeared" and "Whiterun has walls redone". See posts above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search Use the DynDOLOD test version from this post above https://stepmodifications.org/forum/topic/21108-gigantic-wall-shaped-lod/#findComment-287058 If that is not the issue or the test version does not fix the problem, then see https://dyndolod.info/Official-DynDOLOD-Support-Forum how to report the problem with logs and screenshots.
-
Moved to the DynDOLOD 3 Alpha thread. 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. Post text instead of screenshots of text, post the text instead as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text The log reports version 2.88 because that is the version of the installed DynDOLOD Resources SE which are for DynDOLOD 2.x. You seem to running DynDOLOD 3 Alpha, which requires DynDOLOD Resources SE 3. See https://dyndolod.info/Downloads for the correct download links for everything. Also, the video lists the correct link to the DynDOLOD Resources SE 3.
-
If the mod list installation installed the DynDOLOD Standalone as part of it and there is no Logs folder inside of if it of it it is empty, report the DynDOLODx64.exe version by right clicking it in Windows Explorer, Properties, Details tab, File version. If there are no further crashes after playing a couple days with the latest DynDOLOD DLL NG and Scripts Alpha version report that as well if you can.
