DynDOLOD 3.00 Alpha 198

[sheson]

2 hours ago, BISOM said:

1) 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?

I can scroll and move every windows, even write on it. Task manager looks like this. there's no prmpt.

2) 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?

It runs normaly, promt show up ask me to exit, check log or restart. 

 

 

3)See what happens if you do not select to generate Occlusion

after unchecked occlusion, running time faster, but still no prompt.

The task manager shows DynDOLOD working and two LODGen still running as well. DynDOLOD is waiting for them to finish. Open up the LODGen windows to see what they are working on.

[Lageron]

8 hours ago, xcal68 said:

You recently install Skyrim Extended Cut - Saints and Seducers?  It happens to me, too, but only with that mod enabled.  I tested with only that mod enabled, too.

Edit - Addressed here: 

 

I did, and i did as they said earlier! Thank you so much for pointing it out, this made texgen carry through with it ^_^

[BISOM]

3 hours ago, sheson said:

The task manager shows DynDOLOD working and two LODGen still running as well. DynDOLOD is waiting for them to finish. Open up the LODGen windows to see what they are working on.

testing alpha106, still no prompt showing up

1) after everything done. window and task manager looks like this.

2) alpha106 debug report is here...if it can help.

3) maybe it is win11 problem? cuz i am currently lastest version of win11 and nvida game driver.

 

[sheson]

2 hours ago, BISOM said:

testing alpha106, still no prompt showing up

1) after everything done. window and task manager looks like this.

2) alpha106 debug report is here...if it can help.

3) maybe it is win11 problem? cuz i am currently lastest version of win11 and nvida game driver.

 

It is normal that you can enter text into the messages tab of xEdit/DynDOLOD.

As far as I can tell you are using the normal release version of Windows 11 and not some beta/preview, so it is most likely not the problem.

Check if there is a bugreport.txt in the same folder as the DynDOLOD exe.

Add the command line argument -autoexit to the arguments starting DynDOLOD to see if it automatically saves and zips without waiting for the prompt/input.

[sheson]

On 11/7/2022 at 8:32 PM, Saint_Chewy said:

I tried the provided .toml and this one also just delays the stutter for me where its right outside of Riften.

I also tested with the default .ini files without the custom .ini over the weekend and there was no change with that either. I tried without using BethINI just straight from the launcher and still stuttered. I had completely reinstalled Skyrim and also moved it to another SSD just as a test and unfortunately I received the same results.

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

[BISOM]

17 minutes ago, sheson said:

It is normal that you can enter text into the messages tab of xEdit/DynDOLOD.

As far as I can tell you are using the normal release version of Windows 11 and not some beta/preview, so it is most likely not the problem.

Check if there is a bugreport.txt in the same folder as the DynDOLOD exe.

Add the command line argument -autoexit to the arguments starting DynDOLOD to see if it automatically saves and zips without waiting for the prompt/input.

1) Add the command line argument -autoexit to the arguments starting DynDOLOD to see if it automatically saves and zips without waiting for the prompt/input.

 

It worked! esp and esm has appeared in output folder, i can just zip all folder and extract in mo2.

though the program didn't auto closed, it just freeze like it used to do, need to alt+f4 to force close.(have wait 15 mimutes already, show no reponsing.)

just let you know.

 

going to test in game, very appreciate.

 

[sheson]

27 minutes ago, BISOM said:

1) Add the command line argument -autoexit to the arguments starting DynDOLOD to see if it automatically saves and zips without waiting for the prompt/input.

 

It worked! esp and esm has appeared in output folder, i can just zip all folder and extract in mo2.

though the program didn't auto closed, it just freeze like it used to do, need to alt+f4 to force close.(have wait 15 mimutes already, show no reponsing.)

just let you know.

 

going to test in game, very appreciate.

 

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

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