DarthVitrial

With that dyndolod version it just gives me an error that the Resources don't match.. DynDOLOD_SSE_Debug_log.txt DynDOLOD_SSE_log.txt

Yeah, positive.

Yeah, you're right, it failed again.. Logs: https://mega.nz/file/9s12SS7T#f56By4jxr03kS6zBj9RhHmS2qg1vyEIUU-q_HAWCCl0 .net crash (two of them this time, one for each of the failed seasons): DynDOLOD_WIN.ini

Running it again now, but I suspect that the prior dyndolod link you sent me actually fixed it and I just needed to clear out the dyndolod cache (which I'd forgotten to do) because something invalid got cached. I'll let you know how it works when it finishes running.

Update, seasons LOD generation reliably works just fine as long as I have SeasonsCombineAtlas=0 in the ini. If I set it to 1, those threading errors happen. Do you want the logs from the successful run?

With seasons fully disabled this works no issues whatsoever. Gonna try with atlas combining off next. I don't use that patch, so that's not it. You can't reinstall .net 4, it's built into windows 10/11 and cannot be changed. I did try running the .net framework repair tool though.

Which DBM patch? I'm wondering if I have that one, might be related to my crash...

No luck with that version either, nor with changing back to the lodgen from 88. Once again here's the latest argument out of range error from the .net framework: DynDOLOD_WIN.ini DynDOLOD_SSE_log.txt DynDOLOD_SSE_Object_LOD.txt DynDOLOD_SSE_Object_Report.7z LODGen_SSE_Tamriel_WIN_log.txt LODGen_SSE_Tamriel_log.txt

OK, I reinstalled everything from scratch, and...well, I'm at least getting a DIFFERENT crash? Now it's an Access Violation. Seems like a race condition? I'll try again, but hopefully the attached logs and bugreport.txt help. EDIT: OK, second time it was back to the usual mystery failure with no logs. Might be related to that race condition though? Anyway here are my exports and logs for that: https://mega.nz/file/otcXGQya#r-KhiASkNjngx0N_2lczQHMeOFyeXhdIof1a9pdstDs https://mega.nz/file/QpsnmSoD#8veEz79OeB0P8UnlYbAe5z_cILKy-8kLH22TocP0lkU And here's the event log for the .net error. The error mentions Threading again so I suspect the race condition is indeed related: Logs.7z bugreport.txt

oh, should I have cleared the Export folder each run? I did clear it when I first updated to 88 since that was a clean install but I haven't since then. https://mega.nz/file/J89mDBTD#DyDMEVf2bQeMtaJ4kQKYv7Ld_fb2cT-VckYom-hpKok EDIT: Could it possible be because I updated from .Net 6.0.3 to 6.0.4? That's the only thing on my system that's changed.

No dice, still nothing in the logs. (https://mega.nz/file/YksHVRwI#BT7qDlhN52VsanvQT1T11pwvRU8eWmYNK0Nmk1CeE9E) Event log:

Yes, I did. i was using 87.

hm Ran with that version, logs still seem kinda empty though, and still no minidump... (Heres the logs: https://mega.nz/file/wssl0LIb#z42pFcJZ1Eixv-ztQr1lXsJ3RZo5YwUQdGt0d3TaCsg BUT, the event log seems useful. I've attached those. event.evtx event2.evtx

Yes, I copied them both there. The Minidump folder is completely empty. Event log: Faulting application name: LODGenx64.exe, version: 3.0.0.0, time stamp: 0x625923b7 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00007ffb9ccfbfaa Faulting process id: 0x0x1884 Faulting application start time: 0x0x1D850E8B5B57F65 Faulting application path: D:\Dyndolod\Edit Scripts\LODGenx64.exe Faulting module path: unknown Report Id: 5c53a2bb-dae0-4083-a99f-113ca29d23ef Faulting package full name: Faulting package-relative application ID: What other diagnostics can I do?

Ok, ran it again with that lodgen you linked. Here's all the logs. it failed in a few places this time (Dimfrost, Tamriel AUT) I dont see anything in those specific logs so probably the debug log has the info https://mega.nz/file/NtsjTaLb#LALCmAXgXHjrxK695FJSDlj2JRaSDrxbjJaOiP9Nvsg

OK, running that now. As a note, the thing is it seems totally random where it fails on and why, the only common thread seems to be having the seasons option enabled?

After updating to alpha 88 I'm getting an error when generating Winter LOD for the Tundra Homestead CC (tamriel worldspace): Error processing meshes\creationclub\eejsse001\architecture\eej_towerroof.nif Object reference not set to an instance of an object. Other than reinstalling dyndolod resources, I haven't made any changes between this run and the prior (successful) run,only change was going to alpha 88. Logs are too big to upload here so here's a mega link (there might be remnants from a prior run in the start of the logs though - I think I cleared out the older stuff but I might have missed one): https://mega.nz/file/ss1SDLQS#SpluHqI8fKtTDdZTUwWEhg7fHmhAR0Ub9NX4NMFumwc (Edit - it seems to be random where that "object reference not set" error happens, rerunning it it happened on Autumn one time and Winter twice, and on different nifs/different worldspaces each time. The common thread seems to be that it's always on a season other than default.) EDIT 2: definitely seasons specific, turning off season LOD it works just fine. EDIT 3: Seems specifically caused by the SeasonsCombineAtlas ini setting, when I change that to 0 the seasons lod works too.

Ah, I see what you mean. I'm not sure what else could have caused that access violation since I didnt have anything else open at the time, and those were all the logs I had. If I think of anything I'll post here.

Hm. Definitely nothing else opening that file as far as I know. no xedit, skyrim wasn;'t running...

Doesn't seem to be reliably repeatable, I've had it happen a few times but I haven't noticed any common trend in when it does or doesn't happen. I'll keep testing. EDIT: Huh, i just noticed that after Dyndolod finished running entirely and closed after zipping the output, Taking Your Firstborn.exe remained running until I forced it to exit via task manager. Maybe that's the issue? Dyndolod hadn't fully exited when I re-ran it?

Hm, this is an odd one, while rebuilding I got an "Access violation at address 000000000002A1A8 in module 'DynDOLODx64.exe'. Read of address 0000000000000000 while processing Skyrim.esm [REFR:000AA0E4] (places MountainCliff03 [STAT:00027D1F] in GRUP Cell Temporary Children of [CELL:00009736] (in Tamriel "Skyrim" [WRLD:0000003C] at 31,-13))" error I've zipped up all the logs including the normal dyndolod log and the debug log. Still a bit too big for here so I uploaded to mega. https://mega.nz/file/kxcwzJTZ#A5fIu2rizJeFCZ38ZZ-sSaazhbzRNoSBcr9GAyva7yg I'm on alpha 87. EDIT: forgot the bugreport.txt, attached. bugreport.txt

Thanks, I found the cause: [06:24] [BuildReferences] <Debug: Swapped [REFR:1D00AFB5] (places HagravenHouse01 [STAT:000ACB04] in GRUP Cell Temporary Children of GHCradelVillage00 [CELL:1D00AC32] (in zGHCradleWoodsWorld "Cradle Woods" [WRLD:1D00AA1A] at -2,2)) to Dynamic Things Alternative.esp dtaHagravenHouse01 "Tent" [FLOR:FE06F85D]> I'll remove Dynamic Things Alternative and rebuild DyndoLod.

Yeah, what confused me is the base record is a STAT though. I attached my log, I cannot upload my debug log because it's 50mb which is too large for my 400kbps internet to upload. DynDOLOD_SSE_log.txt DynDOLOD_SSE_Object_LOD.txt DynDOLOD_Summary_LargeReferenceBugs.html

I'm having a bit of a hard time interpreting this message: Warning: Base record type not STAT or MSTT for large reference Skyrim.esm [REFR:0002B0C0] (places HagravenHouse01 [STAT:000ACB04] in GRUP Cell Temporary Children of SerpentsBluffRedoubtExterior02 [CELL:000099FC] (in Tamriel "Skyrim" [WRLD:0000003C] at -24,-2)) The message itself says that HagravenHouse01 is a STAT, but then it also says it's not a STAT? I'm not sure how to interpret that. Sorry if this has been asked before, I checked the forum but didn't see any similar mentions.

Hi, in Alpha 36, I'm having TexGen SSE instantly crash when generating stitched textures with a List Index Out of Bounds error. Bugreport and logs attached. Is there any other info I can provide? bugreport.txt TexGen_SSE_Debug_log.txt TexGen_SSE_log.txt