DynDOLOD 3.00 Alpha 182

[ButchDiavolo]

1 hour ago, sheson said:

Use task manager to end Texconvx64.exe. Maybe reboot.

Make sure that OS, UAC, antivir is not interfering with DynDOLODx64.exe, TexGenx64.exe, Texconvx64.exe or LODGenx64.exe.

"Exception Message: Out of memory"

Use the x64 version.

OMG *facepalm* I am an idiot... Thank you.

[Traevelliath]

22 minutes ago, sheson said:

Check the Windows Event log for hints.

https://imgur.com/a/ribhLSC
It says this. Could you provide me with some pointers please?
Also I don't have windows defender on my PC.

Edited January 18, 2022 by Traevelliath

[sheson]

18 minutes ago, Traevelliath said:

https://imgur.com/a/ribhLSC
It says this. Could you provide me with some pointers please?
Also I don't have windows defender on my PC.

Make sure to download the latest version and to unpack it into a new and empty folder. Do not overwrite or mix with older versions.

The tools use standard OS functions to access files and folders. Whatever happens beyond these functions is out of the control of programs.

Check the hints given by the event 1005 about disk problems and what to do about them.

If the disk has no errors etc. check MO2 virtual file system / log.

And again, UAC, antivir or any similar 3rd party programs that might control and interfere file access.

It may be caused while trying to read a specific texture (via Texconv). So it could be either C (temp folder) or D drive.

[z929669]

2 hours ago, Traevelliath said:

https://imgur.com/a/ribhLSC
It says this. Could you provide me with some pointers please?
Also I don't have windows defender on my PC.

If you are running Windows 10 (or even earlier versions, unless I'm mistaken), then you are running Windows Security in one form or another (Windows Defender handles the firewall in Win10+ and possibly earlier versions). Windows update can also change the state of native OS security apps. Regardless, you may want to see this topic best answers:

 

[Traevelliath]

11 minutes ago, z929669 said:

If you are running Windows 10 (or even earlier versions, unless I'm mistaken), then you are running Windows Security in one form or another (Windows Defender handles the firewall in Win10+ and possibly earlier versions). Windows update can also change the state of native OS security apps. Regardless, you may want to see this topic best answers:

 

Thank you, I'll look into it.
However, I was able to successfully run DynDOLOD 3 in safe mode. That's something for me to move from.

[jwisser]

When using Alpha-64, DynDOLOD removes a tower structure introduced by the mod Fortified Whiterun. Using identical load order and the same (latest) version of DynDOLOD Resources SE 3 and DynDOLOD DLL SE, but building the plugins with an older version ("DynDOLODx64.exe, Version: 3.0.0.0, Date: 2021-12-15 09:05:25", per the log), the tower structure is present as expected. In neither case does DynDOLOD produce any errors.

Using Alpha-64, the tower is not invisible; it is simply not present. The stairs that should be part of it can't be climbed, there's no collision where the walls should be, etc. Find attached screenshots showing the missing tower from Alpha-64, as well as data relating to the tower collected while running with the older version.

Forgive me if this report is missing key information; this is my first time reporting an issue with DynDOLOD and I'm not sure what all is useful. Just let me know what else you need and I will happily collect it. Thanks for your consideration!

[sheson]

26 minutes ago, jwisser said:

When using Alpha-64, DynDOLOD removes a tower structure introduced by the mod Fortified Whiterun. Using identical load order and the same (latest) version of DynDOLOD Resources SE 3 and DynDOLOD DLL SE, but building the plugins with an older version ("DynDOLODx64.exe, Version: 3.0.0.0, Date: 2021-12-15 09:05:25", per the log), the tower structure is present as expected. In neither case does DynDOLOD produce any errors.

Using Alpha-64, the tower is not invisible; it is simply not present. The stairs that should be part of it can't be climbed, there's no collision where the walls should be, etc. Find attached screenshots showing the missing tower from Alpha-64, as well as data relating to the tower collected while running with the older version.

Forgive me if this report is missing key information; this is my first time reporting an issue with DynDOLOD and I'm not sure what all is useful. Just let me know what else you need and I will happily collect it. Thanks for your consideration!

Post the logs as explained in the first post.

[jwisser]

Sorry, should have included these in the first place: Alpha-64 debug log is here (but 88MB) and main log is here (730KB). There was no bugreport.txt for this generation, and I was not prompted to copy any text to clipboard. Let me know if you also need logs from the older version.

Edited January 19, 2022 by jwisser

[sheson]

4 minutes ago, jwisser said:

Sorry, should have included these in the first place: debug log is here (but 88MB) and main log is here (730KB). There was no bugreport.txt for this generation, and I was not prompted to copy any text to clipboard.

What is the last screenshot showing. Is that the building that goes missing?

[jwisser]

4 minutes ago, sheson said:

What is the last screenshot showing. Is that the building that goes missing?

Yes, that's the interior of the tower, having clicked on it to show info about it in the console. It's roughly the same shot as the second screenshot, but with the tower present rather than missing.

[sheson]

5 minutes ago, jwisser said:

Yes, that's the interior of the tower, having clicked on it to show info about it in the console. It's roughly the same shot as the second screenshot, but with the tower present rather than missing.

Post a reference form id of a building or structure that goes missing while everything is working as it should, e.g. before generating LOD.

[jwisser]

15 minutes ago, sheson said:

Post a reference form id of a building or structure that goes missing while everything is working as it should, e.g. before generating LOD.

Reference form ID without DynDOLOD active is 8600AA28. Attached is another shot of the same interior without DynDOLOD active, showing the reference form ID and the fact that the ref was last changed by WhiterunDefenses.esp (whereas in the previous screenshot it was last changed by DynDOLOD).

EDIT: I should also mention that I noticed the tower IS visible as LOD from inside the Whiterun worldspace. It's only the physical tower in the Tamriel worldspace that seems to go missing.

Edited January 19, 2022 by jwisser

[sheson]

5 minutes ago, jwisser said:

Reference form ID without DynDOLOD active is 8600AA28. Attached is another shot of the same interior without DynDOLOD active, showing the reference form ID and the fact that the ref was last changed by WhiterunDefenses.esp (whereas in the previous screenshot it was last changed by DynDOLOD).

Test with a new game.

[jwisser]

3 minutes ago, sheson said:

Test with a new game.

These screenshots are all on brand new games, using

coc whiterunstables

from the menu screen to enter the world with the default character. Behavior is identical on a new game as well as on existing saves.

[sheson]

7 minutes ago, jwisser said:

These screenshots are all on brand new games, using

coc whiterunstables

from the menu screen to enter the world with the default character. Behavior is identical on a new game as well as on existing saves.

The screenshot from "inside" the tower shows that the model of the tower is loaded and showing. It is the same model and from id for outside the tower.

Explain or show how DynDOLOD makes this same full model disappear, while being in the same cell and DynDOLOD does nothing to the full model.

I can not replicate the issue with a vanilla load order + the mod.