On running DynDOLOD 'worlds' script, I get following error about 40 minutes into the process:
Exception in unit create line 1197: Invalid floating point operation
The last several lines on the TES5Edit_log.txt are:
[00:40:53.732] Found C:\Games\SkyrimUtils\TES5Edit\Edit Scripts\DynDOLOD\DynDOLOD_TES5_manual_refr_Tamriel.txt
[00:40:53.746] Add 4 manual references for DynDOLOD
[00:40:53.754] no DynDOLOD for WhiterunDragonsreachWorldFire01 00033DA4. Add a rule
[00:40:53.765] no DynDOLOD for WhiterunDragonsreachWorldFire02 00033DA4. Add a rule
[00:40:53.773] Adding LOD objects data with 3160 entries
[00:40:54.272] Saved C:\Games\SkyrimUtils\TES5Edit\TES5LODGenOutput2\skse\plugins\StorageUtilData\DynDOLOD_Tamriel_Objects.json
[00:40:54.285] Adding 10 child worlds using Tamriel for LOD
[00:40:54.293] WindhelmPitWorldspace
[00:40:56.170] KatariahWorld
[00:40:58.750] WhiterunDragonsreachWorld
[DynDOLOD.esp] Adding master "Book Covers Skyrim.esp"
[00:40:59.209] SolitudeWorld
[00:41:02.769] WhiterunWorld
[00:41:05.060] RiftenWorld
[00:41:10.800] WindhelmWorld
[00:41:15.564] AN_DruidGroveWorld
[00:41:15.748] An_Lothlorien
[00:41:18.957] An_SancreselWorld
Exception in unit create line 1197: Invalid floating point operation
[Apply Script done] Processed Records: 0, Elapsed Time: 42:29
[00:00] Saving: DynDOLOD.esp.save.2016_03_08_14_45_11
[00:02] Done saving.
DynDOLOD version: 1.47 TES5Edit version should be the latest available:
TES5Edit 3.1.3 EXPERIMENTAL starting session 2016-03-08 13:44:44
Using Skyrim Data Path: C:\Games\SteamLibrary\steamapps\common\Skyrim\Data\LODGen.exe I believe came with TES5Edit, the file is dated 17 FEB 2016 5:15 and file size is 242 KB (248 320 bytes) I've tried the generation with both high and med settings as memory serves, with both 1024 and 512 textures for atlas. Any thoughts on where I should look for the problem? --- edit --- Went further back on thread and found same issue posted earlier... I'll try that. --- edit2 --- That fixed the issue. Also fixed the crash I was previously getting when trying to load that esp - not surprisingly. Seems like everything's working fine now.