Jump to content

DynDOLOD 3.00 Alpha 169


sheson

Recommended Posts

 

5 hours ago, sheson said:

Pay attention to log message https://dyndolod.info/Messages and the summary https://dyndolod.info/Help/Summary-Of-Messages

In this case the issue is probably caused by several plugins adding the same new cells:

[00:48] <Warning: Potentially wild edit cell JKs Skyrim.esp [CELL:27023913] (in RiftenWorld "Riften" [WRLD:00016BB4] at -1,-1)>
[00:48] <Warning: Potentially wild edit cell RLO - Exteriors.esp [CELL:390116D5] (in RiftenWorld "Riften" [WRLD:00016BB4] at -1,-1)>
See https://dyndolod.info/Messages/Potentially-Wild-Edit-Cell

[00:48] <Warning: Duplicate Cell at -1,-1 in JKs Skyrim.esp [CELL:27023913] (in RiftenWorld "Riften" [WRLD:00016BB4] at -1,-1) and RLO - Exteriors.esp [CELL:390116D5] (in RiftenWorld "Riften" [WRLD:00016BB4] at -1,-1)>
See https://dyndolod.info/Messages/Duplicate-Cell

Riften is not near the center of the map, so there is most likely no real reason for any plugin to add new cells at -1,-1 for it.
The cell records can/should probably be removed with xEdit for example.

https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD
Pay attention to all log messages. It should end with the log message 'DynDOLOD plugins generated successfully' and lines like 'LODGen generated object LOD for [WORLDSPACE] successfully' for each selected worldspace. Do not use the output if there were errors that stopped the process prematurely.

https://dyndolod.info/Messages/File-Not-Found-Textures
In case a texture is not found while running TexGen, it will be substituted with the default diffuse (full red color) for *.DDS or the default normal map (flat surface) for *_n.DDS automatically. The first should be very obvious in case the generated object LOD texture or LOD billboard is used in the game and typically needs to be fixed. The flat normal map substitute means the surface of the object will be flat, which might not be a very visible problem if at all.

If the trees / billboards are not used in the game / for LOD generation, then you won't see any visual issues.

well, I've deleted cell -1,-1 and 0,1 (or another which was in specified error that broke the process) and LODs are generated successfully, but there're still those stupid lights image.thumb.png.80c68a0564d3f1c47f733e43f9ac86ae.png

Link to comment
Share on other sites

16 hours ago, darikzen said:

well, I've deleted cell -1,-1 and 0,1 (or another which was in specified error that broke the process) and LODs are generated successfully, but there're still those stupid lights 

Read the first post which log and debug log to upload when making posts to accompany meaningful screenshots.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make meaningful screenshots with additional information by opening the console and clicking the object in question (best with More Informative Console installed).

Link to comment
Share on other sites

19 hours ago, Blackread said:

The HearthFires building should not be there, I was straight out of the alternate start room. I ran from Honningbrew Meadery along the east side of Whiterun to the whitewatch tower, where I first noticed the misplaced building. It is fully replicable on that LOD generation (I haven't successfully completed another one yet). I hadn't altered my speed mult, it was vanilla (or very close to it at least).

Edit: Forgot to mention, nothing in Papyrus logs.

Edit2: Did another DynDOLOD run without Occlusion just to see if the HearthFires building is still there, and it looks like it is. Logs Seems it is replicable at least on this mod list. Still nothing in Papyrus logs. I'll root out the memory issues when I have the time.

Check before generating LOD if any plugin overwrites 03010F54  or the enable parent 03016DF1.

The  Lux Orbis - Master plugin.esm overwrite of 03010F54 should be fine if it is only adding the BYOHHouse3Location

If there is nothing else overwriting / patched, let me know the new form id of the LOD reference in the DynDOLOD plugin and upload ..\skse\plugins\DynDOLOD_Data\DynDOLOD_Tamriel_Objects.txt from the output.

Link to comment
Share on other sites

Hey again, sheson...I just ran alpha 100 with the large reference bug workaround and when I went to start my game I got a message "dyndolod dll papyrus scripts are the wrong version."  However I use 1.5.97 and have been using the same scripts and dll since I've been running dyndolod 3.0.

 

Ah ok now I'm reading the effin manual I see the latest scripts are needed...trying again, sorry.

Edited by MisterMorden
Link to comment
Share on other sites

When running TexGen and creating textures I'm getting the following error with Skyrim VR:

Error: File not found textures\effects\FXWhiteWater02_falls.dds.

Could be that period on the end of the filename

Edited by benhollio
Link to comment
Share on other sites

2 hours ago, benhollio said:

When running TexGen and creating textures I'm getting the following error with Skyrim VR:

Error: File not found textures\effects\FXWhiteWater02_falls.dds.

Could be that period on the end of the filename

Read the first post which log and debug log to upload when making posts.

As explained, read https://dyndolod.info/Messages -> https://dyndolod.info/Messages/File-Not-Found-Textures for explanations of log messages and/or read the https://dyndolod.info/Help/Summary-Of-Messages.

It is not the period that is added at the end of a sentence. The texture is part of the core files of Realistic Water Two and is missing while the RealisticWaterTwo.esp is installed.

Link to comment
Share on other sites

I am still testing, but I mostly have the configs for the vanilla stitched object LOD textures complete for Fallout 4.

However, I did notice an issue with a very popular mod in my list that causes the output to contain a bad texture. FlaconOil's Complete Retexture Project erroneously includes a few textures in sRGB instead of linear, and while it doesn't appear to cause apparent artifacts in game, it causes the generated LOD texture to be incorrect. Specifically, the textures\architecture\diamondcity\corrugatedmetal02_d.dds inside the FlaconOil - BA2 2K - Part3 file is saved as DXGI_FORMAT_BC1_UNORM_SRGB.

Perhaps a warning could be added for when an input texture is in sRGB instead of linear? Or perhaps it could convert to linear upon generation?

I will also try to reach out to the mod author so they can hopefully correct this oversight.

Included are the logs, the configs, and the output incorrect texture. https://mega.nz/file/pY4l1RLb#J3mIXjYuONKJ9zSSfVzqXNtfcaTxqWYqV6KkH9LOpZ0

Link to comment
Share on other sites

On 10/1/2022 at 5:44 PM, sheson said:

Check before generating LOD if any plugin overwrites 03010F54  or the enable parent 03016DF1.

The  Lux Orbis - Master plugin.esm overwrite of 03010F54 should be fine if it is only adding the BYOHHouse3Location

If there is nothing else overwriting / patched, let me know the new form id of the LOD reference in the DynDOLOD plugin and upload ..\skse\plugins\DynDOLOD_Data\DynDOLOD_Tamriel_Objects.txt from the output.

Updating to Alpha 100 seems to have solved the memory issues, at least I didn't get any Out of memory errors during my latest run.

03010F54  is overwritten by Lux Orbis - Master plugin.esm only, it changes the emittance in addition to adding the location value.

03016DF1 is overwritten by Lux.esp, it adds an emittance value and a location value.

The form IDs of the LOD reference are 380A258F (base, DynDOLOD.esm) and 6E67B45B (ref, DynDOLOD.esp), assuming this is what you meant https://i.imgur.com/E3EWJyH.png

DynDOLOD_Tamriel_Objects.txt from the output

Logs in case they are needed

Edited by Blackread
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.