DynDOLOD 3.00 Alpha 180

[sheson]

On 5/29/2022 at 2:12 AM, mrudat said:

I was having an error when attempting to use a Smelter (the constructible one at Goldenhills Plantation, though it looks like the outdoor HF smelters should have similar behaviour, though I haven't tested those), "Someone else is using this"; I finally got around to investigating why this particular smelter wasn't working.

In DynDOLOD.esm, built with alpha 92, a reference to `CraftingSmelterMarker1 "Smelter" [FURN:0009C6CE]` is replaced with 'CraftingSmelterMarker01_DynDOLOG_NOFLAG "Smelter" [FURN:190017E4]'.

CraftingSmelterMarker1 has three things that CraftingSmelterMarker1_DynDOLOG_NOFLAG does not:

• the 'Has Distant LOD' flag
• MNAM - Active Markers is present with the values Sit 0 and Unknown 31
• WBDT - Workbench Data/Uses Skill has the value Smithing while the DynDOLOD_NOFLAG has the value None

Reverting the edit to the reference, so that it points to CraftingSmelterMarker1 again, allows use of the smelter once more; it also allows NPCs to use the idle marker at the smelter. I expect that this has other effects that are undesirable, otherwise the reference wouldn't have been replaced.

WBDT - Workbench Data/Uses Skill - Smithing on CraftingSmelterMarker1 comes from Complete Crafting Overhaul_Remastered.esp, and is faithfully copied into DynDOLOD.esp, which is where the 'Has Distant LOD' flag is added as well.

MNAM - Active Markers comes from Skyrim.esm, and I'm uncertain what benefit removing it has; ...do markers work even if the reference is disabled?

I'm going to try copying MNAM and WBDT from CraftingSmelterMarker1 -> CraftingSmelterMarker1_DynDOLOD_NOFLAG to see if that also allows using the Smelter.

I can not reproduce this with Alpha-92 and Skyrim AE. There is no change to xxxxxE60 in ccvsvsse004-beafarmer.esl or any other reference using 0009C6CE.
As mentioned earlier, a similar issue with a Hearthfire smelter was reported before and was already addressed in Alpha 89.

Make sure you are actually using the latest version. Unpack the DynDOLOD Standalone archive into a new and empty folder.

[DarthVitrial]

Crashed while generating dynamic LOD in alpha 92. (Error: Assertion failure (C:\Delphi\Projects\DynDOLOD3\Core\wbImplementation.pas, line 17465) while processing Glenmoril.esm [REFR:1C000E6B] (places zzzRevDeadHillDockStrent04 [STAT:1C000D8B] in GRUP Cell Temporary Children of RevPortWorm01 [CELL:1C001A52] (in zRevNamiraRealm "Surtsbrunnr" [WRLD:1C000D62] at -8,-1))

 

Bugreport attached.

Logs: https://mega.nz/file/FwMy1SgY#97RtdF4n0J7nLdvKS9-wILFBcyVry6IC5AMOupj1uVw

bugreport.txt

[sheson]

1 hour ago, DarthVitrial said:

Crashed while generating dynamic LOD in alpha 92. (Error: Assertion failure (C:\Delphi\Projects\DynDOLOD3\Core\wbImplementation.pas, line 17465) while processing Glenmoril.esm [REFR:1C000E6B] (places zzzRevDeadHillDockStrent04 [STAT:1C000D8B] in GRUP Cell Temporary Children of RevPortWorm01 [CELL:1C001A52] (in zRevNamiraRealm "Surtsbrunnr" [WRLD:1C000D62] at -8,-1))

 

Bugreport attached.

Logs: https://mega.nz/file/FwMy1SgY#97RtdF4n0J7nLdvKS9-wILFBcyVry6IC5AMOupj1uVw

bugreport.txt 171.8 kB · 1 download

That is not repeatable, is it?

[DarthVitrial]

10 hours ago, sheson said:

That is not repeatable, is it?

it happened like  twice out of 20 runs, so it seems it was just that rare race condition popping up.

[z929669]

On 5/24/2022 at 1:47 AM, sheson said:

Normally full grass has no normal maps. Hence the grass LOD billboard generation uses the default flat normal map as substitute.
Complex grass now has a normal map texture, so the grass LOD billboard generation uses it. Since object LOD requires normal map texture, and so does grass LOD, nothing else needs to change. Since complex full grass has normal maps too now, it means the grass LOD billboard direct/ambient light settings in TexGen and/or the GrassBrightness* INI settings most likely need adjusting. If ENB uses the "standard" shader for complex grass so it behaves like everything else including object LOD, then it the light between full grass / grass LOD should now behave full trees and HD tree billboards with Billboard1. Maybe try same direct/ambient light as HD billboards and the same values RGB GrassBrightnessTop* and GrassBrightnessBottom* respectively, so the color tone is not changed. 

If there is difference between full grass and grass LOD that me and speculate on, make a screenshot directly looking at it. All the screenshot you posted shows me is that there is grass LOD in the distance and there is full grass in the front. Maybe they are supposed to be different grass. Maybe the grass LOD needs brightness adjustment. Maybe a certain full grass has no billboard. Maybe the full grass fades badly because of its mipmaps.

Obviously, determine a specific full grass model in question and check its generated billboard texture looks as expected.

------

The temp textures filenames TexGen adds to the billboards txt seem to be wrong, since they are unlikely to be the texture filename(s) defined in the ferngrass01a.nif.
So ignore the message about the textures for now until next version.

 

Just wondering if the consistency check file paths/reference issue was addressed in Alpha 93, as it's not obvious to me in the changelog. If it has been fixed, I will test sooner rather than later. I'm in the midst of creating my own complex grass versions for Cathedral Landscapes to see if I can't make the normals behave a bit more predictably.

[sheson]

12 hours ago, DarthVitrial said:

it happened like  twice out of 20 runs, so it seems it was just that rare race condition popping up.

See if there is any difference with Alpha-93.

7 hours ago, z929669 said:

Just wondering if the consistency check file paths/reference issue was addressed in Alpha 93, as it's not obvious to me in the changelog. If it has been fixed, I will test sooner rather than later. I'm in the midst of creating my own complex grass versions for Cathedral Landscapes to see if I can't make the normals behave a bit more predictably.

Yes it should have. I forgot to add it to the changelog.

[DarthVitrial]

49 minutes ago, sheson said:

See if there is any difference with Alpha-93.

 

Don't want to jinx it but it seems to be fixed in 93.

[Emayn]

Hi - I've been running Dyndolod now for around 8 hours and it's still not completed. There's no error logs as it is still running - I get the occasional bit of activity but I'm sure this isn't right!
Specs are Intel Core i7-3770K CPU@ 3.50GHz, 16GB RAM, 8GB Asus Rog Strix Geforce GTX 1080

Anyone come across it being this slow or what I should be looking to do? It's still running currently and using a bit of memory (around 1-2k MBs) but very little cpu - up to 1%

Edited June 2, 2022 by Emayn

[sheson]

1 hour ago, Emayn said:

Hi - I've been running Dyndolod now for around 8 hours and it's still not completed. There's no error logs as it is still running - I get the occasional bit of activity but I'm sure this isn't right!
Specs are Intel Core i7-3770K CPU@ 3.50GHz, 16GB RAM, 8GB Asus Rog Strix Geforce GTX 1080

Anyone come across it being this slow or what I should be looking to do? It's still running currently and using a bit of memory (around 1-2k MBs) but very little cpu - up to 1%

No  load order or used settings were provided.
The main log and debug log will be saved when the program is closed. Until then the messages log can be copied and pasted to the clipboard or screenshotted if everything else fails to show what the current process is. 

For the vanilla game with default settings TexGen should take about 2 min, DynDOLOD about 5.

https://dyndolod.info/FAQ under "DynDOLOD/TexGen Questions" check the answers for "Long running time or output several GB in file size" and "High memory usage"

[SidDaNumidium]

Hello, I'm encountering a problem related to Dyndolod 3.0 where I get a cyclic error as seen in the attached image . I've attempted to address this by making 0Kaidan.esp an esm file via SSEedit but the same error just moves to another mod in relation to Dyndolod (I've also checked the masters of Kaidan in sseedit to confirm Dyndolod wasn't a master for some reason, which it isn't) . My Dyndolod log files are too big to attach to this post but the portion of them in the image seems to imply that Dyndolod had generated successfully, which had seemed to be the problem that the last user I saw on the forum who encountered this problem faced. I've also attempted to regen the Dyndolod files to confirm this issue, and after regening them it seems to be the case. I'm unsure how to proceed from here and any assistance regarding this matter would be greatly appreciated. Thanks! Edit1 - Added bugreport.txt as an attachment

bugreport.txt

Edited June 2, 2022 by SidDaNumidium
Edit1 - Added bugreport.txt as an attachment

[SidDaNumidium]

Seems like my post was moved here but as a followup to the my post above, this is my DynDOLOD log file. https://paste.ee/p/iYWJ8

[sheson]

58 minutes ago, SidDaNumidium said:

Hello, I'm encountering a problem related to Dyndolod 3.0 where I get a cyclic error as seen in the attached image . I've attempted to address this by making 0Kaidan.esp an esm file via SSEedit but the same error just moves to another mod in relation to Dyndolod (I've also checked the masters of Kaidan in sseedit to confirm Dyndolod wasn't a master for some reason, which it isn't) . My Dyndolod log files are too big to attach to this post but the portion of them in the image seems to imply that Dyndolod had generated successfully, which had seemed to be the problem that the last user I saw on the forum who encountered this problem faced. I've also attempted to regen the Dyndolod files to confirm this issue, and after regening them it seems to be the case. I'm unsure how to proceed from here and any assistance regarding this matter would be greatly appreciated. Thanks! Edit1 - Added bugreport.txt as an attachment

bugreport.txt 879.14 kB · 2 downloads

I moved the post the DynDOLOD 3 Alpha thread.

Read the first post which log and debug log to upload to a file or paste service when making posts. Do not post screenshots of text.

Always use the latest DynDOLOD version.

The DynDOLOD.esm is not supposed to contain any non ESM flagged as masters. I need to the log files to see what went wrong / try to reproduce the problem.

25 minutes ago, SidDaNumidium said:

Seems like my post was moved here but as a followup to the my post above, this is my DynDOLOD log file. https://paste.ee/p/iYWJ8

Also upload the debug log to a paste or file service.

[SidDaNumidium]

23 minutes ago, sheson said:

I moved the post the DynDOLOD 3 Alpha thread.

Read the first post which log and debug log to upload to a file or paste service when making posts. Do not post screenshots of text.

Always use the latest DynDOLOD version.

The DynDOLOD.esm is not supposed to contain any non ESM flagged as masters. I need to the log files to see what went wrong / try to reproduce the problem.

Yes, sorry about that. https://paste.ee/p/iYWJ8 Here is the "DynDOLOD_SSE_log", https://paste.ee/p/tAbCr Here is the "bugreport.txt", and https://ufile.io/l3sgz89j here is the "DynDOLOD_SSE_Debug_log".

[sheson]

33 minutes ago, SidDaNumidium said:

Yes, sorry about that. https://paste.ee/p/iYWJ8 Here is the "DynDOLOD_SSE_log", https://paste.ee/p/tAbCr Here is the "bugreport.txt", and https://ufile.io/l3sgz89j here is the "DynDOLOD_SSE_Debug_log".

That generation is with 0Kaidan.esp having the master flag. What is the "other" plugin that has the cyclic interaction in that case?

This is with Kaidan 2.1.1?

[SidDaNumidium]

1 hour ago, sheson said:

That generation is with 0Kaidan.esp having the master flag. What is the "other" plugin that has the cyclic interaction in that case?

This is with Kaidan 2.1.1?

The other plugin was better courier.esp, and this was with Kaidan 2.1.1. I'm also on Skyrim AE in case that changes anything.

Currently, I had made it not a master in sseedit, ran LOOT again and I got the same error. Then I disabled the dyndolod output mod folder in MO2 (left pane), made Kaidan a master again via sseedit, re-enabled the Dyndolod output and am running LOOT and it just finished successfully so I'm not sure why exactly it worked this time and not previously. Sorry this is really weird I spent some time yesterday working through this with someone else and it wasn't working then and nothing else has changed in my setup.

I'm also happy to test continue testing if wanted too to see if this was a weird one-off error or a something demonstrably reproducible.

Edited June 2, 2022 by SidDaNumidium