Jump to content
  • 0

guide on how to get LOD glow windows for custom models?


I have designed a custom building model, and with it, I have a custom LOD model for my building. As my building has exterior windows with glow, I have additionally made LOD models for the windows. I want to use DYNDOLOD to thus enable my LOD building model to also use the LOD window model.


There are no guides for this in the manual, as the section dedicated to describing LOD glow is only written for skyrim models (e.g. enabling LOD glow for High Hrothgar), but there is nothing there for modmakers who want their custom buildings to have LOD glow.


So as I spend some time trying to figure out how for instance the High Hrothgar LOD glow windows work, I am assuming that there may be many hidden variables that I am completely missing that I would never be able to figure out myself. So for Shenson or anyone out there who have themselves successfully gotten LOD glow to work on models that previously have not had LOD glow, I would appreciate any guidance I can get.

Share this post

Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

Yes, the manual is thin on the details for that. Make sure to read the Glow LOD Windows section in the manual:
Checking the [x] Windows option adds glowing LOD windows to all vanilla LOD buildings. Glow LOD Windows are independent meshes that are added in addition to the LOD of the object they belong to. If the [_] High option is not checked the glowing windows are added as static object LOD. Check the [x] High option to add glowing windows as dynamic object LOD if applicable. As explained above, dynamic object LOD windows react to external lighting. However, windows on vanilla forts for example are not using external emittance and consequently will always be generated as static object LOD.
Most windows are automatically added to the FarGrid, some are added as neverfades that always show regardless of distance. This is determined by the *glow_lod_X.nif file name. If X equals _0 it is assigned to NearGrid (LOD4), _1 to FarGrid (LOD8) and _2 (LOD16) is a neverfade.


The glow LOD windows are done as a separate meshes. If required (and if High Windows has been checked) they can be added as dynamic LOD in order for them to react to the external emittance (window lighting changes based on weather/light conditions) settings defined on the reference. Otherwise they will be simply merged into the static object LOD BTO.


For example, if the LOD model has the file name house01_lod*, its glow LOD windows should have the file name house01glow_lod_*.nif.


If checking [x] Windows, the glow LOD mesh is then automatically found whenever a reference uses house01_lod_1.nif. There are no additional settings required.


Check the existing glow LOD meshes. They are also setting Decal, Dynamic_Decal on Shader Flag 1 and No_Fade on Shader Flag 2 as that will be help with the long distance visibility and z-fighting.

The windows themselves typically float a bit in front of the LOD mesh for the structures.


Now when you include the house01_lod* and its house01glow_lod* LOD meshes with your mod and then later users use DynDOLOD to generate LOD with the Windows and optional High settings checked, it should just work.

  • Upvote 1

Share this post

Link to post
Share on other sites
  • 0

After following these directions, everything works beautifully!


I have only tried this for a single house, using the NIF naming conventions:

house01 (for the base highpoly model)

house01_lod (for the LOD model)

house01glow_lod_1 (for the LOD glow windows), with 1 meaning assigned to FarGrid. 


I am not using external emittance and am deciding on just using the glow windows as static LOD for now. Once I am more confident in how I can liberally use the various features within dyndolod, I will experiment. However, with static LOD only (only checking [x] Windows and leaving the rest of the stuff to the right of that unchecked), I can confirm that everything works beautifully, and now my building's LOD model has working LOD windows.


I should note that for the LOD window mesh, I also as you recommended for improved visibility at far distances, "also setting Decal, Dynamic_Decal on Shader Flag 1 and No_Fade on Shader Flag 2 as that will be help with the long distance visibility and z-fighting." I first did it without this, and decided I couldn't see the glow at all from a very far distance, so then I added these flags. Regardless if these flags are checked or not, for many weathers where there is even a very slight mist / fade at a distance, I am getting the window glow to not be visible, where the silohuette of the rest of the building is still visible. I'll play around with this more to see differences in visibility performance, but as things stand now I am very happy and content with the results. 


You sir are a pillar to this community. The credit will be yours when someday my mod finally gets out there.

Share this post

Link to post
Share on other sites
  • 0

One test I like to do, compare the full model with its glowing windows at the same distance as the LOD by using tfc in console. LOD has only limited shader support, but often it is just the way the engine works.


Check the mipmaps of the glow map texture_g.dds of the third texture slot. Test if removing the mipmaps yields better results. Consider manually creating the mipmaps or using another mipmap shrinking texture algorithm in the graphics program you use edit textures. If you check the mipmaps of hhwin02noalpha_g.dds you will see that they basically just become a white pixel in the end. The usual algorithm would make it dark grey/black.


You can also try increase to the Emissive Multipe value in the Shader of the glow LOD mesh a bit. 


ENB affects lighting, test without it for comparison.


Good luck with the mod.

  • Upvote 1

Share this post

Link to post
Share on other sites
  • 0

Good to know these things, I'll try another mipmap gen tool at some point once I figure out what a mipmap is.


I used blender to bake my LOD glow windows from the original highpoly windows, and I note that if you do this, you will need to play with the emissive multiple, like you are saying. Where the original windows had an emissive multiple around 1-2, I am needing to bump up to between 9 and 12, otherwise they always start out too dim (blender doesn't bake the correct brightness). But this otherwise helps to ameliorate my previous problem of the dimness of the windows at a distance. 


Fixing the emissive multiple in combination with setting it to a neverfade is a good solution.

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

  • 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 sheson
      This is a beta of [FNV|FO3|FO4|FO4VR|TES5|SSE|TES5VR|ENDERAL|ENDERALSE]LODGen/Edit with terrain LOD meshes and textures generation.
      This is for experienced mod authors and users that know how to use xEdit, xLODGen or DynDOLOD already.
      Installation and Setup
      xLODGen beta 95 - based on 4.1.4b
      Unzip into a dedicated folder outside of any Steam, game or mod manager folders or special Windows folders like Program Files.
      Rename xLODGen.exe to [game mode]LODGen.exe (TES5LODGen.exe for example) or start with command line parameter -fnv, -fo3, -fo4, -fo4vr, -tes5, tes5vr, -sse, -enderal, -enderalse
      Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder. Then install output as a mod.
      Do not generate into any game, any mod manager folders or special Windows folder like Program Files x86.
      Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which xLODGen.exe (x86) or xLODGenx64.exe (x64) is used.
      RTFM and Share Results
      See the included Skyrim-Occlusion-Readme.txt for a brief explanation of the Skyrim TVDT Occlusion data generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions or give feedback in the dedicated Skyrim TVDT - Occlusion Data thread.
      See the included Terrain-LOD-Readme.txt for a brief explanation of the settings for terrain LOD generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions about terrain LOD in this thread for a more in-depth explanation if required and share feedback (with screenshots) about results or problems.
      These tools generate LOD meshes and textures "exactly" like CK, but not like the meshes and textures which are shipping with the games (they are often manually edited).
      However, these tools provide more options and higher resolutions (use the x64 version if there are memory errors because you believe you require 4k or higher) and can be updated to add more useful features and options.
      I did some testing in the different games, but finding the best combinations of options and settings requires lots of testing and are a matter of personal opinion and which game is used, the load order, mods, even different worldspaces probably.
      That means, I am only able to give generic guidelines and hints to send you off to find and test for yourself and share your results. My main interested is that generations works correctly and without problems for now.
      Check out the thread xLODGen Terrain Settings Compare. Also refer to any modding guide which has a list of relevant mods close to your load order.
      The object and tree LOD generation is the same as the current versions of xEdit / xLODGen. Refer to their respective descriptions and explanations.
      Obviously, users of Skryim/Enderal/Skyrim SE/Skyrim VR/EnderalSE continue to use the easier and more comprehensive DynDOLOD for drastically improved object and tree LOD generation and only use xLODGen for terrain LOD (and maybe Occlusion) generation.
      First Time
      Here are suggestion to start without going crazy and that should be quick enough to generate:
      Set quality of meshes for LOD4 to 5 and then +5 for each next level. Or just set levels 8/16/32 to 10.
      Check protect cell borders (yes it fixes the ugly terrain drops at outer cell borders that still exist in Fallout 4).
      Use the max vertices setting only if you want to hard limit max file size.
      In Skyrim Special Edition or Skyrim VR, if you notice terrain briefly flickering when new areas are loading in, set [Display] bEnableLandFade=0 in Skyrim.INI
      Set Optimize Unseen to off for LOD4 for first generation. Start experimenting with a value of 550 with a quality setting of 10 or lower for LOD32 (used for map) and compare coastlines and file size to other settings.
      To quickly generate terrain LOD meshes just for the map, check only terrain LOD Meshes, check the Specific Chunk checkbox and set drop down to 32. Leave SW fields empty for complete map or set SW cell coordinates to same values as a *.btr filename to test a specific area with lots of water, river etc.
      Set texture sizes to 512 for a start. Larger sizes and large world spaces will take a considerable time (like 15 to 30 minutes or more easily). Each higher resolution means quadruple the work.
      Use DXT1 for diffuse and 565 (DXT1 if on Windows 7) for normal maps. If generating for Skyrim Special Edition and VRAM is not of concern use BC7. Uncheck mipmaps, raise steepness and Bake normal maps.
      For now, leave the Brightness, Contrast and Gamma at 0 and 1.0 respectively. It seems that only Skyrim CK and Skyrim SE CK are manipulating the intensity of the textures to adjust for the noise.dds and the god awful "improved" snow shader of Skyrim SE (just turn that thing off, really). If textures seem too dark in the game, brighten the noise.dds instead or vice versa. That way you can get perfectly matching LOD textures that look just like the textures in the loaded cells. For Skyrim a good average color of the noise texture seems to be around #C0. See below for a couple noise texture downloads.
      If you want to test larger texture sizes, use the chunk option to limit the number of textures that need to be generated. For example, check [x] Specific chunk, leave the drop down empty and set WS to the lower left cell coordinate of an 32x32 area, like 0, 0. It will then generate all textures up to 31,31. Not all worldspaces have their origin at 0,0 so you will have to check already generated meshes/texture filenames for their lower left coordinates.
      Questions and Feedback
      Obliviously anything related to terrain LOD should be posted in this thread.
      Posts related to Occlusion should be made here.
      Recommended Optionals
      TES5-Terrain-Tamriel.esm (Mega), SSE-Terrain-Tamriel.esm (Mega)
      TES5-Terrain-Tamriel-Extend.esm (Mega), SSE-Terrain-Tamriel-Extend.esm (Mega) - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm (Mega) - Entire map from -96,-96 to 95,96 with northern ocean extension. Useful for mod authors.
      Put in game data folder obviously. Adds back terrain for Skyrim (Tamriel worldspace) at the outer edges so there is no missing terrain meshes/textures when generating terrain LOD for Skyrim.
      Load as early with lowest priority as possible, so that any other plugins overwriting or adding land records or cells with the same coordinates take precedence.
      Only required to be loaded when generating terrain LOD. No harm done when loaded in-game but typically the player can not get close to these areas. There are no effects outside the far away added cells.
      Single color flat noise, Adjusted vanilla noise, HD Terrain Noise Texture SE
      Examples for Skyrim. Install to game folder like any other texture mod. The noise texture is applied in-game on top of terrain LOD textures, so no effect for LOD generation.
      Only the red channel is used in case the textures is not a grey channel format. MipMaps are ignored. The textures is tiled 3x3 per LOD quad, e.g. for LOD level 4, the noise texture is repeated 3 times to cover 4 cells, for LOD level 8, the noise texture is repeated 3 times to cover 8 cells and so on.
      For testing terrain LOD distances. Plain color terrain LOD textures for Tamriel with coordinates for every LOD quad. Green for LOD 4, yellow for LOD8, blue for LOD 16 and red for LOD 32.
    • By Hypobolic
      So after changing the tree mod I'm using as well as grass and some terrain textures, I'm going through the STEP LOD generation guide, in the DynDOLOD section there are some recommended rules for LOD generation when using A Clear Map of Skyrim. Specifically is says to set the Tree LOD4 rules to use Billboard4, and also notes that the Aspen trees can drop FPS by 30 if this is not done.

      It actually says that Aspen trees are ALWAYS set to tree LOD4, so as not to render branches.
      I am choosing not to use A Clear Map of Skyrim. My question is if the above statement is true for all tree LOD generation, even when not using A Clear Map of Skyrim?
      Even through these recommendations are inset under the heading specifically for A Clear Map of Skyrim, is this true when not using it? 30fps is an alarming number.
  • 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.