DynDOLOD 3.00 Alpha 190

[sheson]

  On 11/11/2022 at 6:13 PM, BISOM said:

 

1) Do you get the Exit, check log, restart prompt when using the cancel button on the wizard/advanced window?

sorry i'm not quiet understand this.

2) TexGen prompt is just look like this. Like every time I did past few years.

 

3) deleted the theme folder and run Dyndolod again

failed. prompt didn't show up.

Expand  

Why do you keep posting screenshots of TexGen that shows the prompt? It seems to be working.

When the DynDOLOD messages window shows like this, it does not react to mouse or keyboard? Can you move the scroll bar down? Is there any CPU usage in the task manager?

After starting DynDOLOD, either the wizard or advanced options window shows. When you click cancel, there will be a prompt to asking to exit, check log or restart. Does that work?

See what happens if you do not select to generate Occlusion.

[mutz]

I received an item not found error for reachclifftree02_1ad939d8_trunk_2.dds

logs attached

debug: https://ufile.io/jzui8wsq

bugreport.txtFetching info... DynDOLOD_SSE_log.txtFetching info...

[sheson]

  On 11/11/2022 at 7:47 PM, mutz said:

I received an item not found error for reachclifftree02_1ad939d8_trunk_2.dds

logs attached

debug: https://ufile.io/jzui8wsq

bugreport.txt 161.58 kB · 1 download DynDOLOD_SSE_log.txt 135.75 kB · 2 downloads

Expand  

Looks like a race condition. Does it run through or mention a different texture when you try again?

[mutz]

  On 11/11/2022 at 8:21 PM, sheson said:

Looks like a race condition. Does it run through or mention a different texture when you try again?

Expand  

Just finished running dyndolod again, worked perfectly this time without error. I didn't even change any settings or add/remove mods. Odd

[sheson]

  On 11/11/2022 at 9:04 PM, mutz said:

Just finished running dyndolod again, worked perfectly this time without error. I didn't even change any settings or add/remove mods. Odd

Expand  

It makes sense to me. Thanks for reporting.

[jiggajigga82]

Hello, I was instructed to post my TexGen Range Check Error here.

Bug report: https://ufile.io/lu9ymmzx

Debug log: https://ufile.io/wj78imxt

TexGen log: https://ufile.io/aiokrenm

And:

[Window Title]
TexGen

[Main Instruction]
Error: Range check error.

[Content]

Click on this link for additional explanations and help for this message

[OK] [Exit TexGen]

[Footer]
Online Help | Support Forum | Copy message to clipboard

If I'm missing anything that's supposed to be reported, please let me know.

 

[sheson]

  On 11/11/2022 at 9:16 PM, jiggajigga82 said:

Hello, I was instructed to post my TexGen Range Check Error here.

Bug report: https://ufile.io/lu9ymmzx

Debug log: https://ufile.io/wj78imxt

TexGen log: https://ufile.io/aiokrenm

And:

[Window Title]
TexGen

[Main Instruction]
Error: Range check error.

[Content]

Click on this link for additional explanations and help for this message

[OK] [Exit TexGen]

[Footer]
Online Help | Support Forum | Copy message to clipboard

If I'm missing anything that's supposed to be reported, please let me know.

 

Expand  

https://dyndolod.info/Installation-Instructions
Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory ...

Do not unpack into a folder still containing older versions.

There seems to be a worldspace with weird wordspace bounds https://dyndolod.info/Messages/Worldspace-Bounds.
Unfortunately the log does not hint which one. You might spot it if you check the worldspace records in xEdit. Next version will try to print which worldspace has the issue.
The error does not affect the TexGen output anymore, so you can use it.

What happens when you run DynDOLOD? There should be a similar error?

[jiggajigga82]

  On 11/11/2022 at 9:39 PM, sheson said:

https://dyndolod.info/Installation-Instructions
Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory ...

Do not unpack into folder already still containing older versions.

There seems to be a worldspace with weird wordspace bounds https://dyndolod.info/Messages/Worldspace-Bounds.
Unfortunately the log does not hint which one. You might spot it if you check the worldspace records in xEdit. Next version will try to print which worldspace has the issue.
The error does not affect the TexGen output anymore, so you can use it.

What happens when you run DynDOLOD? There should be a similar error?

Expand  

Thank you for the quick response! I just deleted the previous installation and did a fresh extract.

I'll take a look in xEdit.

I don't get much TexGen output, or do you mean I should use what's there to test DynDOLOD?

 

Edited November 11, 2022 by jiggajigga82

[sheson]

  On 11/11/2022 at 9:54 PM, jiggajigga82 said:

Thank you for the quick response! I just deleted the previous installation and did a fresh extract.

I'll take a look in xEdit.

I don't get much TexGen output, or do you mean I should use what's there to test DynDOLOD?

Expand  

Yes, it is possible that DynDOLOD has a more information when it encounters the same problem.

[jiggajigga82]

  On 11/11/2022 at 10:06 PM, sheson said:

Yes, it is possible that DynDOLOD has a more information when it encounters the same problem.

Expand  

Same error in DynDOLOD

Bug Report: https://ufile.io/rav3jxk1

Log: https://ufile.io/lrtk0i5h

Debug Log: https://ufile.io/zyp77kti

The last worldspace referenced in the log is the new mod that expands Saints and Seducers.

For reference: https://www.nexusmods.com/skyrimspecialedition/mods/72772/

Update: I removed the aforementioned mod and TexGen doesn't error out right away. Still running...

Edited November 11, 2022 by jiggajigga82

[sheson]

  On 11/11/2022 at 10:19 PM, jiggajigga82 said:

Same error in DynDOLOD

Bug Report: https://ufile.io/rav3jxk1

Log: https://ufile.io/lrtk0i5h

Debug Log: https://ufile.io/zyp77kti

The last worldspace referenced in the log is the new mod that expands Saints and Seducers.

For reference: https://www.nexusmods.com/skyrimspecialedition/mods/72772/

Update: I removed the aforementioned mod and TexGen doesn't error out right away. Still running...

Expand  

Run this test version of TexGen https://mega.nz/file/xEJBTarA#zQPw9J9g4VZqnRlnTevplIrnaHyaZqtsvL3rdIBsnbk

It should mention the worldspace the error happens in. Then check the Object Bounds of all plugins modifying that worldpace.

[jiggajigga82]

  On 11/11/2022 at 10:46 PM, sheson said:

Run this test version of TexGen https://mega.nz/file/xEJBTarA#zQPw9J9g4VZqnRlnTevplIrnaHyaZqtsvL3rdIBsnbk

It should mention the worldspace the error happens in. Then check the Object Bounds of all plugins modifying that worldpace.

Expand  

 

I attached screenshots of the xEdit record headers of the respective records that modify the worldspace.

Bug report: https://ufile.io/uura8iyl

TexGen log: https://ufile.io/ys466lak

Debug log: https://ufile.io/ebzbax9x

[Window Title]
TexGen

[Main Instruction]
Error: Range check error while processing worldspace bounds Skyrim Extended Cut - Saints and Seducers.esp ECSSzDummyMarkerWorld [WRLD:1655C4B3]

[Content]

Click on this link for additional explanations and help for this message

[Exit TexGen]

[Footer]
Online Help | Support Forum | Copy message to clipboard

[sheson]

  On 11/11/2022 at 11:21 PM, jiggajigga82 said:

 

I attached screenshots of the xEdit record headers of the respective records that modify the worldspace.

Bug report: https://ufile.io/uura8iyl

TexGen log: https://ufile.io/ys466lak

Debug log: https://ufile.io/ebzbax9x

[Window Title]
TexGen

[Main Instruction]
Error: Range check error while processing worldspace bounds Skyrim Extended Cut - Saints and Seducers.esp ECSSzDummyMarkerWorld [WRLD:1655C4B3]

[Content]

Click on this link for additional explanations and help for this message

[Exit TexGen]

[Footer]
Online Help | Support Forum | Copy message to clipboard

Expand  

For time being, set the bounds to valid numbers like 0.

[jiggajigga82]

  On 11/11/2022 at 11:37 PM, sheson said:

For time being, set the bounds to valid numbers like 0.

Expand  

NAM0 and NAM9, correct?

[sheson]

  On 11/11/2022 at 11:43 PM, jiggajigga82 said:

NAM0 and NAM9, correct?

Expand  

Yes, replace both the "default" and "min"