DynDOLOD installation error and discrepancy

[RainyDayMatt]

I've been following the STEP guide to the letter, and I've made it down to the very end of the patches section without any crashes. However, I've been attempting to properly configure DynDOLOD for several days now, and I am continually experiencing CTDs - after starting the game, as I load a save (I also tried a new game, with the same crashes). I followed the detailed instructions to the letter with regard to installation, generation of LODs, and generation of DynDOLOD. If DynDOLOD, the archive imported during the Generate LODs section, and the archive imported during the Generate DynDOLOD section are all ticked, I get crashes; if I disable the last imported archive (from Generate DynDOLOD), the game runs, but I experience MCM complaints about inability to reach the JSON files. Is there any step implied by these errors that I might've missed or performed incorrectly? Is there a stack trace or other error log that I might examine?

 

 

 

 

Also, the GamerPoets video includes download of billboards (vanilla, as well as SFO - which I installed as part of STEP), but skips generation of LODs and use of the TexGen script; is that video out of date? Should I be following it, or the written guide?

 

[TechAngel85]

You should follow the written Guide. It will be the most up-to-date of the two.

 

If you're having troubles, I would start fresh by deleting the mod and reinstalling a fresh copy to use. When loading saves, make sure you're not loading into a save that already has DynDOLOD present in it; else, you need to follow the updating procedures found in the DynDOLOD manual. This manual is found with the mod, if you installed it according to our directions.

[RainyDayMatt]

I'll try it again. My STEP compilation/patch is showing version # 1.2. instead of 2.2.9.2. as in screenshots. I've deleted and readded, with no change. Is that a known issue?

Edited February 12, 2016 by RainyDayMatt

[GrantSP]

  On 2/12/2016 at 6:36 PM, RainyDayMatt said:

I'll try it again. My STEP compilation/patch is showing version # 1.2. instead of 2.2.9.2. as in screenshots. I've deleted and readded, with no change. Is that a known issue?

Not an issue as such, just an oddity in the way MO pulls the version numbers of files from the Nexus page. You can simply change the version number in MO via the "Information" dialogue and viewing the 'Nexus' tab.

Or by double-clicking on the version number in the left-hand pane.