Jump to content

Recommended Posts

Posted
30 minutes ago, sheson said:

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD log and debug log to upload when making posts.

Errors are not normal...
It is supposed to create those texture if they do not exist. Do they exist in the old DynDOLOD output?

thanks sheson but I did it already and i sent another post regarding fixing it and find the solution, idk but sometimes in this form posts won't persist 

problem was that I was doing this without previous dyndolod generation enabled and with only texgen enabled, my bad.

 

  • 2 weeks later...
Posted (edited)

Hi Sheson, hope you're doing alright! I’m running into a strange issue involving LOOT and/or Vortex, the mod "Water for ENB (Shades of Skyrim)" and my DynDOLOD-output. LOOT keeps detecting "cyclic interactions" between these mods, no matter how I adjust the load order...? Even when I sort everything manually or create specific custom rules, LOOT still reports the same cyclic dependency (see screenshots). This has never happened before and I have generated Dyndolod at least 100 times together with "Water for ENB (Shades of Skyrim)" and the same Load order without this error... 

So, anyway, I hope you can help. All logs, debug files, and my load order can be found here (no bug report was generated): https://limewire.com/d/B27Xk#uPqrussaqH  Cheers!

Edited by TheDude
Posted
8 hours ago, TheDude said:

Hi Sheson, hope you're doing alright! I’m running into a strange issue involving LOOT and/or Vortex, the mod "Water for ENB (Shades of Skyrim)" and my DynDOLOD-output. LOOT keeps detecting "cyclic interactions" between these mods, no matter how I adjust the load order...? Even when I sort everything manually or create specific custom rules, LOOT still reports the same cyclic dependency (see screenshots). This has never happened before and I have generated Dyndolod at least 100 times together with "Water for ENB (Shades of Skyrim)" and the same Load order without this error... 

So, anyway, I hope you can help. All logs, debug files, and my load order can be found here (no bug report was generated): https://limewire.com/d/B27Xk#uPqrussaqH  Cheers!

Upload DynDOLOD.esm and DynDOLODExtender.esp.

Posted (edited)

Hello Sheson,  I met color mismatch between Lod objects and full models. I have read https://dyndolod.info/Mods/Community-Shaders#PBR and change the gamma in Texgen_SSE.ini from 1.3 to 2.2, then the color of dds file looks very close (compare to its non-PBR version), but after regen dyndolod I found it not change at all in game. Then I found dyndolod will convert sRGB to linear too and put textures into DynDOLOD_Output\textures\pbr , I think maybe the're used by LOD objects. But after I change the gamma in DynDOLOD_SSE.ini to 2.2 and rerun dyndolod, I found the texture it generate not changed. (e.g.  \DynDOLOD_Output\textures\pbr\landscape\mountains\mountainslab01linear)

Edited by blueetenicolet
Posted
1 hour ago, blueetenicolet said:

Hello Sheson,  I met color mismatch between Lod objects and full models. I have read https://dyndolod.info/Mods/Community-Shaders#PBR and change the gamma in Texgen_SSE.ini from 1.3 to 2.2, then the color of dds file looks very close (compare to its non-PBR version), but after regen dyndolod I found it not change at all in game. Then I found dyndolod will convert sRGB to linear too and put textures into DynDOLOD_Output\textures\pbr , I think maybe the're used by LOD objects. But after I change the gamma in DynDOLOD_SSE.ini to 2.2 and rerun dyndolod, I found the texture it generate not changed. (e.g.  \DynDOLOD_Output\textures\pbr\landscape\mountains\mountainslab01linear)

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD log and debug log to upload when making posts.

You will have to delete the ..\DynDOLOD_Output\textures\ folder as it will create linear textures again if they already exist in the output or the data folder.

Posted
5 minutes ago, sheson said:

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD log and debug log to upload when making posts.

You will have to delete the ..\DynDOLOD_Output\textures\ folder as it will create linear textures again if they already exist in the output or the data folder.

Sorry for bother, I have tried restart my PC and then seems it works well, Maybe the change to ini file not correctly aplly first time.

Posted
22 hours ago, TheDude said:

Get the test version from https://mega.nz/folder/JdpU1KZB#cYTSPK6NW2CSbGrvQ-w_6A. If the issue persists, upload new logs and DynDOLOD.esm.

A somewhat quicker test run with just Tamriel, object LOD, standard tree LOD and dynamic LOD would be enough.

  • Like 1
Posted
4 hours ago, sheson said:

Get the test version from https://mega.nz/folder/JdpU1KZB#cYTSPK6NW2CSbGrvQ-w_6A. If the issue persists, upload new logs and DynDOLOD.esm.

A somewhat quicker test run with just Tamriel, object LOD, standard tree LOD and dynamic LOD would be enough.

Yeeees, it seems to work!! I did a quick test with just Tamriel LOD (without occlusion) and I'm getting perfect results with LOOT/autosort, no cyclic rules whatsoever! Thank you so much!!

  • +1 1
Posted (edited)
3 hours ago, TheDude said:

Yeeees, it seems to work!! I did a quick test with just Tamriel LOD (without occlusion) and I'm getting perfect results with LOOT/autosort, no cyclic rules whatsoever! Thank you so much!!

Hmm, unfortunately I'm now getting a lot of "Access violation"-errors instead (when I'm trying to generate lod for all worldspaces + occlusion) so I had to abort the Lod-generation since the program was stuck... Files including bugreport: https://limewire.com/d/XoUEi#0u0CpnUPOe

Edit: the errors seems to happen when Dyndolod tries to generate occlusion for "DLC01FalmerValley "Forgotten Vale"

Edited by TheDude
Posted
7 hours ago, TheDude said:

Hmm, unfortunately I'm now getting a lot of "Access violation"-errors instead (when I'm trying to generate lod for all worldspaces + occlusion) so I had to abort the Lod-generation since the program was stuck... Files including bugreport: https://limewire.com/d/XoUEi#0u0CpnUPOe

Edit: the errors seems to happen when Dyndolod tries to generate occlusion for "DLC01FalmerValley "Forgotten Vale"

I uploaded a new test version that hopefully should run through.

  • Like 1
Posted (edited)

DynDOLOD_SSE_log

I have no idea what is wrong. There are many, many warnings when I ran DynDOLOD 3. I've spent the last several hours trying to look over things and I am more confused now than I was when I started. I've tried to follow the instructions on this thread where I've read https://dyndolod.info/ and searched through this discussion. I've gone over my mod list and load order to check everything is set and that Majestic Mountains has the correct DynDoLod V 3.0 Lod pack. I've also gone searching through the mod's pages on Nexus and it's just left my head hurting.

One of the instructions is not to ignore DynDOLOD warnings. Four of the warnings are "Property Not Found * In Scripts", 3 of them reference 000FCBathOutfitTrigger in ForgottenCity.esp and one of them references secondsetofrocks in Ascend - Hidden Peaks of Skyrim.esp. I've no idea about scripting, there is nothing to find out about the Forgotten City but it is mentioned in the 'bug reports' of the Ascend - Hidden Peaks of Skyrim mod where it has been labeled 'not a bug' and the mod author jayserpa instructs that not all properties in a script need to be filled so ignore DynDOLOD. So I'm confused. Do I ignore it?

Some of the warnings were "Duplicate Reference" which the LOD will not duplicate and some were "Reference Attached to Wrong Cell" like the one I found referencing Environs - Tundra Farmhouse.esp that was mentioned in the mod's 'bug report'. Are these essential to fix or just something at would be good to fix for a cleaner game? I'd rather not try to clean it myself as I've spent three weeks and I'm too confused to try these things just to tidy up some when it can be reported to the mod's authors for a patch.

There are also fourteen "Potentially Wild Edit Reference" warnings all of them in the Sleepwalking Into A Nightmare - New Daedric Prince Quest and mentioned on their 'bugs reports' again where it is instructed to disable the mod when running DynDOLOD. Again something I would rather not have to fix myself if it's just some trees floating in hell.

I am mostly confused by the many, many "Textures Do Not Match" warnings because I'm using DynDOLOD Resources SE 3  Additional DynDOLOD Resources and DynDoLod V 3.0 Lod pack (all versions) so I've no idea what is going wrong?

Also for 'Filename * Does Not Adhere To File Naming Conventions' most of them are in Skyrim.esm or Dawnguard.esm. Should I ignore these warnings? It's possible but at this stage I'm just too confused to know anything for sure anymore.

There is a lot that is wrong here and it's so much I'm not sure why or what to fix, what to ignore or what to remove. I really need some help even to know where to start from.

Edited by Bushranger

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

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