MaverickMartyn

Just finished running it again, with the same result. Same memory address and offset as before. Here are all the logs. https://ufile.io/alah81mb Slightly off-topic: How the fudge do you attach a file to a post here? I see others have done so, but I can't see any option for it.

For what it's worth, I've had issues generating LODs too, although that was using xLODGen. Also Access Violation errors. Stress testing using OCCT revealed instabilities in my system, and after resetting my BIOS to factory defaults I was able to generate terrain LODs. I've now just encountered yet another Access Violation error, this time with DynDOLOD. I doubt it's a stability issue this time, since the OCCT test passed after the BIOS reset. It's late, so I won't be investigating any further tonight, but I'll return with any updates. Bugreport: https://pastebin.com/NZgaTETW Relevant bits of the pop-up dialogue: [Main Instruction] Access violation at address 0000000001ED0CAD in module 'DynDOLODx64.exe' (offset EF0CAD). [Content] Read of address 0000000000000000.