Jump to content
  • 0
Sign in to follow this  

DynDOLODGen Not using enderal despite passing the parameter


DynDOLODGen is using the skyrim configs despite the fact i have passed the "-enderal" parameter to it in command line.

my game IS in fact an enderal install, and TexGen worked flawlessly AFAIK. my question is there a different way to "suggest" to this program that i have enderal installed OTHER than the argument "-enderal"? as "-enderal" is clearly not what it is looking for, any ideas?

Share this post

Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

i believe the issue might have been on my end, i re-installed both the main resources and the optional hi-res textures from the optional patches, and now it has decided to go ahead and work right! sorry to anyone i may have bothered, and i would just like to mention how much i love your program! :)

Share this post

Link to post
Share on other sites
  • 0

For future reference: Enderal is discovered by checking for the Vyn worldspace in the Skyrim.esm that was loaded by loaded by DynDOLOD/TexGen. There is no command line parameter -enderal.

Share this post

Link to post
Share on other sites
  • 0

For future reference: Enderal is discovered by checking for the Vyn worldspace in the Skyrim.esm that was loaded by loaded by DynDOLOD/TexGen. There is no command line parameter -enderal.

ty i'll have to remember that

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
      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 94 - 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.
      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 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 VR 1.4.15
    • By sheson
      xLODGen beta (47 or newer) and DynDOLOD (2.70 or newer) can be used to update or generate TVDT Occlusion culling data on cell records, which is famously wrong for some cells in Tamriel causing rectangular holes in the distant LOD.
      Please read the included documentation Skyrim-Occlusion-Readme.txt in the xLODGen archive and the TVDT - Occlusion Data section in Docs/DynDOLOD_Manual.html to learn about TVDT data, how to generate it and the settings.
      Mod users / complete load orders
      For Skyrim, Skyrim VR and Skyim Special Edition I generally suggest to use DynDOLOD 3/xLODGen to create an Occlusion.esp for the entire load order. Generating the Occlusion.esp is fairly quick with quality 2 and it means not having additional plugins as master in DynDOLOD. The Occlusion.esp is automatically ESL flagged for Skyrim Special Edition. Since DynDOLOD is just the advanced version of xLODGen for tree and object LOD generation, the code to generate the occlusion data and the results are the same. Using DynDOLOD has the advantage that the occlusion is generated automatically with pre-defined settings in the DynDOLOD INI as part of the LOD generation process. Using xLODGen has the advantage of being able to update a separate plugin which only contains the occlusion data and nothing else more quickly and even for a specific worldspace only.
      For Enderal it seems more convenient to have DynDOLOD generate the data into the DynDOLOD plugin, so in DynDOLOD it is enabled by default for Enderal only. There are also additional optimizations in DynDOLOD for Enderal that help improve performance in certain locations.
      In xLODGen the Occlusion generation is an additional option below the Terrain LOD options. See the included documentation for information about the settings. Once generation is complete, Occlusion.esp is saved to the data folder (or MO mod folder / MO Overwrite folder accordingly). To make sure its updated TVDT data is used, ensure the Occlusion.esp is loaded last so it overwrites any other plugin.
      Generate the Occlusion.esp last. So the order would be:
      Finalize load order use xLODGen to generate terrain LOD meshes [and textures] use TexGen/DynDOLOD to generate drastically improved object and tree LOD (uses terrain LOD meshes for object LOD optimization) use xLODGen to create Occlusion.esp (uses object LOD meshes to determine max height samples) If the load order changes afterwards and a plugin makes changes to WRLD/CELL records, the entire worldspace should be updated in the Occlusion.esp (unless the new plugin loads after Occlusion.esp of course).
      Worldspaces in Occlusion.esp can be updated by simply starting xLODGen with the current Occlusion.esp being last in the load order. Select the desired worldspaces only and generate Occlusion for it. The selected worldspace is removed from Occlusion.esp and then generated completely anew for the new load order. Other worldspaces in the Occlsuion.esp will not be changed.
      Mod authors
      It is possible to update the TVDT data on CELLs in a single plugin by starting the tool in edit mode.
      Generate/Update object LOD first so the object LOD meshes match the current state of the worldspace.
      As suggested in the included documentation, generate max height data for all cells with CK beforehand. You are welcome to test the included MHDT generation as well.
      Consider defining/updating the Border Region for the worldspace so the +Border filter option can be used.
      Either start xLODGen.exe in edit mode with the -edit command line or rename xLODGen.exe to [Gamemode]Edit.exe e.g. TES5Edit.exe
      Select loading of plugins as usual. Right click desired plugin in the left tree view, click Other, Generate LOD.
      Check Occlusion and verify the text next to it mentions the desired plugin to be updated. Adjust other settings as desired and explained in the included documentation.
      For large / multi people projects it is probably better to generate an Occlusion.esp the usual way and merge the TVDT data. Stick to the usual workflow.
      As always, mod authors are welcome to direct message me here or on discord for help with their projects.
      Read the provided information and in case of questions about occlusion generation, post them in this thread regardless of using xLODGen or DynDOLOD.
  • 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.