Can not find textures

[redshift87]

I recently upgraded to DynDOLOD 2.59 and am now getting an error I've never seen before:

 

[00:03:18.731]    Preparing texture data
[00:03:18.759]      Can not find textures\mrkwalkwaysa01.dds for texture atlas
[00:03:18.775]      Can not find textures\mrkbuildingslod03.dds for texture atlas
[00:03:18.791]      Can not find textures\mrkbuildingslod02.dds for texture atlas
[00:03:18.812]      Can not find textures\crackrock4var3.dds for texture atlas
[00:03:19.473]    
[00:03:19.473]    Exception in unit userscript line 331: File not found: textures\crackrock4var3.dds
[00:03:19.473]    
[00:03:19.473]    Check log lines above the exception for additional hints. Check the FAQ and search official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/ for those errors.
[00:03:19.473]    
[00:03:19.473]    If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_TES5_log.txt to official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/
[00:03:19.474]    Error: File not found: textures\crackrock4var3.dds
[00:03:43.723]    [03:41] Saving: DynDOLOD.esp
[00:03:43.831]    [03:41] Done saving.

I installed the 2.59 resource pack, ran Texblend, and followed the upgrade procedure like usual. I'm running the x64 version of the dyndolod exe so I don't think it's a memory issue. There haven't been any big changes to my load order since I last successfully ran an older version of dyndolod. The only big change I can think of is that I upgraded Unslaad to version 2.

I searched my Data folder for that crackrock4var3 file and actually found it in ...textures\architecture\markarth not just loose in textures where dyndolod appears to be looking. Not sure if this is an error on my side or a misconfiguration in DynDOLOD?

logs.7z

[sheson]

The texture paths DynDOLOD looks for are typically found in the meshes used for LOD. So you would have to find out which meshes define those exact texture paths (it is possible the meshes only define the texture filename.dds without the "textures\" part) It may be possible those come from texture replacements, so it seems unlikely in case of the LOD textures.

 

It is kind of supposed to just print a message earlier and then ignore them though, not quite sure why that is not happening here.

 

Make sure to remove any old DynDOLOD Resources before installing the new version.

Edited April 3, 2019 by sheson

[redshift87]

Thank you for the reply Sheson!! I double-checked, and I did remove the old resources completely before I upgraded so I'm not sure what the trouble is.

I ended up taking the easy way out and just copied those textures that it was complaining about into my base textures folder, and then the process completed without a hitch. I will delve deeper into the cause if I have the time later. I'm sure you're right and some of my LOD meshes must be pointing to the wrong texture paths.

[sheson]

Thank you for the reply Sheson!! I double-checked, and I did remove the old resources completely before I upgraded so I'm not sure what the trouble is.

 

I ended up taking the easy way out and just copied those textures that it was complaining about into my base textures folder, and then the process completed without a hitch. I will delve deeper into the cause if I have the time later. I'm sure you're right and some of my LOD meshes must be pointing to the wrong texture paths.

It is totally possible something goes wrong somewhere in DynDOLOD. For the next version I will try to add a debug line first time a new texture path is found that will also print the source mesh. That should help with easier troubleshooting

[redshift87]

Are the old versions of DynDOLOD (exe + resources) archived anywhere? What's on the Nexus under Old Versions are very old. I'd really like to try running 2.57 or 2.58 again as a quick test.

[redshift87]

Well damn. Still having issues; I've gone through the complete uninstall of old Dyndolod resources and exe folder / reinstall of version 2.59 a couple of times now, always doing the clean save upgrade procedure. While I've bypassed those texture errors I was getting, something else is still very wrong. The DynDOLOD exe tells me that the worlds were completed successfully, however, when I load up my game and go outside the distant lod is very empty and obviously wrong (I checked in the MCM menu and DynDOLOD is active). High Hrothgar and Dragonsreach are invisible, except for floating windows for example. I even started a new game thinking maybe there was something borked with my existing save, but the new character has the same problems. Even though I haven't made any recent ini changes (and used Beth INI to generate my current files) I also tried resetting things with Beth INI as a test but that also had no effect.

 

I've run through the DynDOLOD upgrade procedure many many times on past versions with no issue, and have made no major changes to my load order or settings since I last ran version 2.58 (or maybe it was 57) successfully with no issues. I'm pretty stumped at this point. Most recent logs attached.Logs.7z

Edited April 6, 2019 by redshift87

[sheson]

The screenshots look like the LOD distances in SkryimPrefs.INI / DynDOLOD SkyUI MCM - Settings are set to very short distances.

 

The log shows you only have a handful of tree LOD billboards installed. Most of them are not found.

 

The logs seems to indicated the object LOD seems have generated fine.

Edited April 6, 2019 by sheson

[redshift87]

I haven't made any changes recently to my view distances or settings, but I went ahead and went into the DynDOLOD MCM and maxed out all the distance settings (screenshots below) but no change. I made sure to change cells a few times in case it's not an instant update.

You're right - in my last nuke everything and restart attempt, I forgot to reinstall my tree billboards. I've done so and ran an update of DynDOLOD, but it did not help with the empty distant lod.

 

Something odd I noticed, in the Info section of my MCM menu it says my DynDOLOD.esp version is 2.45 even though I installed version 2.59

[sheson]

maxed out all the distance settings

WTF? Reset the values to sane default settings. Use BethINI.

 

You're right - in my last nuke everything and restart attempt, I forgot to reinstall my tree billboards. I've done so and ran an update of DynDOLOD, but it did not help with the empty distant lod.

Check the LODGen logfiles do not contain error messages and everything looks normal. Check the generated BTO files have OK file sizes and open some in NifSkope to check they contain the object LOD meshes.

 

 

Something odd I noticed, in the Info section of my MCM menu it says my DynDOLOD.esp version is 2.45 even though I installed version 2.59

It's the data/API version for the scripts. That is the correct version.

Edited April 6, 2019 by sheson

[redshift87]

I do use BethINI and reverted my settings after that test. I was just trying to illustrate that no matter what value I changed the view distance to, had no effect.

All LODGen logfiles exited with code 0, don't see any errors.

What is an ok file size for the bto files? Mine range from 1 kb - 6,000 kb. The 1kb btos just show an empty grid in Nifskope, the larger ones actually have objects as expected.

 

Do you have a GitHub project or other version control archive? I would really like to revert and test one of the last few versions that I had no issues with before. Clearly I missed something in the upgrade or else something in my setup is not compatible with 2.59  :-(

[sheson]

The "empty grid" is water, so those are oceans.

 

There is nothing wrong with DynDOLOD and the LOD DynDOLOD generated.

 

It seems something is messed up in the load order.

Edited April 7, 2019 by sheson

[redshift87]

Thanks for all your help, sheson, I really appreciate it. DynDOLOD is amazing and I'm not sure I can play Skyrim without it.

I went through all my plugins, checking for errors, but there was nothing serious. I also always have DynDOLOD.esp loaded last.

 

Do you have any suggestions for what specifically I should be looking for in my load order? SMIM is the only "some assembly required" mod that I use. I do have Majestic Mountains installed, folded into my Merged_Misc plugin, and from reading through the forums here MM might not play nice with DynDOLOD?

[sheson]

If you have a load order that does not show object LOD do some basic troubleshooting:

 

Remove all of the DynDOLOD output. If the problem still exists, then fix the INIs / settings / whatever other mod is causing the problem.

 

If removing the DynDOLOD output makes things go back to normal, then first only enable the generated static object LOD in the meshes/textures folders but do not enable plugins. 

 

If things go wrong then something is wrong with the meshes (or textures though unlikely). In that case upload meshes\terrain\tamriel\objects\tamriel.4.4.-4.bto, which should show the plains district from Whiterun, so I can verify it. Include Textures\DynDOLOD\LOD\DynDOLOD_Tamriel.dds and *_.dds.

 

If the generated static object LOD meshes/textures work fine and things only go wrong when the plugins are enabled, test with a clean save. If things are still wrong with a clean save, check the 3  INIs via MOs puzzle icons / INI Editior. If all fails upload those plugins and include the INIs shown in MOs INI editior.