DynDOLOD 3.00 Alpha 196

[Vyse458]

Hello I have a problem with my LOD with both a vanilla game and using LODgen. The LOD doesn't change assets until I'm very fairly close. Made sure ugrids was at 5. This happens on a completely vanilla fallout 4 not sure what the issue is 

 

Rtx 2080ti 

I7 8700k 

16g ram 

M.2 SSD 

[sheson]

7 hours ago, Vyse458 said:

Hello I have a problem with my LOD with both a vanilla game and using LODgen. The LOD doesn't change assets until I'm very fairly close. Made sure ugrids was at 5. This happens on a completely vanilla fallout 4 not sure what the issue is 

 

Rtx 2080ti 

I7 8700k 

16g ram 

M.2 SSD 

The LOD area starts beyond the active cells, the uGridsToLoad. Large objects that have their origin outside the active cells may span across cell borders. That is how the engine always worked as you already found out by verifying with the vanilla settings and game.

[Vyse458]

Thats just how it is? Its so Jarring even with ultra Everything.

 

Theres picture of my char standing on the rock beyond the bridge

 

Fo4lodgen Makes the LOD better for sure but its still jarring.

Besides increasing ugridstoload is there anything else that can be done? I've already maxed out everything with bethini.

Edited September 10, 2021 by Vyse458

[sheson]

1 hour ago, Vyse458 said:

Thats just how it is? Its so Jarring even with ultra Everything.

 

Theres picture of my char standing on the rock beyond the bridge

 

Fo4lodgen Makes the LOD better for sure but its still jarring.

Besides increasing ugridstoload is there anything else that can be done? I've already maxed out everything with bethini.

 

The LOD area starts beyond the active cells, the uGridsToLoad area. To show full models (like clouds) in that area, the references need to be persistent and have the Is Full LOD flag set. Obviously this can not be done for too many things for performance reasons.

I suggest to create/install higher quality LOD models/textures. AFAIK there are a couple mods for FO4 that do just that.

[TheDude]

12 hours ago, sheson said:

Why would you save between tests and then load that save for the next test when testing mods?

For quick LOD testing, simply coc whiterun form main menu.

Or keep loading  the same save that was cleaned or never saw DynDOLOD output before.

True, thats even better! Will use "coc location" next time! Thanks!

[backudog]

Im new to using DYNDOLOD, but its been working fine so far, but I just changed a texture mod overhaul type thingy for Whiterun that came with a wip lods (the only thing i've changed or added) TEXGEN ran fine, but when i try to run DYNDOLOD it gets so far and then this pops up 

[Window Title]
DynDOLOD

[Main Instruction]
Can not resolve large reference in Skyrim.esm for cell [49,-13] in Reference #12 for Skyrim.esm SkuldafnWorld "Skuldafn" [WRLD:000278DD]

[Content]

Help for this message

FIX THE ERROR as explained in the help OR PERMANENTLY REMOVE THE BROKEN PLUGIN.
Ignore wrong "advice" to only temporarily disable plugins.
Do not try to circumvent the error message, FIX THE ERROR instead.

[Exit DynDOLOD]

[Footer]
DynDOLOD FAQ | Support Forum | Copy message to clipboard

 

I don't know what any of that means, so not sure what i have to replace or fix? the help didn't really..er..help, so can anyone point me in the right direction please?

[sheson]

25 minutes ago, backudog said:

Im new to using DYNDOLOD, but its been working fine so far, but I just changed a texture mod overhaul type thingy for Whiterun that came with a wip lods (the only thing i've changed or added) TEXGEN ran fine, but when i try to run DYNDOLOD it gets so far and then this pops up 

[Window Title]
DynDOLOD

[Main Instruction]
Can not resolve large reference in Skyrim.esm for cell [49,-13] in Reference #12 for Skyrim.esm SkuldafnWorld "Skuldafn" [WRLD:000278DD]

[Content]

Help for this message

FIX THE ERROR as explained in the help OR PERMANENTLY REMOVE THE BROKEN PLUGIN.
Ignore wrong "advice" to only temporarily disable plugins.
Do not try to circumvent the error message, FIX THE ERROR instead.

[Exit DynDOLOD]

[Footer]
DynDOLOD FAQ | Support Forum | Copy message to clipboard

 

I don't know what any of that means, so not sure what i have to replace or fix? the help didn't really..er..help, so can anyone point me in the right direction please?

You are participating in the DynDOLOD 3 alpha test.

Read the first post. Pay attention to the part In case of error messages, click "Help for this message" if available, which will open ..\DynDOLOD\docs\help\Unresolved.html. Read that help file.

There might be an edited/corrupt Skyrim.esm in the load order. Verifying the game files in Steam might help restoring the plugin.

In case further help to solve the issue is needed, read the first post what log files to upload when making posts.

[Mirx]

Hi, i've just tested the latest version of DynDOLOD (40) with the new version of DynDOLOD Resources SE(12) and im getting this error, and i don't know what to do

[sheson]

1 hour ago, Mirx said:

Hi, i've just tested the latest version of DynDOLOD (40) with the new version of DynDOLOD Resources SE(12) and im getting this error, and i don't know what to do

 

Read the first post which log files to include when making post.

Do not make screenshots of text. Use Copy message to clipboard and paste the message instead.

Edit: I was able to replicate. Will post a new version ASAP.

[Sovn]

Hi. I have one of those Unresolved FormIDs errors when generating DynDOLOD.
The problem is that I don't have any error in my Load Order; I am a Wabbajack Modlist developper and thus have a Method Patched list that I carefully update.
Today I updated DynDOLOD and it flagged new mods that it didnt flag before as "Broken", and they come as is, I did not modify them.
The detected mods are:

- Away - Come Away

- G.R.I.M

I didn't try to go further to solve them as I have no wish to do so, those mods work as is, scripts are the only thing I do not touch in Skyrim Modding, I won't start now because you tell me to fix mods.

I don't know what kind of reasoning is behind the choice of gatekeeping users from your tool, like, cool you make one of the niftiest tools on SE Nexus, but that doesn't allow you to judge what mods are and aren't "broken".
I cannot simply toggle them off because they're required for my patches which are required for a correct Lod Generation.

I'd love it to be removed, maybe have warnings for broken mods if you really want to help users. Atleast a flag like xEdit's "-IKnowWhatImDoing" which would bypass that flag; would be of use.
I am completely speachless of this decision.

[sheson]

29 minutes ago, Sovn said:

Hi. I have one of those Unresolved FormIDs errors when generating DynDOLOD.
The problem is that I don't have any error in my Load Order; I am a Wabbajack Modlist developper and thus have a Method Patched list that I carefully update.
Today I updated DynDOLOD and it flagged new mods that it didnt flag before as "Broken", and they come as is, I did not modify them.
The detected mods are:

- Away - Come Away

- G.R.I.M

I didn't try to go further to solve them as I have no wish to do so, those mods work as is, scripts are the only thing I do not touch in Skyrim Modding, I won't start now because you tell me to fix mods.

I don't know what kind of reasoning is behind the choice of gatekeeping users from your tool, like, cool you make one of the niftiest tools on SE Nexus, but that doesn't allow you to judge what mods are and aren't "broken".
I cannot simply toggle them off because they're required for my patches which are required for a correct Lod Generation.

I'd love it to be removed, maybe have warnings for broken mods if you really want to help users. Atleast a flag like xEdit's "-IKnowWhatImDoing" which would bypass that flag; would be of use.
I am completely speachless of this decision.

Unresolved Form ID is an error reported by the xEdit error check.
Such errors prevent the DynDOLOD process from working as intended. Also, unresolved form IDs can cause CTD or other errors in the game or mean things are not working as intended.

If you believe the xEdit error check is making wrong reports about errors, I suggest to make a bug report on the xEdit discord.

If you believe DynDOLOD is making a wrong error report, see the first post what logfile to include when making posts.

If you need help fixing errors in plugins or the load order, see the first post what logfiles to include when making posts and ask qualified questions about it.

https://stepmodifications.org/forum/topic/15606-dyndolod-300-alpha-40/?do=findComment&comment=249961

[Sovn]

22 minutes ago, sheson said:

Unresolved Form ID is an error reported by the xEdit error check.
Such errors prevent the DynDOLOD process from working as intended. Also, unresolved form IDs can cause CTD or other errors in the game or mean things are not working as intended.

If you believe the xEdit error check is making wrong reports about errors, I suggest to make a bug report on the xEdit discord.

If you believe DynDOLOD is making a wrong error report, see the first post what logfile to include when making posts.

If you need help fixing errors in plugins or the load order, see the first post what logfiles to include when making posts and ask qualified questions about it.

https://stepmodifications.org/forum/topic/15606-dyndolod-300-alpha-40/?do=findComment&comment=249961

I do not believe any of the tools used is making a mistake by reporting the error. I am syaing the error is not the end of the world.
Those mods work; countless users have done them an uncountable amount of time. They've been in my Load Order forever. Heck, even the vanilla esms have countless errors, and cleaning esms is still a debatable topic in the community.
I am not saying the reports are wrong; I just want the ability to ignore them, because they should be ignored. (Also all the ones I found are on activators, which to my understanding do not interfere with DynDOLOD to run)

I do not need help to solve those errors, I already solved many, many bugs in my list as I am a modlist developper for Wabbajack.

Edited September 11, 2021 by Sovn

[sheson]

37 minutes ago, Sovn said:

I do not believe any of the tools used is making a mistake by reporting the error. I am syaing the error is not the end of the world.
Those mods work; countless users have done them an uncountable amount of time. They've been in my Load Order forever. Heck, even the vanilla esms have countless errors, and cleaning esms is still a debatable topic in the community.
I am not saying the reports are wrong; I just want the ability to ignore them, because they should be ignored. (Also all the ones I found are on activators, which to my understanding do not interfere with DynDOLOD to run)

I do not need help to solve those errors, I already solved many, many bugs in my list as I am a modlist developper for Wabbajack.

Great. Seems everything is working as it is supposed to be then.

[Sovn]

21 minutes ago, sheson said:

Great. Seems everything is working as it is supposed to be then.

Very sad to see a prominent tool dev simply ignoring people's concerns.

I'm totally not recommending you to implement a similar "if error detected, ask to ignore Yes/No"; something to bypass the error, something I can tell you've already implemented for another piece of your software but it's good to decide which mods are usable with your tool or not.
 

[BuddyKidd]

In version Alpha 41 I notice that there is not a Preset folder and it seems like there are other files missing. Is that correct?