ShawnTheGuitarist

After updating to Alpha-89 the issues could not be reproduced, so that may have been the solution.

This is my first time using the posts, so I hope I provide everything you need. Let me know if I miss anything. The plugin that sets the parent is Perfecter Whiterun.esp as far as I can tell. Here's a screenshot of my xEdit showing the Perfecter Whiterun.esp plugin containing the enable parent reference. I've uploaded the bugreport.txt and DynDOLOD_SSE_log.txt, but strangely I couldn't find a [Worldspace]_log.txt for WhiterunWorld. I'm wondering if that might hint at a problem. Also, I did just notice when manually looking up xx00401C that it is among several Placed Objects not flagged as conflicting, but yes those are also missing the enable parent flag. There's quite a few records like this.

I have tree billboards appearing within the WhiterunWorld cell while running the latest DynDOLOD 3 Alpha 89 (screenshot here to keep my post short). I'm using Perfecter Whiterun, Enhanced Vanilla Trees SE, and Happy Little Trees. Letting xEdit load my entire mod list and selecting Perfecter Whiterun.esp to "Apply Filter for Conflicts" shows TreePineForest01 and TreePineForest01Dead have object bounds touched by Skyrim.esm, HappyLittleTrees.esp, and Enhanced Vanilla Trees SSE.esp. Looking at the Worldspace changes, the only other mod with conflict is USSEP for WhiterunWorld, which the Perfecter Whiterun mod page states are intentional. It looks like it's simply DATA Position/Rotation coordinate changes. Looking at each of the placed objects, I can see under XESP - Enable Parent that it is set to PlayerRef (00000014), which seems to match the answer given in the sticky post on Perfecter Whiterun about those flags helping ensure they do not get LOD generated for them.