DynDOLOD 3.00 Alpha 182

[burnersaurus]

5 minutes ago, sheson said:

Cells that have no grass cache file won''t have grass LOD. Doesn't really make sense to only delete the file then not start the game to create the cell real quick.

Well yes and no.. I agree it would be best, however in order to run No Grass in Objects, even for just one cell, I would have to downgrade SKyrim AE to Skyrim SE once more, with all the hassel that intails.. I might well do that, however, I want to know my options.. after all, the cell in question might be snowy mountain cell, with no grass at all..

[Traevelliath]

DynDOLOD 3 started to crash (without any logs) shortly after I click "ok" and begin generating LODs, MO2 left locked waiting for textconv64.exe to finish, and it never would.
Please help.
https://imgur.com/a/ribhLSC

bugreport.txt DynDOLOD_SSE_Debug_log.txt

[ButchDiavolo]

Heyas Sheson,

While running TexGen (latest DynDOLOD and DynDOLOD Resources), I got a number of "Access violation at address" messages and TexGen stopped working. Unfortunately I have no idea how to read bugreports, so I have no idea what is causing it. I have set all the necessary files as exclusions in my antivirus programs.

 

Here are the logs:

Logs.7z

[sheson]

1 hour ago, Traevelliath said:

DynDOLOD 3 started to crash (without any logs) shortly after I click "ok" and begin generating LODs, MO2 left locked waiting for textconv64.exe to finish, and it never would.
Please help.
https://imgur.com/a/ribhLSC

bugreport.txt 42.76 kB · 1 download DynDOLOD_SSE_Debug_log.txt 178.08 kB · 5 downloads

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.

8 minutes ago, ButchDiavolo said:

Heyas Sheson,

While running TexGen (latest DynDOLOD and DynDOLOD Resources), I got a number of "Access violation at address" messages and TexGen stopped working. Unfortunately I have no idea how to read bugreports, so I have no idea what is causing it. I have set all the necessary files as exclusions in my antivirus programs.

 

Here are the logs:

Logs.7z 134.06 kB · 0 downloads

"Exception Message: Out of memory"

Use the x64 version.

[Traevelliath]

31 minutes 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.

There is no such proccess in task manager, I tried rebooting numerous times.
Also DynDOLOD 2.98 works just fine, so I assume OS or UAC have nothing to do with it? MO2 is launched with Admin rights and I do not use any anti-virus.

Edited January 18, 2022 by Traevelliath

[sheson]

1 hour ago, Traevelliath said:

There is no such proccess in task manager, I tried rebooting numerous times.
Also DynDOLOD 2.98 works just fine, so I assume OS or UAC have nothing to do with it? MO2 is launched with Admin rights and I do not use any anti-virus.

If MO2 says it is waiting for X, it typically means that X is still active. It will at least mean the the virtual file system is still locked for that and anything else trying to use it probably has problems.

Windows Defender is an anti virus. 

DynDOLOD 2.x is a different program. Any comparison to it is irrelevant.

Check the Windows Event log for hints.

[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?