kcbaxton

So I have the DynDOLOD log and bug report log, anything else I should upload? Thank you for helping, by the way. DynDOLOD Log: https://ufile.io/ss8eqnvd Bug Log: https://ufile.io/ljugat59

Sorry, double posted. That error was from an old run a few weeks ago, I forgot to esl some patches I made. I haven't added any new worldspaces since the issue first appeared. Here's the log from only the last run. https://zerobin.net/?763e1f51f4909409#JWlDflzWr2VbCnEd+eXQ+soa6B2U2a7T8ZkEDy6Bxco= The only error is from BSHeartland, which I've been using since I created this modlist.

I'm no stranger to the process of DynDOLOD, I'm sure there isn't any old output data in my game. It must be a bad edit from a mod, because it's there everytime, and it's only LOD so I can't click on it in the console. The question I was asking is how to figure out what mod is adding that without spending months removing a mod, rerunning DynDOLOD, ect. over and over. Log: https://zerobin.net/?529d0dd026026335#pju5WTsrljhCuDfk5yTuyDbQtfSiGZB3N99qarjSWc0=

I'm certain it's a bad edit, I've used DynDOLOD many times and I am very familar with process. This was a completely fresh run definitely without any old output data, so something in my list is adding it there. The question I was asking is how to find what mod that is without having to spend a month removing a mod, rerunning DynDOLOD, ect.

I regenerated Texgen, DynDOLOD, and Occlusion from scratch, and unfortunately the object LOD still persists.

@shesonAs I said, I am unable to click on the object, because it isn't an object at all, it's just an LOD. Moving up to it with the player causes it to dissapear, and when I use the freecam to move to it, it's still unable to be clicked on in the console. You are referring to the DynDOLOD_SSE_log in the DynDOLOD folder, yes? There are no mentions of wild edits or deleted references in it.

Hi, I am experiencing an issue with floating LOD models high above northern Whiterun, near Volunruud. They can be seen from all over the map. The problem for me is that they are just LODs without static models, so using tcl and running up to them causes them to disappear, and they also can't be selected with the console in free cam. Because of this, I'm not sure how to see what mod it is from. My question is, how do I find out what mod is placing them there? And once I do, is there a way to remove them from my game without rerunning DynDOLOD?

I tried the fixes in both links he provided, no luck. I did exactly what was stated in the first, opened up xEdit and searched for 00050372 to see what was conflicting. Exactly as stated in the post, it was HD LOD Texture's snow shader overwriting Majestic Mountains. The user in the post said removing that file from the esp fixed their problem, however it only made mine worse.

Still no luck. Messing with the snow shaders did not do anything. Any other ideas?

Thanks for the quick response. I deleted 00050372 from HD LODs Textures.esp (it was overwriting MM) as stated in the first link you posted, and it only made the problem worse. Now All my mountains look gray like in the screenshots until I get up close. The second record (0006ae38) was not being overwritten by anything. I'm truly at a loss here. I know it sounds dumb and it's probably something obvious I'm overlooking, but like I said nothing about my load order was changed on my break, especially not any core mods like MM or LODs. I'm considering removing BDS and rerunning DynDOLOD.

Hey, thanks for the response. I'm using MO2. Running BethINI did not help.

Hi, so I'm having a very weird problem with my LODs. After a few hours of gameplay, my distant mountain LODs suddenly changed to an ugly gray instead of the usual Majestic Mountain textures. What's weird is that they changed on their own. They were completely fine for the first ~10 hours of my game, and after coming back to Skyrim after a week long break I'm now having this problem. I've used DynDOLOD for a very long time and never had any issues with it, which is why this problem is so perplexing. Nothing about my mod list was changed. DynDOLOD is still active, dynamic LODs are still there, however they are flickering a little bit now. Trees and everything else look fine. Rerunning DynDOLOD doesn't fix my current game. I had this problem a while back, so I re-ran DynDOLOD and started a new game, which fixed the problem, for a while at least. However the problem is once again persisting on its own, which means it will probably happen again eventually even if I start new game. I've moved the DynDOLOD output to the bottom to make sure it's not being overwritten. It could possibly be an .ini problem, I used to z-fighting fix on my Skyrimprefs.ini found on this website, however changing it back did not fix the problem. Here's a couple screenshots of the issue: https://imgur.com/a/HN6S2Up I've done everything I can possibly think of at this point, so some help would be greatly appreciated. Thanks.