Hi I'm experiencing a very wierd behaviour with DynDOLOD 2.59 (have not tested other versions), don't really know if it is a bug or an expected behaviour. It will always stop responding and not progress during the atlas creation (waited around an hour a nothing happenned, the screenshot is for this error) if I allow it to use more than 1 physical core. Sometimes it works with 3-4, but is umpredictable at best, with just 1 physical set via affinity, it always works, but takes very, very long time. I'm using the x64 version, as with the x32 I always get a memory access violation, the attached log is for x32 as the x64 does no hard crash, it just stops responding if I use more than 1 physical core, so for the x64 i've attached a screenshot of the process stuck (0% and no change in memory allocation for more than an hour) As the log will show, my desktop (or workstation to be more precise) has an odd configuration, with 2 physical procs, but what is strange to me, is that even if I restrict it to a single physical processor, but using all cores (or more than 1) it causes the same error. If I try the Lodgen on EditScripts, I the below text. ============================================================ Skyrim Object LOD Generator 2.5.7.0 Created by Ehamloptiran and Zilav Updated by Sheson Log started at 11:41:54 Nothing to do Log ended at 11:41:55 (0:0) Code: 1 bugreport.txt
