z929669

using Level# at higher LOD# means 3D models in far distance. Much worse performance. I use 175/60 for HD Tree. This will likely increase the specular of normal faces on the 3D models in the distance though. Experiment with something like 25/125

For some meshes, NiAlphaProperty is definitely required to get the effects; however, for the firewood NIFs, I can see no relevance whatsoever, since the mesh polys align with the vanilla textures in terms of UV mapping and the physical dimensions of the meshes. If someone were to create a replacer with a sloppy alpha opacity, it would probably still look okay on firewood. Contrast that with some other meshes that are basically relying on the texture alpha opacity to look right, because the mesh is basically wrong: ... this mesh actually uses textures\landscape\trees\treepineforestbarkcompsnow.dds as an alternate for this, and since that texture has no alpha opacity (it's bark), it looks wrong. This is something T4 will need to fix by either removing the texture set (and letting mods like BDS handle snow), or create a proper alternate snowy texture with proper alpha cutout. PS: My guess is that this mesh was derived from vanilla, as I doubt the MA would have done it. I don't know though.

Specular/glossiness and all other parameters on the mesh were vanilla, and changing them to same values for HLT trunk bark meshes shows no difference (glossiness reduced from 80 to 10, emmissive multiple reduced from 1 to 0). In fact, looking at the vanilla stuff shows similar 'shininess' if you look closely at the bark in small areas (the contours of these barks are flatter) ... I think it's the normal maps personally. No alpha on those. I can test, but I doubt T4 will want to change his normals.

@TechAngel85 For some reason, neither BDS or SoS mentions the other on the Nexus mod description. These mods essentially do the same thing, but neither mentions the other in terms of compatibility or makes this clear in any obvious way (nor how they differ). Reddit has a somewhat dated discussion, but the info there is completely unreliable (as is most of what I find on Reddit ... PS: I hate Reddit). It would be great if you or Sparrow (or wSkeever) could shine a light on this really obvious discrepancy. I think it would clear up a lot of confusion and prevent people from running both or deciding on one or the other. PS: This came up in my realization that @Mousetick seems to be using SoS and cannot get snow on vanilla firewood meshes, due to NiAlphaProperty ... BDS doesn't have this issue, BTW.

Vidistis wants to choose a text color, I assume. So sounds like it's not supported. Only background (which is supported, and I can attest to that with my many-colored separators).

You need to look at your ..\DynDOLOD\Logs\DynDOLOD_SSE_Tree_Report.txt to see what LOD models are or are not found according to your plugins. My guess is that these are vanilla billboards and that you are trying to run multiple tree mods that affect the same vanilla trees, and the winning plugin doesn't find the LOD models you need. Only install ONE tree mod. Remove all LOD models for trees from other mods. Re-run TexGen and DynDOLOD.

FIrst: Based on those screens, the only "shininess" I see is due to the vanilla textures. The HLT stuff doesn't look shiny to me where vanilla textures aren't in play. Looking in game, I also don't see the issue. The firewood meshes are vanilla with UV tweaks ... that's all. I think the issue may be with the alpha of the diffuse. Eliminating that should resolve if you want to give it a try to test. These are in the trees, so I kept it for the firewood. Otherwise, removing the NiAlphaProperty or lowering the alpha threshold to like 50 would probably also resolve. This is an issue with stumps at Fort Dunstad for same reason (although the UV on that needs fixing if the NiAlphaproperty is removed). I will likely remove the diffuse alpha and the NiAlphaProperty from the mesh. T4 is back working on the mod though, so I don't want to 'collide' with any changes he's making. I cannot speak to the shrubs. Some dude recently asked for perms to use HLT assets for that one I think. @Mousetick The NiAlphaProperty is only an issue with SoS. BDS works as expected in my testing. I don't know yet why these meshes have it, because removing it doesn't cause any noticeable clipping (as is the case in other situations I have tested (see my explanation in the recently reported HLT Bug "Tree snow stump tops") Tested a few things: HLT+BDS (textues with alpha, NiAlphaProperty exists) >> HLT+BDS (textues wo alpha, NiAlphaProperty exists) >> HLT+BDS (textues with alpha, NiAlphaProperty removed) There is no difference I can see This is clear weather at about 10 AM with sun at about 2 o'clock ... I suppose there is some shininess, but not really 'shiny', IMO

I use parsing by defualt and never notice this. I agree with the assessment in principle an will look at it.

I'm fine with adding this, as it has no issues for me and adds needed variation. We would also want to install some of the add-on mods: Security Overhaul SKSE - Add-ons Security Overhaul SKSE - Gems Patch - The Cause Chests Secured Security Overhaul SKSE - Regional Locks Requires version 3.0 or higher Security Overhaul SKSE - Some More Locks Must have Soul-Cairn Objects Secured I'm fine with adding any of these ...

The Conflict Resolution Patch was updated to remove unrequired masters in order to grant more flexibility to users. These were not cleaned out in the previous update. There is no need to update this file if the current build is working as desired. Removed masters: - Odin - Skyrim Magic Overhaul.esp - ClavicusArgonianMasque.esp - ButterfilesUnchained.esp - Atlas Map Markers.esp

Added new Saints & Seducers TCIY patch to the wiki list

I installed the 2K variant, but it may not matter for the minigame performance or general performance if it's 4K

I agree that it looks like a mesh issue, but I know little about head meshes and facegen stuff other than that they are finicky. I would run the LE meshes through SSE NIF Optimizer in converting them to SSE and look on that mod page for assistance. I think it's the best LE-SE conversion optimizer available, and those guys know quite a bit about this stuff.

They should be cleaned, so you must've borked it somehow. Try repeating the cleaning process, and ensure you are using correct version of xEdit and have the autoclean version configured correctly. Recommend to re-validate Skyrim files and repeat. Where does it say this? The guide says that ALL DLC are required, even the Anniversary Update DLC. Technically, many of them are not required as masters, but many are. You can't pick and choose the Anniversary Update CC-DLC. It's all or nothing.

Adding to Tech's note: We do this so that those large overhauls aren't required as masters, and while the changes are small, they are needed for consistency for the majority of our users using those mods. The trade-off is the minor inconsistency for those not using these mods in favor of a more important consistency for those using these mods, which is also a majority of users.

I'll be sure to check it out. Thanks back!

There are likely considerations for ESL specifically that others may mention, but general steps to manually removing a patch dependency are outlined here:

Myrkvior for one has the same issue. It's largely an issue with vanilla-derived pine trees in general. It has been noticed, but others have largely resolved it to acceptable degree (as I have demonstrated). Agree. And as I have mentioned multiple times, there are two mesh vertex-color variants, two mesh size variants, and no less than 6 texture variants in the Lush version of EVT alone. That is 2 * 2 * 6 = 24 possible variants in this single version. With Basic, there are at least 12 more, and with Custom Trees, you can create far more than even Lush. We haven't even considered the SFO variants ... I have tried third-party vanilla trees textures with EVT for kicks (because EVT is compatible with vanilla pine texture replacers), and found that the tree tops were significantly darker or lighter with those, depending ... so just trying different branch texture versions alone can change this ... but for some reason, when multiple 'fixes' are right there, advice and suggestions are not heeded. EVT has a configuration for just about any ENB. Approaching the 'problem' methodically would arrive at the solution rather quickly, I think

We specify instructions for the optimal result. Use the exact guide instructions for an ideal result. The guide explains where you may want to improve performance or quality. Anything mentioning 4k setting or 'Ultra' is best, but caveats apply. It's really all in the guide.

Just follow the instructions and GUI images in the guide for generating terrain and object LOD. Also follow instructions for DynDOLOD and ACMoS configuration. There is nothing to explain in the forums. It's all in the guide in exact and complete detail. You just need to read and follow to get the correct result.

Sheson will want to see the logs as described in the OP. Debug log for one. Upload to a file service is simpler for those looking. See links in forum rules and OP

Posting this as a spoiler when it is too large makes no sense. Try searching your log for 'error' to find that you have exceeded the plugin limit for one: [00:00:00.306] Exception in unit prepare line 60: Too many full modules [00:00:00.306] [00:00:00.306] Remove or merge plugins so there is room for the DynDOLOD plugins to be added to the load order. [00:00:00.306] [00:00:00.306] If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum https://stepmodifications.org/forum/forum/223-shesons-dyndolod-xlodgen/ [00:00:00.310] Error: Too many full modules ... I will venture to guess that the issue is with one of the many additional worldspaces you are using? Also, please actually read the forum posting rules. Your log contains at least three separate run outputs, which is one reason why it's large. I assume this is not your debug log, or it would be much larger. The forum rules also recommend better options for uploading huge logs into actual files that can be downloaded and searched.

Then you possibly still have DynDOLOD output from a previous run in your mod list. You must run TexGen and DynDOLOD on your mod list cleaned of all plugins and mods (and outputs) used in previous runs. There could also be a 'bad' edit in one of your plugins. You will need to supply logs as described at the top of this forum and several other places if you want explicit and accurate instructions. Otherwise, be deliberative and check your mod list carefully.

Droppedfor 2.1.0 in favor of Obsidian Mountain Fogs Tweaked

I vote for using this one in 2.1.0 with 10% reduction to replace the original. It fixes some plugin issues and preserves the effect.