DynDOLOD 3.00 Alpha 190

[sheson]

  On 5/1/2023 at 3:57 AM, z929669 said:

OpenGL error finally with 126. I have the debug options active in my INI. Bugreoprt and logs.

I'm rerunning again now and will let you know if repeatable.

---

Second attempt succeeded without issue.

Expand  

23.2.2.230217 does not seem to be latest WHQL recommended driver?

Did the problem happen without setting GLListDebug and GLDebug?

Test with RenderSingle=1 added under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini

[heheloveer]

  On 4/30/2023 at 6:24 PM, sheson said:

Windmill fans are dynamic LOD objects that replace the original references so that the same reference is used for LOD and also shows in active cells. LOD from the parent also shows in childworlds that use the parent world for LOD. For windmill fans that also means active childworld cells just the same as it does for the parent world.

If the large reference copying for the large reference workarounds happens to also automatically creates copies for the windmill and other buildings that patch manually adds, then don't bother with the patch to avoid conflicts.

In case the patch is still needed for something, do not edit the generated plugins. Instead edit the patch in the ..\Data\DynDOLOD folder by removing unwanted lines. Copy the patch file to a new mod so it overwrites the patch file in DynDOLOD Resources, then you never have to bother about it again.

To find which line to remove look at the editor ID of a reference added by the patch, for example:

whiterunexterior_tamrielpatch_00000D_DynDOLOD_PATCH_DynDOLOD_NOLOD

Take note of the highlighted hex line counter: 00000D = line #13. The first non commented // line is #0. e.g. overwrite=skyrim.esm;0001a279,XCLW=-4700.000000

So the 13th line to remove from WhiterunExterior_Tamriel.patch would be:
overwrite=skyrim.esm;000e8ecb,REFR=new,EDID=NOLOD,NAME=skyrim.esm;00022468,DATA\Position\X=34320.523437,DATA\Position\Y=-14425.012695,DATA\Position\Z=-4481.890137,DATA\Rotation\X=359.9769,DATA\Rotation\Y=359.4513,DATA\Rotation\Z=183.5520

You can use the base record (NAME=skyrim.esm;00022468) and position to doublecheck you got the right line.

Expand  

Thanks for the tip. I thought of editing the patch file but for some reason I decided against it. Maybe I was just weirdly more comfortable editing plugins in xEdit.

Tested with version 126 and with the Exterior Patch on. Misplaced duplicate waterfalls are gone and the vanilla waterfalls added by the exterior patch are covering up Natural Waterfalls waterfalls, which is pretty much expected. I also looked around to see if the exterior patch was still useful. For now the answer seems largely negative. Most buildings outside the city, like the windmills, have two exact copies in the same place, added by Large Reference Bugs Workarounds and the exterior patch respectively. They don't result in visual glitches since they're exactly the same, but this does make the exterior patch rather meaningless. I did find two buildings and one or two smaller objects only added by the exterior patch, but they are all in places where I don't think you could really see them without tfc or tcl. With me using mods that replaces the vanilla bridges and waterfalls, the Whiterun Exterior Patch seems too much trouble for it's worth at this point. I'll look around solitude next. The Solitude Exterior Patch adjusts placements of occlusion planes, so maybe it's still worth keeping?

Edit: checked Solitude and it seems there's some noticeable objects only placed by the exterior patch, so I think I'll keep it. Also it turns out the glowy objects added by the patch like windows and giant campfires can be pretty noticeable at night. Hmm, maybe I'll reconsider.

Edited May 1, 2023 by heheloveer

[shaman]

Error: Texconv error 80070070 textures\architecture\whiterun\WRCityWall01.dds "D:\Main Download\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -gpu 0 -y -aw 256 -f R8G8B8A8_UNORM -o "C:\Users\REDACTED AppData\Local\Temp\TexGen_SSE" "C:\Users\REDACTED \AppData\Local\Temp\TexGen_SSE\23361F52950E495CB3F2983E7CF9906C.dds"
[01:24] )

Please explain what I can do about this no video or forum has helped me. location changes all over the place from whiterun to riften to solitude.

Note 2. I am not using a C drive I am using my D drive. Nothing in my C drive exists on what it is saying as only windows is installed there.

[dnmt]

Brand new install of DynDOLOD, continually running into an error where DynDOLOD simply closes during generation with no pop-up error or anything. Not a clue what could be causing it as it happened once after a few minutes and then again after about 30 minutes after clearing the folder and trying again. Newest Alpha with new resources - had no problems running DynDOLOD Alpha-125 and only ran into this issue when trying Alpha-126 tonight. Logs are attached. Any advice is appreciated. Thank you.

DynDOLOD_SSE_Debug_log.txtFetching info... DynDOLOD_SSE_log.txtFetching info...

Edited May 2, 2023 by dnmt

[sheson]

  On 5/1/2023 at 10:25 PM, shaman said:

Error: Texconv error 80070070 textures\architecture\whiterun\WRCityWall01.dds "D:\Main Download\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -gpu 0 -y -aw 256 -f R8G8B8A8_UNORM -o "C:\Users\REDACTED AppData\Local\Temp\TexGen_SSE" "C:\Users\REDACTED \AppData\Local\Temp\TexGen_SSE\23361F52950E495CB3F2983E7CF9906C.dds"
[01:24] )

Please explain what I can do about this no video or forum has helped me. location changes all over the place from whiterun to riften to solitude.

Note 2. I am not using a C drive I am using my D drive. Nothing in my C drive exists on what it is saying as only windows is installed there.

Expand  

Moved to the DynDOLOD 3 Alph athread. Read the first post which log, debug and bugreport.txt if it exists to upload. https://dyndolod.info/Official-DynDOLOD-Support-Forum

From https://dyndolod.info/Help/Texconv
80070070 There is not enough space left on the disk to which Texconv is trying to writing to.

[sheson]

  On 5/2/2023 at 2:23 AM, dnmt said:

Brand new install of DynDOLOD, continually running into an error where DynDOLOD simply closes during generation with no pop-up error or anything. Not a clue what could be causing it as it happened once after a few minutes and then again after about 30 minutes after clearing the folder and trying again. Newest Alpha with new resources - had no problems running DynDOLOD Alpha-125 and only ran into this issue when trying Alpha-126 tonight. Logs are attached. Any advice is appreciated. Thank you.

DynDOLOD_SSE_Debug_log.txt 457.73 kB · 3 downloads DynDOLOD_SSE_log.txt 69.55 kB · 3 downloads

Expand  

The logs you uploaded seem to show what happens when you start the tool, click High on the advanced settings and then Click Cancel.

Clean out the log folder. Enable the realtime log https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
Select at least a worldspace, select at least one option to generate, like object, tree and dynamic LOD.
Upload logs including the real time log and bugreport.txt if it exists. Also check the Windows Event log.

[dnmt]

  On 5/2/2023 at 6:07 AM, sheson said:

The logs you uploaded seem to show what happens when you start the tool, click High on the advanced settings and then Click Cancel.

Clean out the log folder. Enable the realtime log https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
Select at least a worldspace, select at least one option to generate, like object, tree and dynamic LOD.
Upload logs including the real time log and bugreport.txt if it exists. Also check the Windows Event log.

Expand  

Thanks. I was actually able to get it to work simply by unchecking the "Upgrade NearGrid large references to FarGrid" option, which seems like a nice-to-have but not required add-on. Curious, but I at least got everything to run. Thank you.

[sheson]

  On 5/2/2023 at 1:15 PM, dnmt said:

Thanks. I was actually able to get it to work simply by unchecking the "Upgrade NearGrid large references to FarGrid" option, which seems like a nice-to-have but not required add-on. Curious, but I at least got everything to run. Thank you.

Expand  

It is very unlikely that checking this options causes the OS to terminate the tool as described. Nothing about that option changed in the past several alpha versions.

[FinalCraneFall]

Texgen does not need DynDOLOD Resource right?

[sheson]

  On 5/2/2023 at 4:42 PM, FinalCraneFall said:

Texgen does not need DynDOLOD Resource right?

Expand  

https://dyndolod.info/Help/DynDOLOD-Resources

DynDOLOD requires the Core Files of DynDOLOD Resources..

They are not called TexGen Resources.

[strangeWindmill]

Hello,

I've been running into an issue when I attempt to update an existing Dyndolod plugin.  What I've been able to do in the past is incrementally build up my full DynDOLOD by first processing the base game worldspaces, followed by the DLC world spaces, and then any mod related world spaces.  When I try to do that with 126-alpha, however, DynDOLOD.esm is updated to have errors.  Every worldspace I had previously included has unresolveable form ids in the large references, preventing me from updating the plugins any further.  I have yet to try generating for all world spaces out of memory concerns, but does anyone have an idea as to why my updates are failing in this way?

Pastee link containing latest DynDOLOD logs and SSEEdit errors: https://paste.ee/p/1OtsL

[sheson]

  On 5/4/2023 at 2:55 AM, strangeWindmill said:

Hello,

I've been running into an issue when I attempt to update an existing Dyndolod plugin.  What I've been able to do in the past is incrementally build up my full DynDOLOD by first processing the base game worldspaces, followed by the DLC world spaces, and then any mod related world spaces.  When I try to do that with 126-alpha, however, DynDOLOD.esm is updated to have errors.  Every worldspace I had previously included has unresolveable form ids in the large references, preventing me from updating the plugins any further.  I have yet to try generating for all world spaces out of memory concerns, but does anyone have an idea as to why my updates are failing in this way?

Pastee link containing latest DynDOLOD logs and SSEEdit errors: https://paste.ee/p/1OtsL

Expand  

Moved to the DynDOLOD 3 Alpha thread. Read the first post which debug log to also upload. https://dyndolod.info/Official-DynDOLOD-Support-Forum

The log you uploaded only contains one session.
It is unclear if when the unresolved errors happen.

If updating does not work, then start from scratch as the message says. See https://dyndolod.info/FAQ "High memory usage / Out of memory"

[ManBearPig1989]

Hi, recently got back into modding skyrim and redownloaded dyndolod and all its requirements from scratch. Unfortunately when I try to run TexGen in crashes while generating textures without any popups or logs. Looking at eventviewer shows an error before the program crashes that points to nvoglv64.dll. This is apparently an nvidia driver thing yet even after installing a new driver the issue remains, I should note I have had no driver-related issues with any prior installation of dyndolod. Ill try using display driver uninstaller and see if that helps with the issue... but if anyone else has any idea as to why this is happening feedback would be hugely appreciated! TexGen_SSE_realtime_log.7z

Event Viewer Log:

EventViewerLog.txtFetching info...

 

[sheson]

  On 5/5/2023 at 7:34 AM, ManBearPig1989 said:

Hi, recently got back into modding skyrim and redownloaded dyndolod and all its requirements from scratch. Unfortunately when I try to run TexGen in crashes while generating textures without any popups or logs. Looking at eventviewer shows an error before the program crashes that points to nvoglv64.dll. This is apparently an nvidia driver thing yet even after installing a new driver the issue remains, I should note I have had no driver-related issues with any prior installation of dyndolod. Ill try using display driver uninstaller and see if that helps with the issue... but if anyone else has any idea as to why this is happening feedback would be hugely appreciated! TexGen_SSE_realtime_log.7z

Event Viewer Log:

EventViewerLog.txt 1.68 kB · 1 download

Expand  

Add RenderTexturesSingleThread=1 under TexGen in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and test if it runs through.

[ManBearPig1989]

  On 5/5/2023 at 7:52 AM, sheson said:

Add RenderTexturesSingleThread=1 under TexGen in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and test if it runs through.

Expand  

Ok that worked! Is this indicative of something faulty on my end?