markuskarttunen

That works perfectly, thank you so much!

Apologies for the late answer. Linked here is a .7z containing the logs requested, a folder called "example mod" with the LOD model, the model it represents and a small plugin with the LOD references ready if you need to test in on your end. Also included three generated object .BTOs, 4, 8 and 16.x.x, where 8 and 16 work as expected but the 4.x.x shader is left as default. Thank you for taking the time and if you need any more logs or assets to take a look at, please let me know!

Hello Sheson, hope you are good. I have a slight setup problem I couldn't find a solution to in the DynDOLOD info website, that I was hoping you could help me with. Essentially, I have a bunch of statics with Glow Shaders, and a similar bunch of LOD models derived from those statics, also with Glow Shaders. As I run DynDOLOD, the Glow Shader (BSLightingShaderProperty - Skyrim Shader Type) and other relevant shader flags are passed along only to the 8.x.x and 16.x.x object lod .BTOs, but not the 4.x.x .BTOs. I am happy to provide the logs and assets as you need them, currently I am stuck trying to debug the situation and any nudge towards the right direction would be appreciated. Thank you!

I am addicted to changelogs and I can't help but to notice v151 hasn't got one. Please sir, I need my fix

Funnily the latest A106 has caused no issues but some earlier versions have consistently blackscreened on me. Imma take a look at my drivers once more, I know I don't have the adrenaline installed (since nothing on it works anyway) but can't remember if I factory reset it back in the day. Thanks!

Really? I've thought it'd have a lot of GPU stuff going on as if I blackscreen during a lod generation it happens right after the little lodgen window pops up, pushes a couple level 4 lods and everything goes black.

I'd love to come back with results on this one but unfortunately AMD has decided to bless me with the blackscreen-treatment with that version of LODGen. I've got the latest recommended drivers but this just happens on some versions of dyndolod, I've decided to live with it until I get around buying a 4090 or any other card with drivers that don't crash daily.

Interestingly, as far as I can see I didn't notice any shift (as in moving the billboard along any axis) but rather a whole turn from the side view, which does look better though; pictured here. I haven't touched the trunk nor the crown models between these two runs. From afar it looks rather good now unless zoomed in from an angle, which I don't think is possible to counter with a model like this on hybrids, but I think I'm going to release a stripped down 3D version of the trunk anyway.

Yeah the silhouette only gets broken with these wonky trunks where it takes a sharp turn one way and the turn doesn't get mirrored on the side that wasn't rendered from. On my LO that'd basically just be reachtrees and reachclifftrees so 4 trees in total, which admittedly doesn't warrant a big change in the rendering process that works perfectly fine with the straight trunks most trees have. Thanks for your time and I'll get to decimating some reachtreetrunks

Hello Sheson, thank you for DynDOLOD and especially it's Hybrid tree LOD feature. Its a game changer and allows for near-seamless transition of LOD and full models without tanking performance. I have a question/request on it, I have no idea if it's possible though but thought I'd ask. Would it be possible for TexGen to generate the hybrid tree trunk renders from all 4 sides instead of 2 and apply them on their respective one-sided planes if template4.nif is selected as the flatnif? This would make them more consistent on tree models that have a very "chaotic" trunk geometry (eg. ReachCliffTree01 pictured here). Thank you for your time