Jump to content

DynDOLOD 3.00 Alpha 173


sheson

Recommended Posts

2 hours ago, mooit said:

I did test with default INI. Hmm HITMEs how do you fix them and what sort of problem are they causing?

I meant the SSE Wiki, for new xLODGen, TexGen, DynDOLOD screen shots.

Step Skyrim Special Edition Guide (stepmodifications.org)

The BTO between Alpha 95 & 97, look about the same, but maybe to make things simpler, here's the output archives.

1. xLODGen Output (mediafire.com)

2. TexGen Output (mediafire.com)

3. DynDOLOD Output (mediafire.com)

THANKS

P.S. Alpha97 doesn't like me... LOL 

Is there anything preventing you from reading this https://dyndolod.info/Messages/Internal-File-FormID-Is-A-HITME?

If you want to provide  information which settings you used, then provide the actual settings you used. I have no connection to third party wikis, guides or information nor do I know what they contain.

If you compared/checked a couple BTO containing the expected object LOD, then there is no need to upload the DynDOLOD output. The object LOD meshes and textures work fine:

test.jpg

The problem is then not with the output files itself. Either the output is not installed, the game does not load the object LOD meshes or does not show them. Those reasons are not directly connected to DynDOLOD / LOD generation.

The known things to do that are short LOD distances or maybe DLL plugins like the Season of Skyrim. Maybe the LOD files are too large for your game setup and the game has resource issue loading them, though in that case I would rather crashes. If it is none of that, I suggest to double check the mod manager and or file access issues.

Your screenshot did not show any problems with terrain LOD so there is no need to check or upload terrain LOD meshes.
You did not report TexGen errors and there weren't any errors in the DynDOLOD log about missing TexGen output or LOD textures. You screenshot does not show missing texture. There is no need check or upload the TexGen.

Link to comment
Share on other sites

7 hours ago, mooit said:

I did test with default INI. Hmm HITMEs how do you fix them and what sort of problem are they causing?

I meant the SSE Wiki, for new xLODGen, TexGen, DynDOLOD screen shots.

Step Skyrim Special Edition Guide (stepmodifications.org)

The BTO between Alpha 95 & 97, look about the same, but maybe to make things simpler, here's the output archives.

1. xLODGen Output (mediafire.com)

2. TexGen Output (mediafire.com)

3. DynDOLOD Output (mediafire.com)

THANKS

P.S. Alpha97 doesn't like me... LOL 

The Step guide (wiki) settings are specific to the Step mod list and will not necessarily be optimal for your mod list. DynDOLOD's defaults are based on optimization against vanilla (the 'standard'). This wouldn't cause missing LOD grass/trees though. I just wanted to clarify that the 'wiki' visual settings are not the vanilla standards shipping with the DynDOLOD configs.

Make sure your grass cache is actually GID and not CGID, and ensure that you are ticking 'Ultra' for trees. Otherwise, you may be using traditional tree LOD with fTreeLoadDistance=0 in skyrimPrefs INI

EDIT: but your screens show that you are not even generating mountain LOD, so you should check the reasons sheson stated and possibly your DynDOLOD output (plugins enabled, asset conflicts)

Link to comment
Share on other sites

I'm not sure what happened during my lod generation, but trees added by Blubbos Pine tree replacer have MASSIVE floating lod, and I have no idea what caused it. I ran Dyndolod again and it still happened :( Worst case scenario, is there anyway of removing just that lod file without running dyndolod again?

20220916134051_1.jpg

Edited by Squonkalicious
Link to comment
Share on other sites

49 minutes ago, Squonkalicious said:

I'm not sure what happened during my lod generation, but trees added by Blubbos Pine tree replacer have MASSIVE floating lod, and I have no idea what caused it. I ran Dyndolod again and it still happened :( Worst case scenario, is there anyway of removing just that lod file without running dyndolod again?

20220916134051_1.jpg

Looks like 'blank' trunk textures

Link to comment
Share on other sites

1 hour ago, Squonkalicious said:

I'm not sure what happened during my lod generation, but trees added by Blubbos Pine tree replacer have MASSIVE floating lod, and I have no idea what caused it. I ran Dyndolod again and it still happened :( Worst case scenario, is there anyway of removing just that lod file without running dyndolod again?

20220916134051_1.jpg

What DynDOLOD version are you using?

LOD can only be added for references that exist. LOD is generated with the LOD assets found in the load order.

Link to comment
Share on other sites

41 minutes ago, Squonkalicious said:

https://ufile.io/3qfnrvph Log file.
and one of the trees. it appears to actually be the blubbos tree addon for daves trees.

20220916195406_1.jpg

Read the first post which debug log to also uploaded when making posts.

Provide links to the involved mods and mention which different download or install option were selected if they exist.

Link to comment
Share on other sites

42 minutes ago, sheson said:

Read the first post which debug log to also uploaded when making posts.

Provide links to the involved mods and mention which different download or install option were selected if they exist.

i dont have a bugreport.txt or a debug_log.txt :(
here is the link for the mod though, both files. https://www.nexusmods.com/skyrimspecialedition/mods/70462

Link to comment
Share on other sites

43 minutes ago, Squonkalicious said:

i dont have a bugreport.txt or a debug_log.txt :(
here is the link for the mod though, both files. https://www.nexusmods.com/skyrimspecialedition/mods/70462

The debug log is saved right after the log is appended to the normal log file. Are sure there is none? Did the last session complete successfully and was there no error when saving/closing?

Did you remove all the third party billboards and generated them with TexGen instead?  https://dyndolod.info/Generation-Instructions#Prerequisites and https://dyndolod.info/Help/Tree-Grass-LOD-Billboards#3rd-Party-LOD-Billboards

You should clean plugins with deleted reference as explained in the summary and https://dyndolod.info/Messages/Deleted-Reference

Link to comment
Share on other sites

40 minutes ago, sheson said:

The debug log is saved right after the log is appended to the normal log file. Are sure there is none? Did the last session complete successfully and was there no error when saving/closing?

Did you remove all the third party billboards and generated them with TexGen instead?  https://dyndolod.info/Generation-Instructions#Prerequisites and https://dyndolod.info/Help/Tree-Grass-LOD-Billboards#3rd-Party-LOD-Billboards

You should clean plugins with deleted reference as explained in the summary and https://dyndolod.info/Messages/Deleted-Reference

Yeah, the last generation was successful and the one that is in there is from a failed one when i had a weird plugin (which i removed from my load order.)

I cleaned all my plugins before, but I didnt remove the third party billboards, so I will try that.

Link to comment
Share on other sites

37 minutes ago, Squonkalicious said:

Yeah, the last generation was successful and the one that is in there is from a failed one when i had a weird plugin (which i removed from my load order.)

I cleaned all my plugins before, but I didnt remove the third party billboards, so I will try that.

Did you generate standard or ultra tree LOD?

If problem persists after that generation, upload new log and debug log (it really should be there)  and also ..\DynDOLOD\Logs\DynDOLOD_SSE_Tree_Report.txt and ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.