DynDOLOD 3.00 Alpha 182

[Roastlawyer]

16 minutes ago, sheson said:

Terrain underside needs to be done in the second pass.

If you do Glow LOD Windows High, do them in second pass only. If they are not high do them in the first pass only.

Can you also upload seasons\blacklist_roastmodularwhiterun_wrcastlestairs01_snow.ini?

 

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

[sheson]

27 minutes ago, Roastlawyer said:

Roastlawyer's Modular Whiterun - WRCastleStairs01.7z 144.56 kB · 1 download Blacklist_RoastModularWhiterun_WRCastleStairs01_SNOW.ini 270 B · 1 download

Should be fixed in Alpha-81

[wWeo]

6 hours ago, sheson said:

This might be fixed next version. If not upload new log, debug log and bugreport.txt if it exists.

This should be fixed in the next version. If not upload new log, debug log and bugreport.txt if it exists.

Test with the next version. Should be fixed. If it still happens upload all new logs and bugreport.txt.

Fortunately fixed. Thanks so much for your help!

[Roastlawyer]

1 hour ago, sheson said:

Should be fixed in Alpha-81

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

[gamingsrc]

Well I didn't clean my Game master for three months and I didn't get any CTD.

However I was surprised that a part of Apocrypha cell disappeared after cleaning some masters. 

[sheson]

23 minutes ago, gamingsrc said:

Well I didn't clean my Game master for three months and I didn't get any CTD.

However I was surprised that a part of Apocrypha cell disappeared after cleaning some masters. 

This is the DynDOLOD 3 alpha thread for testing LOD generation etc.

DynDOLOD reports facts about records/plugins/load order, just like LOOT or the xEdit error check does.

Refer to https://tes5edit.github.io/docs/7-mod-cleaning-and-error-checking.html how to properly clean plugins.
To avoid user error, consider using Batch Plugin Cleaner for Mod Organizer or xEdit Cleaning Extension.

[nolbear]

8 hours ago, sheson said:

Check/Upload the LODGen_SSE_Test_log.txt file and check the event log.

Okay, my log file is attached. It seems to be pointing to the performance counters error even though I've tried the fix. I'm not sure what else I can do at this point, so any help would be appreciated.

LODGen_SSE_Test_log.txt

[sheson]

59 minutes ago, nolbear said:

Okay, my log file is attached. It seems to be pointing to the performance counters error even though I've tried the fix. I'm not sure what else I can do at this point, so any help would be appreciated.

LODGen_SSE_Test_log.txt 1.01 kB · 1 download

Replace LODGenx64.exe in Edit Scripts with this test version. It uses an alternative method. Let me know how it goes.

[nolbear]

23 minutes ago, sheson said:

Replace LODGenx64.exe in Edit Scripts with this test version. It uses an alternative method. Let me know how it goes.

That worked! I was able to get past the initial loading stage, which is where I was getting stuck before, to the point where the DynDOLOD Wizard popped up. I haven't tried to actually run the program yet, but I'll let you know if I run into any issues when I do.

Thanks so much! The support you give on here is absolutely legendary. You are a true gem of this community.

[Roastlawyer]

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:

Spoiler

 

[Window Title]
TexGen

[Main Instruction]
Error: ErrorSelectingRenderContent The handle is invalid.

[Exit TexGen]

[Footer]
Online Manual | Support Forum | Copy message to clipboard

 

 

 

TexGen_SSE_Debug_log.txt TexGen_SSE_log.txt

Edited March 12, 2022 by Roastlawyer

[sheson]

18 minutes ago, Roastlawyer said:

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:

  Hide contents

 

[Window Title]
TexGen

[Main Instruction]
Error: ErrorSelectingRenderContent The handle is invalid.

[Exit TexGen]

[Footer]
Online Manual | Support Forum | Copy message to clipboard

 

TexGen_SSE_Debug_log.txt 2.81 MB · 0 downloads TexGen_SSE_log.txt 106.62 kB · 0 downloads

That error should be unrelated to updating the Redis.

Any changes to the graphics card/driver/OS? What is the graphics card? How much VRAM?
Track its usage. It seems that TexGen has less and less of it available until the "render context" (think of it like a hidden window) somehow becomes invalid.

Kill any hidden TexGenx64/Texconv lingering in task manager. Try not to run other programs that use (lots) VRAM.

Only select one TexGen option at a time, e.g it seems billboards went fine, and its at the start of rendered object LOD were things went wrong. 

[Roastlawyer]

16 minutes ago, sheson said:

That error should be unrelated to updating the Redis.

Any changes to the graphics card/driver/OS? What is the graphics card? How much VRAM?
Track its usage. It seems that TexGen has less and less of it available until the "render context" (think of it like a hidden window) somehow becomes invalid.

Kill any hidden TexGenx64/Texconv lingering in task manager. Try not to run other programs that use (lots) VRAM.

Only select one TexGen option at a time, e.g it seems billboards went fine, and its at the start of rendered object LOD were things went wrong. 

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).

Edited March 12, 2022 by Roastlawyer

[sheson]

16 minutes ago, Roastlawyer said:

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).

I can see form the debug that it is reducing the setting automatically down to 6 and still fails. You had success with setting to 10 from the start. Try that again.

[Roastlawyer]

19 minutes ago, sheson said:

Only select one TexGen option at a time, e.g it seems billboards went fine, and its at the start of rendered object LOD were things went wrong. 

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.

[Roastlawyer]

32 minutes ago, sheson said:

You had success with setting to 10 from the start. Try that again.

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.

Edited March 12, 2022 by Roastlawyer