DynDOLOD 3.00 Alpha 182

[BISOM]

2 hours ago, sheson said:

Upload the debug log for that please. Doublecheck if there is a bugreport.txt in the same folder as DynDOLOD.exe.

Check if there is a zip file in ..\DynDOLOD\Edit Scripts\Export\*.zip

 

Sure, will upload tmrw

[semithicc]

10 hours ago, sheson said:

The is the terrain underside mesh. Increase object/terrain LOD distances and/or lower the underside mesh, so it does not peak through.

https://dyndolod.info/Help/Terrain-Underside#Troubleshooting

I tried all of the above and nothing changed. The only thing that fixes the problem is disabling the terrain underside mesh completely, which I don't really want to do since I enjoy using EVLaS. 

[z929669]

17 minutes ago, semithicc said:

I tried all of the above and nothing changed. The only thing that fixes the problem is disabling the terrain underside mesh completely, which I don't really want to do since I enjoy using EVLaS. 

I'm guessing this is more related to DynDOLOD rather than xLODGen, no? DynDOLOD generates the terrain underside, AFAIK.

Just to rule out a wild goose ...

Be sure you aren't running a mod that provides the underside mesh (like EVLaS, I think), so that the DynDOLOD version is all that is installed in your mod list at very high priority in your mod manager.

If you use the default terrain height (500, I think), there should be no issues unless you are running landscape/terrain mods that deviate a lot from vanilla.

[semithicc]

12 minutes ago, z929669 said:

I'm guessing this is more related to DynDOLOD rather than xLODGen, no? DynDOLOD generates the terrain underside, AFAIK.

Just to rule out a wild goose ...

Be sure you aren't running a mod that provides the underside mesh (like EVLaS, I think), so that the DynDOLOD version is all that is installed in your mod list at very high priority in your mod manager.

If you use the default terrain height (500, I think), there should be no issues unless you are running landscape/terrain mods that deviate a lot from vanilla.

I'm using EVLaS without the included terrain underside, generating my own underside with DynDOLOD. However, no matter what settings I try regarding the quality or height of the underside, it still peeks through my mountain textures. I do use Majestic Mountains, but DynDOLOD should account for that when generating terrain underside, no?

[sheson]

51 minutes ago, semithicc said:

I tried all of the above and nothing changed. The only thing that fixes the problem is disabling the terrain underside mesh completely, which I don't really want to do since I enjoy using EVLaS. 

Moved to the DynDOLOD 3 alpha forum.

Read the first post which log and debug log to upload.

What are the LOD distance values? Provide a screenshot of the DynDOLOD SkyUI MCM Settings page.

if you change the height in the advanced settings it should directly affect the z value of the reference that adds the underside mesh in the DynDOLOD plugin.

Use xEdit to change the z position manually without having to run DynDOLOD / underside only generation.

[semithicc]

21 minutes ago, sheson said:

Moved to the DynDOLOD 3 alpha forum.

Read the first post which log and debug log to upload.

What are the LOD distance values? Provide a screenshot of the DynDOLOD SkyUI MCM Settings page.

if you change the height in the advanced settings it should directly affect the z value of the reference that adds the underside mesh in the DynDOLOD plugin.

Use xEdit to change the z position manually without having to run DynDOLOD / underside only generation.

Sorry, here's the log and a screenshot of my settings.

https://ufile.io/wyeyj6c7

https://imgur.com/a/M7JbLZE

I'm afraid I'm not experienced with using xEdit so some more detailed instructions would be greatly appreciated. 

[fractalbase]

I get a "Range Check Error" exception with TexGen.

logs: https://drive.google.com/drive/folders/18jUb4MPFhPKAO3SvEwKO7Eb4SkYLvoyl?usp=share_link

[sheson]

10 hours ago, semithicc said:

Sorry, here's the log and a screenshot of my settings.

https://ufile.io/wyeyj6c7

https://imgur.com/a/M7JbLZE

I'm afraid I'm not experienced with using xEdit so some more detailed instructions would be greatly appreciated. 

You have tried increasing the fSplitDistantMult to 1.5 or 2?

Open DynDOLOD.esp in xEdit.

In the left tree view, unfold DynDOLOD.esp, unfold Worldspace, unfold 00000003C Tamriel, unfold 00000D74 Cell, unfold Persistent.
Click on the column header FormID to flip its sort order.
The terrain underside reference should be first record now.

Click it in the left tree view to shows its data in the right window. Scroll the right window down to the bottom and unfold the DATA - Position/Rotation.
Double click or right click the value in the row Position / Z in order to edit it.

Close xEdit to save. If there is a problem with renaming, find the saved plugin in MO2 Overwrite folder and rename the filename manually.

[sheson]

3 hours ago, fractalbase said:

I get a "Range Check Error" exception with TexGen.

logs: https://drive.google.com/drive/folders/18jUb4MPFhPKAO3SvEwKO7Eb4SkYLvoyl?usp=share_link

Always use the latest alpha version. Do not waste time using older versions or reporting problems with older versions
and
Use search to find similar questions and answers
as explained on the first post.

The problem was already reported, discussed and fixed in the latest alpha version.

https://dyndolod.info/Changelog
Version 3.00 Alpha 106
TexGen.exe/DynDOLOD.exe - fixed an out of range error because of undefined worldspace bounds

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

[cat210803]

Trying to use DyndoLOD through MO2. When I run it, and after pressing the high option, I get countless warnings and errors. I've attached the log below.

I aleady used texgen and installed the output. I don't know what I have done wrong. Please help.

DYNDOLOD Log.txt

[sheson]

2 hours ago, cat210803 said:

Trying to use DyndoLOD through MO2. When I run it, and after pressing the high option, I get countless warnings and errors. I've attached the log below.

I aleady used texgen and installed the output. I don't know what I have done wrong. Please help.

DYNDOLOD Log.txt 1.21 MB · 1 download

Moved to the DynDOLOD 3 Alpha thread. Read the first post which debug log to upload as well.

Read https://dyndolod.info/Messages what a particular message means and what/if something needs to be done about it.
Also read https://dyndolod.info/Help/Summary-Of-Messages, which groups similar messages to show them with their explanations to make it easier to check and learn about them.

For example see https://dyndolod.info/Messages/Overwritten-Large-Reference and click through to https://dyndolod.info/Help/Large-References to learn about large reference bugs.

https://dyndolod.info/Mods/Beyond-Skyrim-Bruma
File not found errors are because not all required assets for LOD generation ship with the mod.

https://dyndolod.info/Messages/Max-Tree-LOD-Billboard-Count-Of-256-On-Atlas-Exceeded
You might have installed third party billboards that add billboards for small bushes and shrups that typically do not have LOD. See https://dyndolod.info/Help/Tree-Grass-LOD-Billboards#3rd-Party-LOD-Billboards

https://dyndolod.info/Generation-Instructions#Prerequisites
Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean

If you require help with a specific message, problem or mod then ask a specific question.

[fractalbase]

I downloaded latest DynDOLOD and extracted to a new folder.

TexGen ran successfully.

I ran DynDOLOD and ran into an exception: "LODGenx64Win.exe failed to generate object LOD for one or more worlds."

logs: https://drive.google.com/drive/folders/1JNr5YFDXWJdw8BglcvptNWqr0t6Y8Lle?usp=share_link

[sheson]

45 minutes ago, fractalbase said:

I downloaded latest DynDOLOD and extracted to a new folder.

TexGen ran successfully.

I ran DynDOLOD and ran into an exception: "LODGenx64Win.exe failed to generate object LOD for one or more worlds."

logs: https://drive.google.com/drive/folders/1JNr5YFDXWJdw8BglcvptNWqr0t6Y8Lle?usp=share_link

I might be blind but the link does not seem to contain the DynDOLOD log and debug log.

The log would say exactly which LODGen log shows the issue. If you check LODGen_SSE_DLC2SolstheimWorld_WIN_log.txt or LODGen_SSE_Tamriel_WIN_log.txt yourself as explained, the error message seems to be self explanatory. For example:

Error writing D:\Tools\DynDOLOD\DynDOLOD_Output\Meshes\Terrain\DLC2SolstheimWorld\Objects\\DLC2SolstheimWorld.4.-36.-12.WIN.bto There is not enough space on the disk.

[Saint_Chewy]

On 11/12/2022 at 6:44 AM, sheson said:

I have two different ESM to test to see if this can be still narrowed down to something more concrete. One is 963kb (9860099 bytes) while the other is 929kb (951422 bytes).

Let me know if either makes a difference or not.

Test the plugins with that second to last papyrus test script the last toml where things happen later than "usual".

DynDOLOD.esm DynDOLOD.esm

Hi Sheson thank you for this new test.

I tried just using the two provided DynDOLOD.esm files with the default script and .toml and unfortunately there was no change there.

I then tried with the second to last SHESON_DynDOLOD_Worshipper.pex you gave me earlier and also the last .toml and that was also identical in my testing where my stutter is delayed and starts at Riften. This happens with both of those provided DynDOLOD.esm files.

I apologize for the bad news here. Thank you again for your help.

 

[fractalbase]

49 minutes ago, sheson said:

I might be blind but the link does not seem to contain the DynDOLOD log and debug log.

The log would say exactly which LODGen log shows the issue. If you check LODGen_SSE_DLC2SolstheimWorld_WIN_log.txt or LODGen_SSE_Tamriel_WIN_log.txt yourself as explained, the error message seems to be self explanatory. For example:

Error writing D:\Tools\DynDOLOD\DynDOLOD_Output\Meshes\Terrain\DLC2SolstheimWorld\Objects\\DLC2SolstheimWorld.4.-36.-12.WIN.bto There is not enough space on the disk.

thank you.

I hadn't exited DynDOLOD yet which is probably why I didn't find those two particular log files initially.