Roastlawyer

Right sorry. I'm not sure what I had done the first time but I reran dyndolod and now it all looks as expected. Sorry for the poorly done false alarm.

Sorry to be a pain again but after generating dyndolod my tree lods still look like normal billboard trees. I'm using vanilla trees which should have 3d lods from dyndolod resources right? I made sure to selecte ultra trees. Edit: somehow I was looking at the output logs from alpha 128, before. The actual logs from this run say that the 3d lod models aren't found though dyndolod resources has a bunch of passthrough_Lod.nifs for them DynDOLOD_SSE_Tree_Report.txt

That test version ran successfully on the vanilla load order. I'll give it a try on my full one. EDIT: Ran successfully on the full load order as well.

Because it was being problematic I've went back to a vanilla load order with just skse and a few .dll mods like engine fixes and papyrus utils, the only mod I have that has any meshes or textures at all is dyndolod resources. Everything is otherwise just the 1.5.97 BSA's bugreport.txt TexGen_SSE_Debug_log.txt TexGen_SSE_log.txt

Made a copy of dyndolod/texgen with that latest test exe at E:\Mods\DYNDOLOD\ and that one still gets a stack overflow TexGen [Main Instruction] Error: Stack overflow while processing E:\Mods\DYNDOLOD\TexGen_Output\textures\terrain\lodgen\skyrim.esm\reachgrassobj01_00053491. bugreport.txt TexGen_SSE_Debug_log.txt TexGen_SSE_log.txt

Still getting a stack overflow, on different files each time First run: [Main Instruction] Error: Stack overflow while processing E:\Mods\[Bethesda Stuff]\Patchers and Similar Tools (Xedit, Wrye Bash,Loot etc)\DynDOLOD & TexGen\DynDOLOD 3.00 Alpha 173\TexGen_Output\textures\terrain\lodgen\skyrim.esm\tundragrassobj03_0002acd3. Second Run: [Main Instruction] Error: Stack overflow while processing E:\Mods\[Bethesda Stuff]\Patchers and Similar Tools (Xedit, Wrye Bash,Loot etc)\DynDOLOD & TexGen\DynDOLOD 3.00 Alpha 173\TexGen_Output\textures\terrain\lodgen\skyrim.esm\reachgrassobj01_00053491. run 1 logs.zip run 2 logs.zip

Replacing the alpha 173 texgen64.exe with the one you linked is giving me a stack overflow: TexGen [Main Instruction] Error: Stack overflow while processing E:\Mods\[Bethesda Stuff]\Patchers and Similar Tools (Xedit, Wrye Bash,Loot etc)\DynDOLOD & TexGen\DynDOLOD 3.00 Alpha 173\TexGen_Output\textures\terrain\lodgen\skyrim.esm\fieldgrass01_000135be. [Content] Click on this link for additional explanations and help for this message For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum. [OK] [Exit TexGen] bugreport.txt TexGen_SSE_log.txt TexGen_SSE_Debug_log.txt

Hello, I'm suddenly getting an access violation error when running Texgen, I managed to run texgen & dyndolod successfully once right after I updated everything, but every time since it has failed. Now it happens every time I try to run it including on a basically vanilla modlist with just a couple of things like engine fixes, sse fixes, .net framework etc. No matter what modlist I run it on, it always has the violation at the same address and the "read of address" is always the same, though the file it was processing varies based on which modlist I use, though if I rerun on the same list it consistently fails at the same file. As far as I can tell I'm using the latest versions of Dyndolod (Dyndolod/Texgen alpha 173, Dyndolod Resources Alpha 50, Dyndolod DLL NG and Scripts alpha 32). Access violation at address 0000000000DB6166 in module 'TexGenx64.exe'. Read of address 0000000000000084 while processing E:\Mods\[Bethesda Stuff]\Patchers and Similar Tools (Xedit, Wrye Bash,Loot etc)\DynDOLOD & TexGen\DynDOLOD 3.00 Alpha 173\TexGen_Output\textures\terrain\lodgen\skyrim.esm\snowgrass01_0001cc70 bugreport.txt TexGen_SSE_log.txt TexGen_SSE_Debug_log.txt

Ensured my CPU overclock was disabled (was already running stock) and that MSI afterburner didn't currently have an GPU overclock set (It didn't) updated Nvidia driver from 528.24 to 336.40 (latest one for 3080) updated AMD APU Graphics driver from 22.20.27.09 (November 2022) to 22.49.57.05 (June 1 2023) (latest one for Ryzen 5600g) Ran DynDOLOD (twice because I forgot to watch Vram usage the first time) Both times it got stuck at "[Tamriel] Creating texture atlas E:\Mods\[Bethesda Stuff]\Patchers and Similar Tools (Xedit, Wrye Bash,Loot etc)\DynDOLOD & TexGen\DynDOLOD 3.00 Alpha 128\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Tamriel_Glow.dds" Vram usage never went above 1.6GB out of 10GB Ram maxed out at 9.6GB used out of 31.8GB Ran a 3rd time but with [DynDOLOD] TextureCache=10 RenderSingle=1 Instead of just RenderSingle=1 set in DynDOLOD_SSE.ini That time it got further, getting to "[06:18] [DLC2SolstheimWorld] Creating texture atlas E:\Mods\[Bethesda Stuff]\Patchers and Similar Tools (Xedit, Wrye Bash,Loot etc)\DynDOLOD & TexGen\DynDOLOD 3.00 Alpha 128\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_DLC2SolstheimWorld_Glow.dds 512 x 256" before CPU usage dropped to 0% and Vram usage dropped back to idle levels (0.5GB used) No real change in amount of Vram or ram used Ran a 4th time: [DynDOLOD] TextureCache=10 RenderSingle=1 AtlasThreads=1 Whoohoo! finally got a complete run. So that's quite nice. Vram usage was pretty much the same. Ram topped out ~13GB when it peaked, most of the time usage was still around 10GB. Edit: Spelling/formatting

Yesterday when it was freezing like that, pressing the X in the top right would cause the program to hang, then windows would say dyndolod stopped responding. I click end anyways, the main window would close and then a dyndolod process that could not be killed would hang around in task manager untill the PC was forcably restarted. When that happened the normal log files where not generated which is why you had my enable the realtime one before. Anyways I'll give the RenderSingle=1 line a try. Alright tried again with the RenderSingle=1 line just below [DynDOLOD] in the _SSE.ini. It hung at [Tamriel] Creating texture atlas. In task manager I couldn't find any TexConv processes. After 25 minutes of DynDOLOD being at 0% cpu usage and no further additionsto the realtime log since it stalled I tried to stop generation. Pressing the X gave me the message about how generation would be incomplete, I accepted and now the dyndolod window is greyed out and the both the window and task manager say it's not responding. Pressing end task in task manager does nothing. Because of this I have no DynDOLOD_SSE__debug_log.txt, bugreport.txt, or DynDOLOD_SSE_log.txt. Here is the realtime log https://drive.google.com/file/d/1fRTAGWFz2OUqAkvpQROdrmSYT77DmVBJ/view?usp=drive_link

Well, not exactly the same as before when it was freezing at generating at Tamriel, but I'm getting an issue with similar effect where generation completely freezes and CPU usage drops to zero. So far it's been frozen for 15 minutes or so without doing anything. The realtime log you had me enable last time I had an issue also stopped being updated when It froze. https://drive.google.com/file/d/1tUjYNaETcLsX4LjJH9aFQNFAB1ZDbOok/view?usp=drive_link Link to log Later edit: It happened on my next try as well, here is the log from that second time https://drive.google.com/file/d/1aotQ77s_BhUu2Do8e-WAOY-mPSh7laXn/view?usp=drive_link

When I tried it again just now it worked, but if it happens again I'll be back with the log

Hello, I'm getting an issue where about every second run (or even more) DYNDOLOD seems to freeze at "[Tamriel] Generating object LOD". CPU usage for dyndolod goes to 0% (sometimes flickers to 0.1%) and the LODgen window doesn't come up (even after it sitting at that message for 15 or so minutes. Actually sometimes LODGen would come up but after it was done the rest of dyndolod would still freeze up just the same, however the last couple runs I couldn't even get that and the DynDOLOD_Output folder has only 4 smim lod textures generated. the only ini edits I've made to \Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini was to change it to boot to advanced mode & my grass LOD brightness settings. I'm using DYNDOLOD 3.00 Alpha 128 [DynDOLOD Resources SE v3.00 Alpha 37], [DynDOLOD DLL NG and Scripts 3.00 Alpha 6 for dyndolod 123+], [PapyrusUtil SE v3.9 for SSE 1.5.97], and I'm also using NGIO v8 with a generated grass Precache When I try and close DYNDOLOD it gives me the expected warning about generated output being incomplete, I click yes, then the window freezes up and DYNDOLOD.exe stops responding. Task manager can't kill it, and If I try to end it from the TM details panel I get "this operation could not be completed. Access is denied" and I have to hard reboot my PC. for log files there aren't many generated: No bugreport.txt, No Dyndolod_SSE_log.txt, No Dyndolod_SSE_Debug_log.txt, and no LODGen_SSE_Tamriel_log.txt EDIT: I ran it again with Verbose=1 in _SSE.ini and it worked, so I'll see if its consistent and if the problem immediately returns if I set it back to 0 EDIT 2: nope while the first 3 runs with verbose did work, this time cpu usage went down to 0%, elapsed time stopped counting, when I tried to save the in window log it froze and went unresponsive and I couldn't close it again. DynDOLOD_SSE.ini

With that (TextureCache=10) set in the .ini again it worked. Once again, thank you so much for all your help and what you do.

I ran texgen again with only "Rendered object LOD Textures" selected. It completed successfully. (edge was closed) Ran it again with stitched object textures. Vram usage (with edge also open in just this tab) hit a max of 4.5gb (2gb dedicated, 2.5gb shared used), This also completed successfully.

No OS updates, driver updates or hardware changes since this morning when it worked fine (after all the seasons troubleshooting and not found errors and whatnot). GPU is a gtx 960 2GB, yesterday there was that other vram issue where you had me add a line to the texgen ini before you updated it. That whole dyndolod install had since been removed and reinstalled. It was now a clean unmodified texgen ini from alpha 81. (I hadn't seen that there was an 82 until just now).

Hello, sorry to be bothering you again. After having dyndolod work this morning and seeing what one of my lods like I continued to mess around with my modlist. During this I updated a few mods and also installed the latest version of the visual C++ Redistributable (Latest supported Visual C++ Redistributable downloads | Microsoft Docs). Having done that I restarted my computer and went to run Texgen yet again. It runs for a bit then I get "Error: ErrorSelectingRenderContent The handle is invalid." I copied the error to the clipboard and pressed "exit texgen". It never closes on its own. I waited 6 minutes for it to close before pressing "X" in the corner of the main texgen window. The main window finally closed and a texgen log was made but the process never ended. Eventually I had to kill it in task manager. Clipboard: TexGen_SSE_Debug_log.txt TexGen_SSE_log.txt

Thank you so much, everything seems to be working great now.

Roastlawyer's Modular Whiterun - WRCastleStairs01.7z Blacklist_RoastModularWhiterun_WRCastleStairs01_SNOW.ini

Alright, I ran Alpha 80 for my minimal test modlist that was getting access violation errors before and that's fixed now, so that worked. Everything completed successfully on that minimal list. After that worked I went back to run TexGen and DynDOLOD on my full modlist and got "Error: Range check error." in DynDOLOD. Copied to clipboard: bugreport.txt DynDOLOD_SSE_Debug_log.txt DynDOLOD_SSE_log.txt

I'm still getting access violation issues, but using that test version I got a bugreport.txt Debug Log: https://drive.google.com/drive/folders/1jTDOvaYZLJpcSiQje3GURhqyvCdqd2cM?usp=sharing bugreport.txt DynDOLOD_SSE_log.txt

Cool, I'll give it a go when I get home later.

I ran both texgen and Dyndolod from Alpha-79. Texgen is now working out of the box. Dyndolod gave an item not found error the very first run (A different one this time, the error window that popped up said it was "Error: Item not found while processing textures\lod\mrkcliff01lod.dds". I backed up the logs and am uploading them to google drive but dyndolod never made a bugreport.txt file, because of that I reran Dyndolod and got an access violation this time. Still no bugreport.txt I manually made a bugreport.txt file in the same directory as the .exe and reran it again for a third run. The bugreport.txt stayed blank. I got the same "Error: Access violation at address 0000000001249385 in module 'DynDOLODx64.exe'. Read of address 0000000000000000." as in the second run again. I'm uploading the log and debug log from all three runs to a google drive folder, it will take probably 30 mins all the debug logs to finish uploading but I'll leave the link to the google drive folder here because I've got to run until 4:00 (just about 1:00 now). Google drive link https://drive.google.com/drive/folders/1AaXMm2JNLhcyfrxdw3-aDJ88kjFon8B0?usp=sharing Second run access violation error copied to clipboard:

Sorry about that, it's from a rerun I did a few moments ago but with the same modlist and giving the same error as in the other logs. Edit: Glancing at the bugreport log, I see I did not clear it and it also includes a number of old runs. My bad bugreport.txt

Debug Log: https://drive.google.com/file/d/1ah99WkM7cy-smuEIAXGOuKC0IYiNGr0o/view?usp=sharing