TheCounterpoint

[00:45] <Warning: File not found textures\dyndolod\lod\trees\treepineforestbroken06_09e933e6_trunk_1.dds. Used by meshes\dyndolod\lod\trees\treepineforestbroken06_09e933e6passthru_lod.nif Dragonborn.esm DLC2TreePineForestBroken06 [STAT:0401D500]> [00:45] <Warning: File not found textures\dyndolod\lod\trees\treepineforestbroken06_09e933e6_trunk_2.dds. Used by meshes\dyndolod\lod\trees\treepineforestbroken06_09e933e6passthru_lod.nif Dragonborn.esm DLC2TreePineForestBroken06 [STAT:0401D500]> [00:45] <Warning: File not found textures\dyndolod\lod\trees\treepineforestbroken06_09e933e6_trunk_1.dds. Used by meshes\dyndolod\lod\trees\treepineforestbroken06_09e933e6passthru_lod.nif Dragonborn.esm DLC2TreePineForestBroken06 [STAT:0401D500]> [00:45] <Warning: File not found textures\dyndolod\lod\trees\treepineforestbroken06_09e933e6_trunk_2.dds. Used by meshes\dyndolod\lod\trees\treepineforestbroken06_09e933e6passthru_lod.nif Dragonborn.esm DLC2TreePineForestBroken06 [STAT:0401D500]> and indeed these textures are not included within the resource files, and I'm pretty sure they are not from a custom mod

working fine now, thanks

the images regarding xlodgen settings are not loading from postimage

here's a save, whiterun facing some houses, load it up and the bug will be present on the roofs (like in the video) this is vanilla ultra settings, so fFirstSlice 2000, fShadowDistance 10000 and 4096 shadow resolution no mods if you test the save, please report your video card model. I suspect this is a shader issue tied with specific hardware I have a gtx960 btw https://www.dropbox.com/s/6r63si2fe4u58by/Save3_00000000_0_4E6F7264_WhiterunWorld_000036_20190701212713_1_1.ess?dl=0

100% vanilla shadows, no enb no reshade no nothing. I'll try to pick a save to see if more people can reproduce this.

testing I done on skyrim special edition in the hopes of dealing with this bug fShadowBiasScale don't do nothing, no matter the value fFirstSliceDistance max value is half of the fShadowDistance value (I try to set both the same, since that bug happens at the end of fFirstSliceDistance), maybe there is a way to change this and match both values?