sheson

Correct, generating into the default game folder will replace loose files in case they exist already. Once you start generating LOD, the message window will print line(s) where it outputs the files.

How is it supposed to look instead? What is it you are comparing with each other? Type tll in console to disable LOD to check which of the rock mountains are actually LOD and which are full models. The LOD mountains in object LOD level 4 typically use the very same full texture(s) as the full model mountains. Mountainslablod.dds is typically only used in the further away LOD levels 8 or 16. If this is about the snow cover, read https://dyndolod.info/Help/Snow-Ash-LOD-Shader The meshes and textures from the Majestic Mountains LOD pack should overwrite DynDOLOD Resources SE. Generated output from TexGen and then generated output from DynDOLOD should always overwrite everything else.

As you have shown, the reference 0009F27E is not changed by DynDOLOD. The base record only has the HasDistantLOD flag set. How do you suppose that reference shows whmaingatesteps_lod_0.nif instead of WHmaingatesteps.nif? Typically there should be a new reference that places whmaingatesteps_lod_0.nif on top of WHmaingatesteps.nif. In console, after highlighting 0009F27E, type disable. The steps from whmaingatesteps_lod_0.nif should still be there and should hopefully be clickable and show a different form id. If the whmaingatesteps_lod_0.nif steps can not be clicked, see if they go away by typing tll in console.

DynDOLOD reporting a problem in the load order does not mean it is causing the problems. That should be obvious after actually reading the explanations for a message. Unless you are saying that the warnings about missing files are not factual? DynDOLOD 2.x also reported missing meshes, for example: SpoilerMissing models were ignored by DynDOLOD. Below is a list of base records with missing models which are used by references: LegacyoftheDragonborn.esm _DA_Light4DBM [MSTT:1036C11B]: Missing model "meshes\dungeons\ship\da_skyship\da_light4.nif" LegacyoftheDragonborn.esm _DA_Light1DBM [MSTT:1036C11C]: Missing model "meshes\dungeons\ship\da_skyship\da_light1.nif" LegacyoftheDragonborn.esm _DA_Light2DBM [MSTT:1036C11D]: Missing model "meshes\dungeons\ship\da_skyship\da_light2.nif" LegacyoftheDragonborn.esm _DA_Light5DBM [MSTT:1036C11E]: Missing model "meshes\dungeons\ship\da_skyship\da_light5.nif" LegacyoftheDragonborn.esm _DA_Light3DBM [MSTT:1036C11F]: Missing model "meshes\dungeons\ship\da_skyship\da_light3.nif" References using base records with missing models can cause CTD. Install the missing meshes, then generate LOD again if LOD for reference using these base records is desired. The root node being a NiNode is also reported by DynDOLOD 2.x for example: Root block of meshes\dbm resources\architecture\museum.nif is NiNode - ignoring DBMOldMuseum [STAT:1013D92C] in LegacyoftheDragonborn.esm for dynamic LOD DynDOLOD 2.x also reports overwritten large references, for example: Spoiler Checking for plugins causing texture z-fighting flicker because of large references bugs. Cutting Room Floor.esp [REFR:000D3AE8] (places RockCliff02Snow01 [STAT:0001EF3B] in GRUP Cell Temporary Children of NightgateInnExterior02 [CELL:0000907C] (in Tamriel "Skyrim" [WRLD:0000003C] at 17,10)) Cutting Room Floor.esp [REFR:000D5FF7] (places TreePineForestLog01Heavy_SN [STAT:00054CE8] in GRUP Cell Temporary Children of [CELL:000093B7] (in Tamriel "Skyrim" [WRLD:0000003C] at -3,15)) Cutting Room Floor.esp [REFR:000F580D] (places FXAmbSnowBlowingPlane [MSTT:000197C7] in GRUP Cell Temporary Children of CRFHoarfrostGrotto [CELL:00008F00] (in Tamriel "Skyrim" [WRLD:0000003C] at 25,22)) Cutting Room Floor.esp [REFR:000D3AE9] (places RockCliff03Snow [STAT:00024BAD] in GRUP Cell Temporary Children of NightgateInnExterior01 [CELL:0000905D] (in Tamriel "Skyrim" [WRLD:0000003C] at 17,11)) Cutting Room Floor.esp [REFR:0006716B] (places WRWallRubblePile02 [STAT:00067168] in GRUP Cell Temporary Children of WhiterunExterior14 [CELL:0000961C] (in Tamriel "Skyrim" [WRLD:0000003C] at 3,-3)) Cutting Room Floor.esp [REFR:00049210] (places RoadStraight01 [STAT:0001C42F] in GRUP Cell Persistent Children of [CELL:00000D74] (in Tamriel "Skyrim" [WRLD:0000003C]) at -11,-15) Cutting Room Floor.esp [REFR:00080C54] (places RTWall06OuterCRF [STAT:1101F65A] in GRUP Cell Temporary Children of [CELL:0000BCF0] (in Tamriel "Skyrim" [WRLD:0000003C] at 43,-25)) Cutting Room Floor.esp [REFR:000F57F2] (places RockPileL01Snow [STAT:00032A94] in GRUP Cell Temporary Children of CRFHoarfrostGrotto [CELL:00008F00] (in Tamriel "Skyrim" [WRLD:0000003C] at 25,22)) Cutting Room Floor.esp [REFR:00062DAF] (places RockPileL01Snow [STAT:00032A94] in GRUP Cell Temporary Children of StonehillsExterior01 [CELL:000093B6] (in Tamriel "Skyrim" [WRLD:0000003C] at -2,15)) Cutting Room Floor.esp [REFR:00097412] (places RockCliff03 [STAT:00025DA8] in GRUP Cell Temporary Children of CRFIrontreeMill [CELL:00009389] (in Tamriel "Skyrim" [WRLD:0000003C] at -23,17)) Cutting Room Floor.esp [REFR:00097413] (places RockCliff02PineForest02 [STAT:00054C32] in GRUP Cell Temporary Children of CRFIrontreeMill [CELL:00009389] (in Tamriel "Skyrim" [WRLD:0000003C] at -23,17)) Cutting Room Floor.esp [REFR:000EF5E2] (places FXSmokeWispsLg2x1 [MSTT:00077776] in GRUP Cell Temporary Children of [CELL:00008EAE] (in Tamriel "Skyrim" [WRLD:0000003C] at 14,25)) Cutting Room Floor.esp [REFR:000EF5E1] (places FXSmokeWispsLg2x1 [MSTT:00077776] in GRUP Cell Temporary Children of [CELL:00008EAE] (in Tamriel "Skyrim" [WRLD:0000003C] at 14,25)) Cutting Room Floor.esp [REFR:000973CA] (places RockPileL02PineForest02 [STAT:0005B810] in GRUP Cell Temporary Children of CRFFrostRiverSE [CELL:00009387] (in Tamriel "Skyrim" [WRLD:0000003C] at -21,17)) Cutting Room Floor.esp [REFR:000973BB] (places MountainTrim01PineForest02 [STAT:00055036] in GRUP Cell Temporary Children of CRFFrostRiverFarmWest [CELL:00009367] (in Tamriel "Skyrim" [WRLD:0000003C] at -22,18)) Cutting Room Floor.esp [REFR:00098CDA] (places RockPileL01PineForest02 [STAT:0005DB00] in GRUP Cell Temporary Children of CRFFrostRiverSmithCell [CELL:00009388] (in Tamriel "Skyrim" [WRLD:0000003C] at -22,17)) Cutting Room Floor.esp [REFR:00098CD6] (places DirtCliffs03PineForest02 [STAT:0005B7E2] in GRUP Cell Temporary Children of CRFFrostRiverSmithCell [CELL:00009388] (in Tamriel "Skyrim" [WRLD:0000003C] at -22,17)) Cutting Room Floor.esp [REFR:00062EAE] (places RockCliff04Snow [STAT:00024C94] in GRUP Cell Temporary Children of [CELL:0000907B] (in Tamriel "Skyrim" [WRLD:0000003C] at 18,10)) Cutting Room Floor.esp [REFR:000D5FC0] (places RockPileL01Snow [STAT:00032A94] in GRUP Cell Temporary Children of StonehillsExterior02 [CELL:00009395] (in Tamriel "Skyrim" [WRLD:0000003C] at -2,16)) Cutting Room Floor.esp [REFR:000424AC] (places RockPileL03TundraRocks01 [STAT:0003ABE0] in GRUP Cell Temporary Children of WhiterunExterior01 [CELL:0000961B] (in Tamriel "Skyrim" [WRLD:0000003C] at 4,-3)) Cutting Room Floor.esp [REFR:000FE25E] (places CollisionMarker [STAT:00000021] in GRUP Cell Temporary Children of RiftenCitySoutheast [CELL:00042243] (in RiftenWorld "Riften" [WRLD:00016BB4] at 43,-25)) Cutting Room Floor.esp [REFR:00080C4E] (places RTWall06InnerCRF [STAT:1101F659] in GRUP Cell Temporary Children of RiftenCitySoutheast [CELL:00042243] (in RiftenWorld "Riften" [WRLD:00016BB4] at 43,-25)) The sad truth with the large reference bugs triggered by large references being overwritten is that most people including mod authors have not read the explanations or understood the problem and its possible workarounds. Hence they can not make qualified statements about it. A statement like "it works" does not mean there can not be problems. The game is failure tolerant to a degree. If the player never goes to an area where a missing assets are used, then there won't be a noticeable issue for example. As explained, DynDOLOD tries to ignore problematic assets or records for the very reason to avoid triggering any issues. As the past years have shown, CTDs and other issues are almost always caused by third party assets or plugins. Reporting the problem and then trying to skip over it for LOD generation means no CTD "caused by DynDOLOD" as people often put it, but can still mean visual inconsistency. The log message are printed so that they can be investigated and addressed if necessary. If you believe a specific log message to be wrong about a problem then report that. If further explanations or investigation of a particular issue in a mod is needed, then ask about that.

This is a vanilla bug. The LOD model included in DynDOLOD Resources was supposed to fix it. Maybe it is the wrong LOD model (I will need check that) or may be there is a plugins moving the wall.

Does xLODGen not start in SSE game mode or does it not output the LOD files to F:\xLODGen\SSELODGen_Output when starting from the short cut? You should be using a proper mod manager like MO2. Especially if not knowing basic computer things like command line parameters. https://www.bleepingcomputer.com/tutorials/understanding-command-line-arguments-and-how-to-use-them/

I have no idea what your game or mountains are supposed to look like, so "looking strange" does not describe anything. Make sure to install the MajesticMountain LOD pack.

Again, try to answer the question. Open console and click the weird stairs and get their form id, then look it up in xEdit and check its Editor ID if it is in a DynDOLOD plugin. It should tell use a plugin name and form id that this originates from. Which DynDOLOD version are you using?

Does the weird step have no form ID when clicking on it with console open?

Are you sure that the weird step is in fact that reference form id? DynDOLOD setting the HasLOD flag does not change the model or texture. Are you certain the wierd step is not a new reference with a different form id? Did you install the new swindmill.nif after generating LOD? Generate LOD from scratch for thew new load order with the new swindmill.nif already installed. No clue what the solitudebase.nif have to do with LOD/DynDOLOD though or what it is that the arrow in the last screenshot is pointing at.

Read the first post what log files to upload when making posts. Are you trying to update existing DynDOLOD plugins made with an earlier Alpha version? Try generating from scratch instead. I am not sure what the question is? Read the explanations given for each message type, about the severity and if they require action.

You didn't answer my question. What are the DynDOLOD plugins doing to the two form ids you mentioned? Assuming that the reference and base record are actually the object in question. Double-check you have right reference form id. What are the supposed conflicts of solitudebase.nif and swindmill.nif with DynDOLOD? DynDOLOD Resources SE does not contain these meshes, so with what do these meshes conflict?

So what are the DynDOLOD plugins actually changing , especially the DynDOLOD.esm for the mentioned records in your case? You seem to know but didn't actually write it... Unclear what the TexGen log is supposed to show? Generating LOD textures does not affect full models.

Read the first post of the DynDOLOD 3 Alpha thread where to make posts when participating in the DynDOLOD 3 alpha test. I moved the post to the thread. Read the first post what debug log files to also upload when making posts. Really read the entire message. You may be misinterpreting its meaning. Read the explanations from the "Click on this link for additional explanations and help for this message" if the link exists. Use the "Copy this message to clipboard" from the message to copy and paste the message when making posts. icewall01_n exists in Skyrim - Textures4.bsa

Code 80070005 means that Texconv was denied access by the OS, UAC, antivir etc. If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\logs\DynDOLOD_TES5VR_log.txt ..

Always use the x64 version. There seems to be a problem with BSA file(s) contain terrain LOD meshes. Verify the BSA files are valid and that the tools are not preventing from reading the by the OS, UAV, antivir.

CTDs are typically caused by 3rd party assets. It's always a good idea to really troubleshoot and fix them. Disabling something is a troubleshooting step and not a fix. Older versions report missing meshes and root nodes being NiNode etc. as well. Problems or warnings in the load order are not going away because there is no log message about them for easier troubleshooting.

Read the first post which entire (for the last meaningful generation) log files to upload when making posts. Check https://dyndolod.info/Messages for the explanations of log messages, warning and errors and the severity and if they require action. Check the summary (..\DynDOLOD\Summary\DynDOLOD_Index.html) which consolidates many of the same log messages into an easier to browse format with the explanations. Do not install 3rd tree LOD party billboard, instead use TexGen to generate all desired billboards. Read the DynDOLOD FAQ answers for ILS or CTD and the ..\DynDOLOD\docs\DynDOLOD-README.txt how to troubleshoot CTD. The easiest option is to check the .Net Framework Crashlog if available. Post it if help is required with it or just ask if you have further specific questions.

Would it be possible to answer all my questions about the texture? Or tell me which tree mod they are from? Upload the debug log from the older version. If you have no interest in providing the requested information or troubleshooting, then don't bother. As explained, Grass LOD is done in object LOD 4. It renders as far as the corresponding INI setting fBlockLevel0Distance which can be changed in the DynDOLOD SkyUI MCM Settings.

The message The requested operation requires elevation means that there is some OS permission problem. There should be no need to run the tools as administrator. Make sure the game is not installed to Program Files x86. Unfortunately you did not upload the log.

So what is the last tree LOD billboard that generates? Is it always the same? What is the resolution of Textures\landscape\trees\TreePineForestBranchComp.dds, its compression format and file size?

Reboot, do not start other programs while running the tool. Check video memory usage while the programs runs to see if usage gets anywhere near its max size. Run one TexGen option at a time. The output can be merged. Check and post if it always happens at the same part. This could be caused by problems with the hardware, overclocking, bad memory, wrong BIOS settings etc.

https://en.wikipedia.org/wiki/Event_Viewer

Why do you keep posting irrelevant logiles from the x86 version that have a clear error message? x86 programs are limited by consumer Windows to a max of 3.1GB. xLODGen/DynDOLOD/TexGen write the log files when they are closed. The exception handler writes the bugreport.txt. Looks like the OS, antivir or whatever might just terminate the program without it letting it handle whatever the issue is. Check the Windows Eventlog for related message(s).

Uploaded a new DynDOLOD DLL version for Skyrim Special Edition 1.6.342 (Anniversary Edition). It requires SKSE64 2.1.4 or higher.