Jump to content
  • 0
Sign in to follow this  
Fixer040

City Entrances Overhaul - Markarth

Question

I am having some issues with DynDOLOD when using the mod City Entrances Overhaul - Markarth. I've been working on a modified version of it which tries to fix all of the bugs and incompatibilites plaguing the original version (as per the author's permission, since he said that he will not do any additional fixes). I have had literally 0 modding experience before that so there is definitely a chance that I'm messing something up, but everything seems to work nicely from up close, however as soon as I move far away, enough for the LOD to kick in, I get some really weird issues.
The first issue is that some sections of the entrance wall are just entirely missing.
gkuD7a6.png
I tried to read the documentation for DynDOLOD and I would just like to ask here to make sure that I understand what needs to be done to fix this correctly. That being, I believe I should add individual mesh rules for either every instance of the static objects that are missing, or better yet just for the objects actually used within my .esp using their ref id? The problematic objects seem to be MrkFrontWALLintBldg02a, MrkBlockA01 and MrkBlockB01, though there will probably end up being a few others that I've missed. So, will adding a mesh rule that sets the LOD 4 option to Static LOD 4 be enough to get rid of this issue?
The other issue is that even the parts that actually show the LOD seem very different to the actual full model that loads in when you get closer, resulting in a very noticeable pop-in. Some of the textures just seem way too dark compared to the original. For reference, this is what it looks like up close:
mvnnait.png
I suppose this may as well just be that there are some objects that are supposed to be in front of the visible walls, but there is no LOD of them due to issue #1? Otherwise, I suppose I could get around this issue by setting the LOD4 to use the full model (though that will most likely not be performance friendly)?

 

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

Yes, adding mesh rules that define to use the full model for LOD in case an object LOD model does not exist should work in this case. See DynDOLOD_Mod_Authors.html for more.

 

It seems you are using a mod that updates pre-rendered object LOD textures, like HD LODs for example. If they don't match your full textures well, try generating LOD without that mod so the vanilla object LOD textures are used.

Share this post


Link to post
Share on other sites
  • 0

Yes, I am using the HD LODs mod, though only the DynDOLOD version of it which if I remember correctly says that it only contains LODs that DynDOLOD has trouble with for whatever reason. Could this version of the mod still cause such an issue?
 

Share this post


Link to post
Share on other sites
  • 0

Yes, I am using the HD LODs mod, though only the DynDOLOD version of it which if I remember correctly says that it only contains LODs that DynDOLOD has trouble with for whatever reason. Could this version of the mod still cause such an issue?

 

It is most likely the one replacing the vanilla LOD textures. AFAIK it is supposed to be used with Noble Skyrim.

Share this post


Link to post
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
Sign in to follow this  

  • Similar Content

    • By sheson
      DynDOLOD DLL for Skyrim, Skyrim Special Edition, Skyrim Anniversary Edition and Skyrim VR
      So far all versions of DynDOLOD use the SKSE plugin PapyrusUtil for the optional dynamic LOD in the game. Starting with version 2.45 there is now the alternative DynDOLOD DLL available.
      The current DLL version is 2.45. It works with dynamic LOD generated by DynDOLOD Standalone 2.45 and newer.
      Read the ..DynDOLOD\Docs\DynDOLOD_DLL.html included in DynDOLOD Standalone for an explanation about DynDOLOD DLL, installation instructions (overwrite papyrus scripts of DynDOLOD Resources) and how it works.
      If there are problems with it, check DynDOLOD_DLL.html and the DynDOLOD FAQ first before posting.
      If a DynDOLOD.DLL version is required for a game version that is not listed below, request it in this thread. First, search this thread if it has been requested already, though. The future will tell how long it takes to release updates.
      Typically a new DynDOLOD.DLL is required for each new game version, but not each new SKSE version. For example a DynDOLOD.DLL compiled with SKSE64 2.0.9 also works with SKSE64 2.0.10 for the same game version.
      Nexus Downloads for DynDOLOD 2.45 and higher
      DynDOLOD DLL for Skyrim
      DynDOLOD DLL SE for Skyrim Special Edition
      DynDOLOD DLL VR for Skyrim VR
      Mega Mirrors:
      DynDOLOD.DLL + Scripts for Skyrim 1.9.32 (overwrite the papyrus scripts included in DynDOLOD Resources)
      DynDOLOD Scripts for Skyrim Special Edition and Skyrim VR (overwrite the papyrus scripts included in DynDOLOD Resources SE)
      DynDOLOD.DLL for Skyrim Special Edition 1.5.39
      DynDOLOD.DLL for Skyrim Special Edition 1.5.50
      DynDOLOD.DLL for Skyrim Special Edition 1.5.53
      DynDOLOD.DLL for Skyrim Special Edition 1.5.62
      DynDOLOD.DLL for Skyrim Special Edition 1.5.73
      DynDOLOD.DLL for Skyrim Special Edition 1.5.80
      DynDOLOD.DLL for Skyrim Special Edition 1.5.97
      DynDOLOD.DLL for Skyrim Special Edition 1.6.318
      DynDOLOD.DLL for Skyrim Special Edition 1.6.323
      DynDOLOD.DLL for Skyrim Special Edition 1.6.342
      DynDOLOD.DLL for Skyrim Special Edition 1.6.353
      DynDOLOD.DLL for Skyrim Special Edition 1.6.629
      DynDOLOD.DLL for Skyrim Special Edition 1.6.640
      DynDOLOD.DLL for Skyrim Special Edition GOG 1.6.659 (untested)
      DynDOLOD.DLL for Skyrim VR 1.4.15
    • By Ease
      I have a problem with two excessively glowing window textures that I've been troubleshooting for several hours now and I cannot seem to figure it out. The problem is only resolved if I disable DynDOLOD and I had to go through my entire load order to figure that out. The almighty Google hasn't found me a whole lot of information on it either. I've read through the Glow LOD section of the dyndolod.info webpage and have messed around with just about every setting I can, but still, I cannot solve this problem. I'm completely open to the idea that it's one of my mods conflicting with DynDOLOD, but I cannot for the life of me figure out what. It may be right under my nose too. I wouldn't be surprised.
      The two windows in question seem to be (according to more informative console) WRTempleOfK01 and WRHouseWind02. 
      Things I have tried:
      Making a fresh save file Disabling any texture mods I am using that change any architecture in Whiterun Disabling my lighting mods Generating LODs without any form of FX, candles, windows glow or any form of LOD glow available Rebuilding ENB shader cache Tweaking window lighting in my ENB settings I've included my mod list as well in case anyone here has a bigger brain than me and can spot the problem just by looking at what I have.
      In the screenshot attached you can see the problem I'm having. Any help on this would be greatly appreciated because I'm not the best at this stuff. Thanks!

      EDIT: Well, after several hours of trying to figure it out, I finally isolated the problem minutes after making this thread. I thought about deleting the thread but instead maybe this might help out someone else in the future. The file causing the issue specifically was in TexGen_Output under textures/architecture/whiterun/wrwindows01_g.dds. I hid the file and now my windows are glowing properly, ending my hours of suffering over a minute detail. 
      Below is a screenshot of the corrected glow on the windows. 

      modlist.txt
    • By 1990srider
      So currently I'm trying to get the stockade mesh in the mesh/clutter/stockade/.nif to show up as full mesh in my lod generations. Because I'm creating new full models using Dyndolod. I've gotten everything else and every other type of model to do what I need it to. Ive tried .....esp/esm;formid I've tried the file path shortened and full all the way to be of the nif file being included. 
       
      4 is full 8 is full 16 is full. I've had this issue also with highherothgar floor models not showing ether... I spelled that wrong in here but yeah. I've tried looking for another rule or mesh mask the could be interfering and I can't find anything. Anyone have any idea what could be wrong?? I'm not trying to generate a lower poly lod I'm using this for other purposes.
       
       
       
       
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.