DynDOLOD 3.00 Alpha 182

[sheson]

46 minutes ago, enthe said:

Texgen from 66, 67, 68, 69 are all creating completely black billboards which were previously skipped - and they then show up in game as ugly black boxes (picture 2).

On _65 with resource 19 I did not have this issue.  Everything looked great.

First pic is a screenshot of the raw, full size texture - all of the grasses which are having this issue look similar (e.g. a lot more blank space than texture). 

I'm posting the entire log below, but I'm not sure how much good it does you.  Here's an example of a grass that I'm talking about though there are 30~ sets of _1.dds , _2.dds , .txt that are pretty much identical 24 x varies .dds that are just solid black.  Again, previous versions skipped these

[LOD]

Width=124.639595

Depth=100.611389

Height=71.222626

ShiftX=0.000000

ShiftY=0.000000

ShiftZ=-2.420879

Scale=1.000000

Width_1=115.965782

Height_1=71.222626

Adjust_1=-2.654934

Width_2=88.443649

Height_2=71.222626

Adjust_2=-6.083870

Model=Meshes\landscape\grass\grass_clump_dead.nif

ModelCRC32=B86D2067

Texture_1=textures\landscape\grass\Grass_Clump_Dead.dds

TextureCRC32_1=4F6E9678

 

Secondly, it's probably not relevant since the above mesh meets size criteria below.... but:

Texgen.ini has this ; automatic tree/grass discovery - base record object bounds Sqrt((X2-X1)^2 + (Y2-Y1)^2 + (Z2-Z1)^2) >= Min[Tree|Grass]ModelVolume

is not volume it's size of the bounding box. Please don't yell at me if pedantic, just was trying to solve this on my own. never had a reason to check this though.

Happy to send meshes/textures, whatever. Not sure if it's just a bugged mesh that's now showing up or what.

Thanks!

TexGen_SSE_Debug_log.txt 802.76 kB · 2 downloads texgen_sse_log.txt 35.34 kB · 2 downloads

Alpha-70 should not create those anymore. Let me know in case there are still problems.

[dregoc]

I am using dyndolod for the first time and I cant resolve this issue. I am using Dyndolod 3.

the messages:

DynDOLOD can not find master data in DynDOLOD_WhiterunWorld

DynDOLOD can not read data from DynDOLOD_WhiterunWorld

 

I checked the faq but eveything seems to be fine.

I have the latest version of PapyrusUtil and its not being overwritten by anything,  the esp , json and txts are all from the same generation, and they all share the same bunch of numbers. And of course all of the outputs are inside the data folder.

While executing DynDOLOD everything seems to be fine, it completes succesfully as far as I can tell.

In the overwold everythting seems fine the issue only pops up when inside a city.

[sheson]

19 minutes ago, dregoc said:

I am using dyndolod for the first time and I cant resolve this issue. I am using Dyndolod 3.

the messages:

DynDOLOD can not find master data in DynDOLOD_WhiterunWorld

DynDOLOD can not read data from DynDOLOD_WhiterunWorld

 

I checked the faq but eveything seems to be fine.

I have the latest version of PapyrusUtil and its not being overwritten by anything,  the esp , json and txts are all from the same generation, and they all share the same bunch of numbers. And of course all of the outputs are inside the data folder.

While executing DynDOLOD everything seems to be fine, it completes succesfully as far as I can tell.

In the overwold everythting seems fine the issue only pops up when inside a city.

I moved your post to the the DynDOLOD 3 Alpha thread.

If you look at a few of the posts above, then you will see that Alpha-70 should fix that problem.

In case it doesn't, upload the log and debug log as explained in the first post.

[PRieST]

Hm, seems that DynDOLOD is not working as supposed to with Alpha-70.
I know how long it takes normally until finished. On my end it is about 45-60 minutes.
At the moment a run is ongoing, but it seems, that the process won't finish. It's lasting 1 hour and 40 minutes now without any progress. The process itself is not stuck, though, but this never happened before.
Is it possible that somehow the installation messed up? I just changed the .exe files and corresponding files instead of deleting the old files. Or could this be something else? I've gotten no errors until now so I can't provide any bugreport.logs, just the normal logs. If I would force kill the process now, could you make use of the generated logs?

Edit: I just killed it now and reinstall and start over. Never the less, here are the logfiles from that run, in case there is in error: Download

Edited February 13, 2022 by PRieST

[sheson]

18 minutes ago, PRieST said:

Hm, seems that DynDOLOD is not working as supposed to with Alpha-70.
I know how long it takes normally until finished. On my end it is about 45-60 minutes.
At the moment a run is ongoing, but it seems, that the process won't finish. It's lasting 1 hour and 40 minutes now without any progress. The process itself is not stuck, though, but this never happened before.
Is it possible that somehow the installation messed up? I just changed the .exe files and corresponding files instead of deleting the old files. Or could this be something else? I've gotten no errors until now so I can't provide any bugreport.logs, just the normal logs. If I would force kill the process now, could you make use of the generated logs?

Edit: I just killed it now and reinstall and start over. Never the less, here are the logfiles from that run, in case there is in error: Download

Keep an eye on memory usage and maybe set OcclusionMaxThreadsObjectLOD=1 in the DynDOLOD INI as explained on  https://dyndolod.info/Help/Occlusion-Data

I think I will set that value automatically if Grass LOD is generated as well.

[PRieST]

'Memory comsumption' was normal as with every other alpha version before (between 7 to 8 GB). Maybe I did messed up with just copying the new files.

I'll check the ini setting you mentioned if my second run also doesn't finish correctly. I never changed this value, was using the default setting all the time.

[dregoc]

1 hour ago, sheson said:

I moved your post to the the DynDOLOD 3 Alpha thread.

If you look at a few of the posts above, then you will see that Alpha-70 should fix that problem.

In case it doesn't, upload the log and debug log as explained in the first post.

Yep, that fixed it, thanks a lot.

[DarkladyLexy]

It been nearly 2 hours and DynDOLOD hasn't even finished I know DynDOLOD takes awhile but it usually done in about 45 mins for me not 2 hours.

[adancau]

Having an issue with TexGen that's just started now with Alpha 70 (Alpha 69 and lower all work well):

[Main Instruction]
Texconv error 80070002.

[Content]
"C:\Users\XXXXX\AppData\Local\ModOrganizer\Skyrim SE\tools\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -sepalpha -aw 256 -m 1 -f BC7_UNORM -bc q -o "D:\Mod Repository\Skyrim SE & VR\texgen_output\textures\terrain\lodgen\cathedral landscapes.esp" -flist "C:\Users\XXXXX\AppData\Local\Temp\TexGen_SSE\Texconv_295_2.txt"

It's always happening on a different billboard though, but always very late in the process. This is another example, on a successive run.

[Content]
"C:\Users\XXXXX\AppData\Local\ModOrganizer\Skyrim SE\tools\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -sepalpha -aw 256 -m 1 -f BC7_UNORM -bc q -o "D:\Mod Repository\Skyrim SE & VR\texgen_output\textures\terrain\lodgen\cathedral landscapes.esp" -flist "C:\Users\XXXXX\AppData\Local\Temp\TexGen_SSE\Texconv_300_1.txt"

Log excerpt (as I said, it's always a different .nif):

[01:43]     Creating billboard D:\Mod Repository\Skyrim SE & VR\texgen_output\textures\terrain\lodgen\skyrim.esm\treeaspen06_0007614a with Meshes\landscape\trees\treeaspen06.nif Skyrim.esm TreeAspen06 [TREE:0007614A]
[01:44]  FAILED (80070002: The system cannot find the file specified.)
[01:44] Error: Texconv error 80070002 "C:\Users\XXXXX\AppData\Local\ModOrganizer\Skyrim SE\tools\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -sepalpha -aw 256 -m 1 -f BC7_UNORM -bc q -o "D:\Mod Repository\Skyrim SE & VR\texgen_output\textures\terrain\lodgen\cathedral landscapes.esp" -flist "C:\Users\XXXXX\AppData\Local\Temp\TexGen_SSE\Texconv_300_1.txt"

I have tried disabling Windows Defender, adding more rules, but nothing fixes it. Reverting to an older version of DynDOLOD, as I mentioned above, works without fail (tried 69, 68 and 66).

[sheson]

1 hour ago, PRieST said:

'Memory comsumption' was normal as with every other alpha version before (between 7 to 8 GB). Maybe I did messed up with just copying the new files.

I'll check the ini setting you mentioned if my second run also doesn't finish correctly. I never changed this value, was using the default setting all the time.

 

51 minutes ago, DarkladyLexy said:

It been nearly 2 hours and DynDOLOD hasn't even finished I know DynDOLOD takes awhile but it usually done in about 45 mins for me not 2 hours.

Yes, I think something "broke" Occlusion generation reading object LOD meshes so it takes forever. Will be fixed in Alpha-71 ASAP.

[DarkladyLexy]

9 minutes ago, sheson said:

 

Yes, I think something "broke" Occlusion generation reading object LOD meshes so it takes forever. Will be fixed in Alpha-72 ASAP.

I have a log it that will help?

[sheson]

21 minutes ago, adancau said:

Having an issue with TexGen that's just started now with Alpha 70 (Alpha 69 and lower all work well):

[Main Instruction]
Texconv error 80070002.

[Content]
"C:\Users\XXXXX\AppData\Local\ModOrganizer\Skyrim SE\tools\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -sepalpha -aw 256 -m 1 -f BC7_UNORM -bc q -o "D:\Mod Repository\Skyrim SE & VR\texgen_output\textures\terrain\lodgen\cathedral landscapes.esp" -flist "C:\Users\XXXXX\AppData\Local\Temp\TexGen_SSE\Texconv_295_2.txt"

It's always happening on a different billboard though, but always very late in the process. This is another example, on a successive run.

[Content]
"C:\Users\XXXXX\AppData\Local\ModOrganizer\Skyrim SE\tools\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -sepalpha -aw 256 -m 1 -f BC7_UNORM -bc q -o "D:\Mod Repository\Skyrim SE & VR\texgen_output\textures\terrain\lodgen\cathedral landscapes.esp" -flist "C:\Users\XXXXX\AppData\Local\Temp\TexGen_SSE\Texconv_300_1.txt"

Log excerpt (as I said, it's always a different .nif):

[01:43]     Creating billboard D:\Mod Repository\Skyrim SE & VR\texgen_output\textures\terrain\lodgen\skyrim.esm\treeaspen06_0007614a with Meshes\landscape\trees\treeaspen06.nif Skyrim.esm TreeAspen06 [TREE:0007614A]
[01:44]  FAILED (80070002: The system cannot find the file specified.)
[01:44] Error: Texconv error 80070002 "C:\Users\XXXXX\AppData\Local\ModOrganizer\Skyrim SE\tools\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -sepalpha -aw 256 -m 1 -f BC7_UNORM -bc q -o "D:\Mod Repository\Skyrim SE & VR\texgen_output\textures\terrain\lodgen\cathedral landscapes.esp" -flist "C:\Users\XXXXX\AppData\Local\Temp\TexGen_SSE\Texconv_300_1.txt"

I have tried disabling Windows Defender, adding more rules, but nothing fixes it. Reverting to an older version of DynDOLOD, as I mentioned above, works without fail (tried 69, 68 and 66).

There is really nothing a program (in this case both TexConv can do about the OS or antivir  denying write access. I mean if a program could circumvent it it would be malicious.

Texconv.exe didn't change since December. The way TexGen uses to build convert textures did not change since Alpha-66.

If the same setup and paths work with Alpha-66 to Alpha-69 I can not really suggest anything else but to hope the next version has different byte code again so it won't trigger anything.

12 minutes ago, DarkladyLexy said:

I have a log it that will help?

No need. Thanks.

[adancau]

14 minutes ago, sheson said:

If the same setup and paths work with Alpha-66 to Alpha-69 I can not really suggest anything else but to hope the next version has different byte code again so it won't trigger anything.

Will post an update re: behavior on the next Alpha. Thanks.

Edited February 13, 2022 by adancau

[sheson]

1 hour ago, PRieST said:

'Memory comsumption' was normal as with every other alpha version before (between 7 to 8 GB). Maybe I did messed up with just copying the new files.

I'll check the ini setting you mentioned if my second run also doesn't finish correctly. I never changed this value, was using the default setting all the time.

 

55 minutes ago, DarkladyLexy said:

It been nearly 2 hours and DynDOLOD hasn't even finished I know DynDOLOD takes awhile but it usually done in about 45 mins for me not 2 hours.

Fixed in Alpha-71

[PRieST]

59 minutes ago, sheson said:

Fixed in Alpha-71

Thank you, just started a new generation cycle.

Edit: Everything is working now.

Edited February 13, 2022 by PRieST