DynDOLOD Beta for Skyrim Special Edition, Skyrim VR and Enderal SE 2.98

[sheson]

Lucky!

 

It is the new Realistic Water Two update that is causing the CTDs. Anything you need me to test or are you able to hopefully fix it with this information?

Hello. I wanted to add that I just now had the same experience with Realistic Water Two. Removing it from my game stabilized my DynDOLOD build while exiting buildings in Riften.

Great job. I will test with the new version myself and see what I can find.

 

Just thought I'd mention that the link to PapyrusUtil is still to the old Nexus which does not work anymore.

Thanks. Updated.

Edited July 1, 2018 by sheson

[tyrindor]

I did some more testing and it's not any of the Realistc Water Two patches (Wyrmstooth, iNEED, etc). I select "high" for texture resolution during installation, everything else default.

 

There's people that are using it without crashing, so hopefully you can reproduce it. I'm running the exact same settings shown in the tutorial, with high preset: https://youtu.be/90TRMvFdduo?t=195

Edited July 1, 2018 by tyrindor

[EZRAS]

Yeah, RWT is the issue for me as well. I installed the same except with medium preset. I also tried downgrading it to the most recent version before the current (v1.4.4) and still got the crash. Haven't tried earlier versions yet.

 

BTW, are you using the LOD fix?

Edited July 1, 2018 by EZRAS

[tyrindor]

Yeah, RWT is the issue for me as well. I installed the same except with medium preset. I also tried downgrading it to the most recent version before the current (v1.4.4) and still got the crash. Haven't tried earlier versions yet.

 

BTW, are you using the LOD fix?

The LOD fix shouldn't be needed with the newest version.

 

About a month ago, I had a ~30 hour save on 1.4.4 + LOD Fix with an older version of DynDOLOD and didn't have these problems. If 1.4.4 is crashing now, might be a recent change in DynDOLOD that is causing it.

Edited July 1, 2018 by tyrindor

[EZRAS]

The LOD fix shouldn't be needed with the newest version.

 

About a month ago, I had a ~30 hour save on 1.4.4 + LOD Fix with an older version of DynDOLOD and didn't have these problems. If 1.4.4 is crashing now, might be a recent change in DynDOLOD that is causing it.

Seems like you're right. Just tried v1.3.5 with and without the lod fix and still crashed.

[Grumbul]

Hi all,

 

I've recently looked at this video and managed to get everything to run quite nicely indeed:

When I first ran DynDOLOD everything seemed to work just fine but then I added som other mods and decided to re-run DynDOLOD.

Now for some reason I have two issues. Just a few of the pines now have purple tree textures and also the windmills have no blades.

I've tried a few solutions such as trying the oldrim EVT & Billboards meshes/textures but all to no avail.

 

[sheson]

Hi all,

 

I've recently looked at this video and managed to get everything to run quite nicely indeed:

 

When I first ran DynDOLOD everything seemed to work just fine but then I added som other mods and decided to re-run DynDOLOD.

 

Now for some reason I have two issues. Just a few of the pines now have purple tree textures and also the windmills have no blades.

 

I've tried a few solutions such as trying the oldrim EVT & Billboards meshes/textures but all to no avail.

If you have problems or questions about third party guides you need to ask the author of that guide. I can not support 3rd party guides.

 

Purple textures are a file not found problem. If the missing textures are related to object LOD (purple textures in the distance), then DynDOLOD log may print a file/texture not found message at LOD generation time.

 

In this case it sounds like texture are missing from full models, which has nothing to do with DynDOLOD or LOD generation at all. Missing textures are easy to troubleshoot with console, form id and looking up the model in xEdit and using the Asset Browser of xEdit to look up the NIF model. The Asset Browser lists the textures a NIF uses without having to open the NIF in xEdit.

[sheson]

Lucky!

 

It is the new Realistic Water Two update that is causing the CTDs. Anything you need me to test or are you able to hopefully fix it with this information?

 

I was able to reproduce the problems with RW2 and trace this back to a regression introduced some time after 2.36. This should be all fixed now in latest 2.40. Get it from first post.

[tyrindor]

I was able to reproduce the problems with RW2 and trace this back to a regression introduced some time after 2.36. This should be all fixed now in latest 2.40. Get it from first post.

Hurray! Thanks.

[Scandre1]

So do you remember how I brought up an issue with dyndolod where it would crash whenever I left an interior cell to a worldspace? I decided after some time that I wanted to figure out which mod it was that caused it and to my surprise it was Elysium Estate 5.01. I tried to figure out why this was the case (even thought it might have been unoptimized meshes, but that was not it). Simply disabling it before generation completely removes any issues. The thing that surprised me was that the older version of Elysium Estate was compatible with dyndolod, but that was back in the days of 2.36 of dyndolod.

 

Anyway I thought to let you and everyone else know that Elysium Estate 5.01 causes ctd's when leaving interior cells to a worldspace when dyndolod is generated with it activated in the  load order.

 

Edit: wrote down the wrong version of dyndolod

Edited July 1, 2018 by Scandre1

[Zanderat]

I was able to reproduce the problems with RW2 and trace this back to a regression introduced some time after 2.36. This should be all fixed now in latest 2.40. Get it from first post.

Thanks! Do we need to regenerate?

[Zanderat]

NM.  Can't edit.  Dumb question.

[EZRAS]

So do you remember how I brought up an issue with dyndolod where it would crash whenever I left an interior cell to a worldspace? I decided after some time that I wanted to figure out which mod it was that caused it and to my surprise it was Elysium Estate 5.01. I tried to figure out why this was the case (even thought it might have been unoptimized meshes, but that was not it). Simply disabling it before generation completely removes any issues. The thing that surprised me was that the older version of Elysium Estate was compatible with dyndolod, but that was back in the days of 2.36 of dyndolod.

 

Anyway I thought to let you and everyone else know that Elysium Estate 5.01 causes ctd's when leaving interior cells to a worldspace when dyndolod is generated with it activated in the  load order.

 

Edit: wrote down the wrong version of dyndolod

Thanks for mentioning, I use that mod and would have probably ragequit modding skyrim if I had to go through the whole trial and error process again.

[sheson]

So do you remember how I brought up an issue with dyndolod where it would crash whenever I left an interior cell to a worldspace? I decided after some time that I wanted to figure out which mod it was that caused it and to my surprise it was Elysium Estate 5.01. I tried to figure out why this was the case (even thought it might have been unoptimized meshes, but that was not it). Simply disabling it before generation completely removes any issues. The thing that surprised me was that the older version of Elysium Estate was compatible with dyndolod, but that was back in the days of 2.36 of dyndolod.

 

Anyway I thought to let you and everyone else know that Elysium Estate 5.01 causes ctd's when leaving interior cells to a worldspace when dyndolod is generated with it activated in the  load order.

 

Edit: wrote down the wrong version of dyndolod

I have no issues with Elysium Estate 5.01 and LOD generated with DynDOLOD 2.40 in Skyrim SE.

[Scandre1]

I did all the testing on 2.39 of dyndolod so it could be possible that you have fixed the problem. It might also be that the location where you do the testing is important. I did all my testing in whiterun running in and out of buildings like some madman and always got the ctd if Elysium Estate was active during creation of dyndolod. However I also noticed that if I started the game in Riften and did the same the game would not ctd. But if I went to whiterun and then back to riften the ctd's do happen again.