DynDOLOD 3.00 Alpha 182

[DoubleYou]

5 hours ago, zhuabaobao said:

hi. I want to ask how to solve this, 
    DynDOLOD  
Warning: Initially disabled large reference in RealisticWaterTwo - Resources.esm [REFR:0700AE48] (places RockPileL02Wet [STAT:00039393] in GRUP Cell Temporary Children of [CELL:000095D7] (in Tamriel "天际" [WRLD:0000003C] at 10,-1))

Update to latest Realistic Water Two I believe should fix this. Otherwise, there really is nothing you can do. 

[sheson]

On 12/23/2021 at 6:41 AM, zhuabaobao said:

hi. I want to ask how to solve this, 
    DynDOLOD  
Warning: Initially disabled large reference in RealisticWaterTwo - Resources.esm [REFR:0700AE48] (places RockPileL02Wet [STAT:00039393] in GRUP Cell Temporary Children of [CELL:000095D7] (in Tamriel "天际" [WRLD:0000003C] at 10,-1))

Read https://dyndolod.info/Messages/Initially-Disabled-Large-Reference

As suggest see https://dyndolod.info/Help/Large-References for further explanations.

If the affected cell has visible z-fighting caused by this large reference being initially disabled, the only solutions are to not initially disable the reference or to move all the large references that have visible z-fighting underground and replace them with new reference that are not large references. Or do not use the large reference system at all by turning it off.

On 12/23/2021 at 11:13 AM, redleviathan said:

Hello, I was using DynDOLOD 3 in SE and love the distance grass. Now that I already upgraded to AE and the mod No Grass In Objects is broken in AE. I want to use DynDOLOD 3 grass LOD in new game. Is there a workaround for grass LOD to be generated?

I am sorry if this question has already asked in the past, if so, I can't find it.

DynDOLOD does not require NGIO, it requires the cgid files to generate grass LOD.

That means, you can use the cgid files generated with NGIO using runtime 1.5.97 to generate Grass LOD with mode 1 with DynDOLOD and use it with runtime 1.6.342 without NGIO running and let the full grass be done as usual by the engine.The position of the LOD and full grass will not match perfectly.

To achieve that, you could rename the all cgid files to just gid and set bAllowCreateGrass=0 and bAllowLoadGrass=1 in the Skyrim INI. However you need to make sure that all vanilla *.gid files from Skyrim - Misc.bsa  are being overwritten, since they are invalid (still in the Skyrim format) and cause visual problems/CTD.

[redleviathan]

I see. Problem is the changes in my load order was significant. I added Bruma mod and big landscape changing mods, this IMO will requires regenerate the cgid files. If somehow I don't use NGIO, is it possible to regenerate the cgid files?

[sheson]

3 hours ago, redleviathan said:

I see. Problem is the changes in my load order was significant. I added Bruma mod and big landscape changing mods, this IMO will requires regenerate the cgid files. If somehow I don't use NGIO, is it possible to regenerate the cgid files?

cgid files were "invented" by NGIO. There is no other tool that generates them at the moment.

[Swifty819]

I see. Are there any recommendations to run or not run specific worldspaces? I'm getting a lot of mesh/similar errors about things like BS Burma (which I expected) and 3DNPC (also expected). I understand those errors have to do with the mods not being LOD ready, rather than a DynDOLOD issue. I'm having trouble understanding whether letting DynDOLOD proceed will cause issues, or if I can just completely ignore all of those and run with whatever DynDOLOD outputs.

I apologize for all of the stupid questions, by the way. It's my first time running DynDOLOD and despite reading all of the documentation and the FAQs I'm still not sure I understand everything it says correctly.

[sheson]

51 minutes ago, Swifty819 said:

I see. Are there any recommendations to run or not run specific worldspaces? I'm getting a lot of mesh/similar errors about things like BS Burma (which I expected) and 3DNPC (also expected). I understand those errors have to do with the mods not being LOD ready, rather than a DynDOLOD issue. I'm having trouble understanding whether letting DynDOLOD proceed will cause issues, or if I can just completely ignore all of those and run with whatever DynDOLOD outputs.

I apologize for all of the stupid questions, by the way. It's my first time running DynDOLOD and despite reading all of the documentation and the FAQs I'm still not sure I understand everything it says correctly.

Read https://dyndolod.info/Help/Wizard-Mode or https://dyndolod.info/Help/Advanced-Mode what it says for the Worldspace check list. DynDOLOD already filters out worldspaces by default.

See https://dyndolod.info/Mods for specific mention of mods, for example https://dyndolod.info/Mods/Beyond-Skyrim-Bruma

Really read the explanations for each message type in the Summary or at https://dyndolod.info/Messages.

"Warning messages inform about issues that should be fixed. If they are ignored there might be visual or game play issues."

"Error messages inform about issues that need to be fixed. If they are ignored the process might not be to complete successfully and/or just like with warnings, there might be visual or game play issues including CTD."

Typically the warning message are either to easily and quickly spot problems with mods or the load order, or to check once a problem is noticed in the game.

As https://dyndolod.info/Generation-Instructions explains, if the processes  "completed successfully" and you saved the plugins, the LOD mod is typically usable then.

[z929669]

16 hours ago, zhuabaobao said:

hi. I want to ask how to solve this, 
    DynDOLOD  
Warning: Initially disabled large reference in RealisticWaterTwo - Resources.esm [REFR:0700AE48] (places RockPileL02Wet [STAT:00039393] in GRUP Cell Temporary Children of [CELL:000095D7] (in Tamriel "天际" [WRLD:0000003C] at 10,-1))

If you are using the latest version of RWT (5.x), there is nothing to fix. This is just a warning to verify you don't see artifacts of the large-reference bug in SSE and that it has been accounted for properly by this plugin (which it is). All such warnings are just that. Most other mod authors haven't made the changes as RWT has made in it's most recent version though.

PS: I rarely see an issue in game for most of these situations, even if they are valid. Sometimes, there are visible issues in game, so having the warnings is a good thing.

[Phlunder]

Hey sheson! I noticed that the Windhelm bridge LOD model (both windhelmbridge_lod.nif and windhelmbridge_lod_1.nif) has a black spot in the latest DynDOLOD Resources 3.00 Alpha 15. The windhelmbridge_lod_2.nif is not affected. A picture of the issue with comparison to the full model:

 

I did notice that this part of the model uses a different texture than the rest of the outer wall, though the issue isn't apparent on the full model or the vanilla LOD model.

Edited December 24, 2021 by Phlunder

[sheson]

7 hours ago, Phlunder said:

Hey sheson! I noticed that the Windhelm bridge LOD model (both windhelmbridge_lod.nif and windhelmbridge_lod_1.nif) has a black spot in the latest DynDOLOD Resources 3.00 Alpha 15. The windhelmbridge_lod_2.nif is not affected. A picture of the issue with comparison to the full model:

 

I did notice that this part of the model uses a different texture than the rest of the outer wall, though the issue isn't apparent on the full model or the vanilla LOD model.

The part in question uses a different texture compared to the main part. The LOD model included in DynDOLOD Resources defines the same textures as the vanilla full model like this since 2017.

In the vanilla full model the part is a decal with an alpha-property (which is not supported by LOD) so it is made to look like the full with the decal applied. It seems the vanilla texture textures\architecture\windhelm\WHruinstonedark.dds for that part is changed with one that has a different alpha channel that makes it so that the decal is barely or not visible in the full model.

Use a different replacement texture with a similar alpha channel to the vanilla texture. Alternatively create a custom LOD model that uses the same texture as the main part. Rename the BSTriShape to Windhelmbridge:2 when doing so. Better yet merge the separate shape with the main part in the custom LOD model.

[Phlunder]

2 hours ago, sheson said:

The part in question uses a different texture compared to the main part. The LOD model included in DynDOLOD Resources defines the same textures as the vanilla full model like this since 2017.

In the vanilla full model the part is a decal with an alpha-property (which is not supported by LOD) so it is made to look like the full with the decal applied. It seems the vanilla texture textures\architecture\windhelm\WHruinstonedark.dds for that part is changed with one that has a different alpha channel that makes it so that the decal is barely or not visible in the full model.

Use a different replacement texture with a similar alpha channel to the vanilla texture. Alternatively create a custom LOD model that uses the same texture as the main part. Rename the BSTriShape to Windhelmbridge:2 when doing so. Better yet merge the separate shape with the main part in the custom LOD model.

Ahh, so it was Noble Skyrim which caused it. Thank you for explaining the issue (that was my own doing) in detail. I already tried to assign the same whoutwall texture to that part, but it was still darker than the adjacent parts. Turns out I had to match the Vertex Colors too! I also renamed the NiTriShape to Windhelmbridge:2 as you suggested. Looks perfect now. Thanks again, and happy holidays to you!

Edited December 24, 2021 by Phlunder

[redleviathan]

20 hours ago, sheson said:

cgid files were "invented" by NGIO. There is no other tool that generates them at the moment.

Ah well, hopefully the mod author found a way to upgrade NGIO.

Thanks!

[Omniguous]

hello. i hope this is the correct place to put this and i searched the other comments for the term `itm` and it came up with no results:

i ran FO4EditQAC on `FO4LODGen-HighTrees.esp` and it resulted in one (1) ITM.

`Removing: TreeMapleForest1 "Maple Tree" [STAT:0004A073]` was the log entry for that ITM.

"dirty" CRC: 0xDC282BF2

"clean" CRC: 0x7203CE8C

FO4Edit version: FO4Edit v4.0.4b

i am wondering if this was intentional, an oversight, etc. (bringing it to your attention, in other words).

 

thank you.

-omni.

[sheson]

7 hours ago, Omniguous said:

hello. i hope this is the correct place to put this and i searched the other comments for the term `itm` and it came up with no results:

i ran FO4EditQAC on `FO4LODGen-HighTrees.esp` and it resulted in one (1) ITM.

`Removing: TreeMapleForest1 "Maple Tree" [STAT:0004A073]` was the log entry for that ITM.

"dirty" CRC: 0xDC282BF2

"clean" CRC: 0x7203CE8C

FO4Edit version: FO4Edit v4.0.4b

i am wondering if this was intentional, an oversight, etc. (bringing it to your attention, in other words).

 

thank you.

-omni.

Looks like the vanilla ESM got updated between 2017 when the FO4LODGen-HighTrees.esp was created and now.

Like any other ITM that should be removed. I will go through the plugins and records to check if there for more changes to the game files happening in the past years.

[Tubb]

Running into an error upon opening Texgen for VR.

 Error: OpenGL: invalid enumerant.

^{TexGen_TES5VR_log.txt}

TexGen_TES5VR_Debug_log.txt

bugreport.txt

[Tubb]

Nevermind, had my iGPU disabled in device manager as I was experimenting with some Oculus stuff and forgot to re-enable.