DynDOLOD 3.00 Alpha 196

[sheson]

30 minutes ago, MysticElodie said:

Tested with the default Ultra INIs, no luck there. Disabling DynDOLOD's output files makes the snow appear as you'd expect from the vanilla LODs.

Noticed glancing again at the meshes that the LOD4 mountain's BSSubIndexTriShape has the name "objSnow-LargeRefobjSnowHD-LargeRef", which doesn't quite look right? But I'm not sure if that's anything.

meshes.zip 2.87 MB · 0 downloads

That really doesn't look alright. Let me check the files.

[sheson]

1 hour ago, MysticElodie said:

Tested with the default Ultra INIs, no luck there. Disabling DynDOLOD's output files makes the snow appear as you'd expect from the vanilla LODs.

Noticed glancing again at the meshes that the LOD4 mountain's BSSubIndexTriShape has the name "objSnow-LargeRefobjSnowHD-LargeRef", which doesn't quite look right? But I'm not sure if that's anything.

meshes.zip 2.87 MB · 1 download

Fixed in Alpha-84.

If you backup and restore the content of the folder ..\DynDOLOD\Edit Scripts\Export\*.*, then you can just "Execute LODGen" for the worldspace(s) in expert mode to update the object LOD meshes only. https://dyndolod.info/Help/Expert-Mode

[MysticElodie]

53 minutes ago, sheson said:

Fixed in Alpha-84.

If you backup and restore the content of the folder ..\DynDOLOD\Edit Scripts\Export\*.*, then you can just "Execute LODGen" for the worldspace(s) in expert mode to update the object LOD meshes only. https://dyndolod.info/Help/Expert-Mode

Worked perfectly, thanks a ton for the quick update!

[EvilBob773]

Hi, hope you're doing well. The texgenx64 works swimmingly for me but my dyndolod (newest version) refuses to run at all. This error persists no matter what I do,

Access violation at address 000000000191D60A in module 'DynDOLODx64.exe'. Read of address 0000000000000000
Error: Access violation at address 000000000191D60A in module 'DynDOLODx64.exe'. Read of address 0000000000000000.
User says "OK"
 

I tried turning off my anti-virus, and adding Dyndolod to the exceptions list, and running it and MO2 as admin but nothing seems to work ;(. Thanks for any help!

[sheson]

20 minutes ago, EvilBob773 said:

Hi, hope you're doing well. The texgenx64 works swimmingly for me but my dyndolod (newest version) refuses to run at all. This error persists no matter what I do,

Access violation at address 000000000191D60A in module 'DynDOLODx64.exe'. Read of address 0000000000000000
Error: Access violation at address 000000000191D60A in module 'DynDOLODx64.exe'. Read of address 0000000000000000.
User says "OK"
 

I tried turning off my anti-virus, and adding Dyndolod to the exceptions list, and running it and MO2 as admin but nothing seems to work ;(. Thanks for any help!

Read the first post which log and debug log and bugreport.txt if it exists to upload when making reports.

[EvilBob773]

24 minutes ago, sheson said:

Read the first post which log and debug log and bugreport.txt if it exists to upload when making reports.

Hi, my mistake sorry :P.

The DynDOLOD_SSE_Debug_log - https://pastebin.com/BYAP9iWG
and the DynDOLOD_SSE_log - https://pastebin.com/pvMVyi2m

Thanks very much for any assistance

DynDOLOD_SSE_Debug_log.txt DynDOLOD_SSE_log.txt

[sheson]

14 minutes ago, EvilBob773 said:

Hi, my mistake sorry :P.

The DynDOLOD_SSE_Debug_log - https://pastebin.com/BYAP9iWG
and the DynDOLOD_SSE_log - https://pastebin.com/pvMVyi2m

Thanks very much for any assistance

DynDOLOD_SSE_Debug_log.txt 340.87 kB · 0 downloads DynDOLOD_SSE_log.txt 333.86 kB · 0 downloads

Is there no bugreport.txt in the same folder as the executables?

No necessarily related but the game shouldn't be installed into special Windows folders like Program Files x86 to avoid issue with UAC, antivir etc.

[EvilBob773]

12 minutes ago, sheson said:

Is there no bugreport.txt in the same folder as the executables?

No, I can only see two files in the logs folder.

[sheson]

14 minutes ago, EvilBob773 said:

No, I can only see two files in the logs folder.

Please carefully read what I wrote ("in the same folder as the executables", e.g. DynDOLODx64.exe) and what the first post says the path (..\DynDOLOD\bugreport.txt) is supposed to be for it.

[EvilBob773]

14 minutes ago, sheson said:

Please carefully read what I wrote ("in the same folder as the executables", e.g. DynDOLODx64.exe) and what the first post says the path (..\DynDOLOD\bugreport.txt) is supposed to be for it.

Hi, sorry about it, here's the bug report,

https://pastebin.com/426pv7Yf

 

bugreport.txt

[sheson]

18 minutes ago, EvilBob773 said:

Hi, sorry about it, here's the bug report,

https://pastebin.com/426pv7Yf

bugreport.txt 132.06 kB · 1 download

Thanks. Did you unpack the Standalone into a new empty folder or where there old files from an earlier version?

Edit: Remove -PseudoESL from the command line options.

[EvilBob773]

19 minutes ago, sheson said:

Thanks. Did you unpack the Standalone into a new empty folder or where there old files from an earlier version?

Edit: Remove -PseudoESL from the command line options.

ooo yes that worked, thank you very much, hope everything goes swimmingly now :fingerscrossed:!

[Abbot]

Hello,

Can grass LOD be generated for Enderal Special Edition? If yes, which are the recommended settings for the grass?

[sheson]

1 hour ago, Abbot said:

Hello,

Can grass LOD be generated for Enderal Special Edition? If yes, which are the recommended settings for the grass?

From https://dyndolod.info/Help/Grass-LOD
"Grass LOD is currently only supported for Skyrim Special Edition and Enderal SE."

The defaults are the recommended settings. That does not mean they are the best for your load order and setup.

[DankTemplar]

Newest version of Dyndolod 3 alpha has solved my "out of memory issues" so far. Whatever you did Sheshon, it worked! Thanks for the update!