Jump to content

Interactive Clutter (by fireundubh)

Recommended Posts

Re- configuring what you pick up, I'm thinking you're best served using the primary safety from your firearm. That's your index finger btw (& yes, I am a smart ass, but I mean well). :;):

I actually use my middle finger to pick things up.But that is not the issue I mean! If you have five carrots inside a basket in game and you try to ONLY grab the carrots, its near impossible! I generally resort to grabbing the basket and turning it upside down before grabbing my carrots... perhaps that's more immersive too...

Share this post

Link to post
Share on other sites

Really glad you posted on Immersive Clutter & Master of Disguise, both coincidentally compliment my current character quite nicely.

Since you're using Hunterborn, I'd also recommend Campfire Cooking. Better Favor Jobs is a good one, too. 

Looking over your list then it seems to me that the amount of firewood is rather... excessive.. as I recall then firewood if you harvest it is what 4 pieces at most ? and it has a weight of what 4 per piece? (sorry if I am outdated on this!)  But it just strikes me as one thing that perhaps should be toned down a little bit! In general since there is so MUCH clutter then what you can get from it should also be scaled down in comparison. Perhaps even add a feature of failing to get anything from an item.

In vanilla, you get 2 firewood every 8 seconds up to 6 firewood per activation. Each firewood weighs 5.
  • Upvote 1

Share this post

Link to post
Share on other sites

I'm sad I can't +1 your "middle finger response" (I'm always happy when I can say something that can, and probably should, be taken two ways).

As for clutter targeting, i assumed it was a mini-game (like lockpicking) try to grab the unowned cabbage without accidently stealing the owned kettle its in. You could always grab the carrot (by holding with your middle finger instead of clicking), lift it into the air, then click it to take it into inventory. Make that an app for mobile devices & get paid!


Ninja'd: got both your suggestions fireundubh, I'm not a stranger to your work (even know about that BFB backdoor). I threw in Cooking for Alchemy so I could skill up while Campfire Cooking and made a [spoiler=Merged plugin]Alternate Start Complete Cooking Expansion;Cooking AlchemyHelgen Imperial ArmoryCooking Expanded DBCampfire Cooking - AlchemyCooking ExpandedCooking Expanded HFCampfire Cooking - DGCampfire Cooking - DBStarting Spell ChoicePatch Starting Spell Choice - LAL



Endorsed the lot, I don't start a new game without them.

Edited by redirishlord

Share this post

Link to post
Share on other sites

The "physics problem" is basically ********. Sorry. More physics-enabled objects doesn't mean worse physics overall... As for picking up a cart instead of a cabbage, maybe try aiming first.

On the second part, you know as well as anyone here that you can be pointing your cursor right at an object, and still get the interaction for another one that, in Skyrim's mind, is between you and the intended object. That said, I'll acknowledge that point because...


You are going way overboard (IMO) about the physics issue. I readily agree, as has everyone here, that using vsync corrects the worst of the problems related. What we refer to is the side effects of having the added physics-enabled items. Things that have been mentioned include the way you can take damage from bodies just by walking over them, caused by HAVOK going wonky for a moment as a result of it's math; The Flying Mammoth (Sorry, Aiyen, for the incorrect attribution earlier), caused by exactly the same calculations; and high-velocity random flying objects that can be caused by (shockingly) the same calculations in addition to (and not only from) the aforementioned v-sync setting.


The argument is not that the engine has problems with physics and v-sync, which you seem unable to get away from. The concern is that, with the sheer number of additional items being physics enabled, more and more obvious issues of the types mentioned above can become far more noticeable. This is not an attack on your work in any way - it is a simple consequence of the engine, it's limitations, and the way HAVOK works it's voo-doo magic.


Try to keep in mind that, unlike most forums on the net that deal with mods and modding that I've seen, we are not here to rip apart ideas or denigrate a persons work. We look at, analyze, and try to provide feedback. Nothing anyone has said, including my single comment, is meant in any other fashion, and to have you reply as you did to my comments is, quite simply, uncalled for. Please, for the sake of the moderator's sanity, try not to lose your cool like that. It can only end in flamage, trolling, and other stuffs that none of us wants.


Honestly, if not for the simple and unavoidable (for now...) physics weirdness, I'd go for this. I simply choose not to potentially be in the direct path of a random edible missile.

Share this post

Link to post
Share on other sites

I don't see how calling this mod or More Interactive Items "an easy pass" qualifies as constructive feedback.


That's great for you that you're not going to use the mod. I respect your decision. But you know I can't fix the engine. Why bother telling me?


When you're not hungry, do you walk into every restaurant and tell the cooks you're not going to eat any of their food?


When you read about a mod on the Nexus and decide to not download it, do you post in the comments "I'm not downloading this"?


Seems to me you just wanted to say "I don't like your mod." That's cool. Well, I don't like your reasoning. At least I'm straight up about it.


As an aside, now I know why JustinOther quit modding Skyrim after More Interactive Items. He caught a lot of flak for trying to make the game more interactive, too.

Edited by fireundubh

Share this post

Link to post
Share on other sites

I don't see how calling this mod or More Interactive Items "an easy pass" qualifies as constructive feedback.

Well, I don't like your reasoning.

As a stand alone comment, out of it's complete context, it wouldn't be. I'm sorry if you take my comment in a way it wasn't intended, but the short version is that, because of all the things I listed before, I didn't have to think too hard about it's inclusion. If you don't agree with my reasoning, that's fair enough - if we all thought the same, mods wouldn't be needed to make good games even better.


I ask, again, that you not make this a crusade. While I've done no modding myself for Skyrim, I did spent just short of a decade producing several for the (now ancient) Quake3 Engine, and I understand fully the frustration that you are feeling at this moment. To continue the metaphor you used in your last post, I don't go into a restaurant to tell them I won't eat their food... I go in to help them make it into something I will eat. By stating the issue, identifying it, I hope to inspire you to go beyond what work you have already done and attempt to either find a way to resolve the issue or, at the least, to perhaps mitigate it. That is the purpose of forums such as this - at least in my mind. The work you have done is, by comparison to anything I am able to produce for this game, stellar. I simply believe that it can be better, and hope that you can match my vision to your reality.


You asked for feedback - you received it. Perhaps it is something that can't be fixed. But until that is known for certain? I've seen amazing work pulled of that nobody thought could be done. This mod and this idea could easily be the next one on that list.


And on that note, I'll step back... maybe I've replied once too often as is, but as I mentioned earlier, I do want to avoid a flame war.

Share this post

Link to post
Share on other sites

:) I'll have a look. At the least, I'll get it in the queue for testing after I resolve a lighting problem and animation issue I'm experiencing.


EDIT: That's what I get for posting before clicking. :) Let me rephrase - I'll CHECK THE LIST in a short while and see what I come up with. :)

Edited by Shadriss

Share this post

Link to post
Share on other sites

For my centennial post on the might STEP Forum, my thoughts on your list. It's pretty much a straight "went down the list, and had this thought" kind of thing. *shrug* SO yeah...


Bones to Bonemeal : Pretty straightforward, but it does occur to me that bigger body parts should produce more bone meal. Or maybe a pair of hands or feet producing one bonemeal... something to show that you get more of the end product out of a bigger beginning product.


Crate to Firewood : Similar to the above. With the amount of camping I've done where I've burned old pallets instead of logs in my fire, I think it's safe to say that a crate would give a smidge more than a single piece of firewood. Maybe up to three or four would be more realistic for the materials present? It would certainly align more with the amount of wood you are planning for barrels and the like.


Gold Utensils : I'm of two minds here. First, I agree with the results being in ore as opposed to ingots. I'm not sure on the numbers you get back though. My division of mind, honestly, has to do with two seperate setups, one with CCOR and one without. Using CCOR, where 5 ore = 1 Ingot, the numbers seem good. But for vanilla, where IIRC 2 ore = 1 ingot, then I think you would be able to get far more value out of the broken down item than the item itself is worth. Actually, that may be true with the CCOR version as well. This actually spawns another question in my mind - how are these items priced now that I can stick them in my Infinite Pocket of Infinity? And how do they balance against what I could get for them if they are broken down?


Urn Fragments : If there are two different sizes, why do both break down to the same amount of clay? Both the Large and Small versions yield a single piece.


Those things aside, the numbers look close to whats in my head - at least close enough that any difference would be pure personal preference.

Share this post

Link to post
Share on other sites

Turns out I worked with an old backup of a modified More Interactive Items so all of the values and weights are wrong.


What I'm going to do is:


- Value the new MISC items by dividing the value of the output by 1.5

- Weight the new MISC items by multiplying the weight of the output by 2


This makes it easy to say things like:


- 1 Stone Block is worth less than 10 Quarried Stone

- 1 Stone Block weighs more than 10 Quarried Stone

- 1 Stone Block produces 10 Quarried Stone


Breaking down an item trims the "fat," basically.

Edited by fireundubh

Share this post

Link to post
Share on other sites

I lie the "trim the fat" reference. I've been clearing BFB with v 0.1 installed, so far so good, no unexpected Havok related havok. Taking the urn several linen wraps were contained in had them gently hit the floor a roll / settle a little. I saw deer skulls in my path so I picked them up instead of impaling myself as I am want to do. I wouldn't call it intense or extensive testing, but initial impression re- physics is good.

Share this post

Link to post
Share on other sites

v0.2 has been uploaded.


- A new optional extension that adds recipes for breaking down items is now available. Hearthfire is required.

- All of the values and weights were updated to match the outputs of the respective recipes for breaking down items.

- The No Hearthfire main plugin and the No Hearthfire version of the recipes extension will be uploaded later.


Other extensions do not require updates; however, be aware that the values and weights are based on vanilla/USKP components. Later, I will need to provide two more main files with values and weights adjusted specifically for Requiem and Requiem - Hard Times.

  • Upvote 1

Share this post

Link to post
Share on other sites

Plugged this mod in to test it out for a bit. Only been using it for a few minutes and can tell you the issue with the objects bouncing on the tables is still present with iPresentInterval set to 0 or 1. Just sat in a chair at a table and had a pie jump off into the floor. At another table an egg kept rolling and rolling in place without anyone touching it.

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
      I will keep this post brief. Make use of the Help buttons and hover over settings. Do not hesitate to ask questions and provide feedback.
      This is early ALPHA to test things and iron out bugs. Certain things may be incomplete, not work as expected or change considerably between versions. In case of error messages, click "Help for this message" if available. Ask questions or report any problems or issue in this thread.
      If making posts or reporting errors, upload/paste these files (if they exist) to a file or text sharing service:
      ..\DynDOLOD\Logs\[DynDOLOD|TexGen]_[TES5|ENDERAL|SSE|TES5VR|ENDERALSE]_log.txt (truncate large log files to last meaningful generation)
      If issue involves LODGen upload/paste
      DynDOLOD Standalone 3.00 Alpha-35 (Mega) DynDOLOD Resources 3.00 Alpha-10 (Mega) for Skyrim/Enderal or DynDOLOD Resources SE 3.00 Alpha-10 (Mega) for Skyrim SE/Skyrim VR/Enderal SE Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 For dynamic LOD: SKSE, SKSE64, SKSEVR and PapyrusUtil, PapyrusUtil SE, PapyrusUtil VR  or DynDOLOD DLL For grass LOD: A warm precache from No Grass In Objects. See next post for details. For Majestic Mountains: Majestic Mountains LOD Pack for DynDOLOD 3 (Mega)  
      Install the requirements as usual. Install the Core Files from either DynDOLOD Resources or DynDOLOD Resources SE depending on the used game version. Typically overwrite any files or refer to Load/Overwrite Orders. Install other options as desired. Unpack the DynDOLOD Standalone archive into a new 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game or any mod manager folders. If the tools are started without setting a Game Mode with a command line argument (-tes5 for Skyrim, -sse for Skyrim Special Edition etc.), a message window will prompt for the desired Game Mode.  
      LOD Generation
      Use TexGen to generate object LOD textures and tree/grass LOD billboards into a dedicated output folder and then install as a mod. Use DynDOLOD to generate object LOD (includes grass LOD if enabled), tree and optional dynamic LOD into a dedicated output folder and then install as a mod.  
      Major Feature Changes
      Generate high quality tree/grass LOD billboards with TexGen. No need to install any billboards. Ultra tree LOD is now a checkbox - remember to update the tree mesh rule as desired. Billboard Grass LOD in object LOD Level 4. See next post for details. Generate some pre-rendered object LOD textures, including all cities. Generate an underside terrain mesh to block sun rays. Automatic texture replacements for stitched object LOD textures.  
      Changelog 3.00 Alpha 35
      DynDOLOD.exe - fixed not updating Mesh Mask/Reference list view
      DynDOLOD.exe - improved reporting and ignoring of some missing textures
      3.00 Alpha 34
      TexGen.exe/DynDOLOD.exe - added game mode selection window if started without game mode command line argument
      DynDOLOD.exe - improved automatic texture replacements for stitched object LOD textures
      DynDOLOD.exe - do not warn about missing textures if they are being replaced
      DynDOLOD.exe - automatically create stitched object LOD texture for replaced textures if required
      DynDOLOD.exe - automatically create non alpha texture of full texture if required
      DynDOLOD.exe - improved mini atlas export data
      DynDOLOD.exe - improved worldspace bounds warning/error settings
      DynDOLOD.exe - fixed and improved mesh rules loading order
      DynDOLOD.exe - fixed sometimes ignoring Reference Enable mesh rule setting
      DynDOLOD.exe - fixed a case of wrongly setting LOD Levels to None
      DynDOLOD.exe - fixed not updating reference rules internally
      DynDOLOD.exe - improved detection of childworld copies
      DynDOLOD.exe - never list child worldspaces that use parent worldspace for LOD even if they have a lodsettings file
      TexGen.exe - added/updated rendered object LOD textures
      TexGen.exe - fixed wrong output path for rendered billboards found in data folder
      TexGen.exe - do not try to render textures for DLC if DLC is missing
      TexGen.exe - improved config file reading for records in ESL flagged plugins
      TexGen.exe - added CreateMod INI setting to generate textures to include in a mod that won't prompt to uninstall old TexGen output
      LODGen.exe - fixed an issue with sometimes not combining crown and trunk when generating hybrids
      LODGen.exe - fixed a random grass LOD exception
      LODGen.exe - fixed grass LOD not being generated for grasses added by ESL flagged plugins
      LODGen.exe - default threadsplit to number of physical cores
      DynDOLOD Resources - updated meshes and textures for better compatibility
      DynDOLOD Resources SE - updated meshes and textures for better compatibility
      3.00 Alpha 33
      DynDOLOD.exe - fixed an issue with adding grass LOD billboards to object LOD atlas
      3.00 Alpha 32
      DynDOLOD.exe - fixed wrong INI settings
      3.00 Alpha 31
      DynDOLOD.exe - added Enderal SE Steam support, start with -enderalse command line argument
      DynDOLOD.exe - added INI settings CrownBrightness, TrunkBrightness, FlatTrunkBrightness vertex color multipliers to control brightness of 3D tree models in object LOD
      DynDOLOD.exe - never ignore neverfades in child worlds for upgrading to static or dynamic LOD
      DynDOLOD.exe - fixed accidentally adding material shader to glow LOD
      DynDOLOD.exe - do not use empty list item from lists in INI
      DynDOLOD.exe - fixed not always disabling some dynamic LOD correctly in scanned childworlds that also have their own LOD (e.g. Markarth)
      TexGen.exe - added rendered object LOD textures - most notably Solitude, Markarth, Riften, Windhelm and College of Winterhold
      LODGen.exe - CrownBrightness*=, TrunkBrightness*=, FlatTrunkBrightness*= added
      DynDOLOD Resources SE - updated meshes and texture for better compatibility
      3.00 Alpha 30
      TexGen.exe - fixed sometimes wrongly applying specular 3.00 Alpha 29
      TexGen.exe - improved loading of cubemap textures
      3.00 Alpha 28
      TexGen.exe/DynDOLOD.exe - added Enderal SE support, uses its own config files in anticipation of Steam version
      DynDOLOD.exe - fixed accidentally generating tree LOD instead of object LOD for child world copies
      DynDOLOD.exe - add full-model-CRC32 matching for object/dynamic LOD models for automatic support of "dumb" mesh replacer mods
      DynDOLOD.exe - fixed not adding center cell data for first dynamic LOD activation
      DynDOLOD.exe - added/updated rules for better compatibility
      TexGen.exe - properly ignore trees without models or deleted base records
      TexGen.exe - added environment/cubemap shader
      TexGen.exe - added rendered object LOD textures - most notably vanilla Whiterun and Dwemer Ruins, DynDOLOD Dawnguard castle and more
      LODGen.exe - improved parsing of txt files
      Texconv.exe - updated to latest version
      DynDOLOD_Manual.html - updated explanations information for Enderal
      DynDOLOD Resources SE - updated meshes and texture for better compatibility
      3.00 Alpha 27
      DynDOLOD.exe - added INI setting TerrainUndersideIgnoreWorlds=
      LODGen.exe - optimize underside terrain by removing triangles for default terrain height
      DynDOLOD-Resources-SE - added patch to enable grass for Whiterun exterior

      3.00 Alpha 26
      DynDOLOD.exe - add terrain underside references to ESP so they work in all worldspaces
      3.00 Alpha 25
      DynDOLOD.exe - fixed a problem with thread control
      DynDOLOD.exe - fixed patches sometimes being confused about the destination plugin
      DynDOLOD.exe - improved enabling/disabling of underside mesh
      Papyrus Script - updated objectenabler script
      3.00 Alpha 24
      DynDOLOD.exe - enable/disable terrain underside meshes in child worldspaces
      DynDOLOD.exe - only generate terrain underside meshes for worldspaces that have LOD level 32
      DynDOLOD.exe - fixed ignoring skinned meshes for dynamic LOD
      Papyrus Script - new objectenabler script for terrain underside meshes
      LODGen.exe - do not fail if optional billboard txt file is not present
      LODGen.exe - fixed sometimes not automatically setting passthru for glow shader
      LODGen.exe - fixed sometimes not applying replacement textures
      3.00 Alpha 23
      DynDOLOD.exe/TexGen.exe - fixed not using SSE config files for TES5VR
      DynDOLOD.exe - added INI settings TerrainUnderside, TerrainUndersideQuality and TerrainUndersideHeigth to automatically generate and place a terrain NIF that aids in blocking sun rays
      3.00 Alpha 22
      DynDOLOD.exe - added INI settings DoubleSidedTextureMask and DoubleSidedMeshMask to force double sided flag for specfic meshes or textures
      LODGen.exe - DoubleSidedTextureMask= and DoubleSidedMeshMask= added
      3.00 Alpha 21
      DynDOLOD.exe - ignore billboards without txt files so LODGen does not fail later
      LODGen.exe - added GrassDensity= to allow for lower density of grass LOD billboards in object LOD
      LODGen.exe - added ThreadSplit= to control ratio of main to sub threads for object LOD generation
      3.00 Alpha 20
      LODGen.exe - fixed looking up wrong path in BSA for billboard txt
      3.00 Alpha 19
      DynDOLOD.exe - fixed skipping over some references using LIGH
      DynDOLOD.exe - fixed ignoring overwrites from patches
      DynDOLOD.exe - fixed not always copying XEMI record from child world to existing parent LOD representations
      DynDOLOD.exe - ignore references with only a notice that have been moved out of their original worldspace
      DynDOLOD.exe - fixed ignoring XESP parent configuration not working as intended
      TexGen.exe - do not leave orphaned billboard files in case they are filtered out
      3.00 Alpha 18
      DynDOLOD.exe - fixed wrong tree LOD atlas coordinates
      3.00 Alpha 17
      DynDOLOD.exe - fixed index out of bounds while generating tree LOD texture atlas
      3.00 Alpha 16
      DynDOLOD.exe - ignore duplicate patches
      3.00 Alpha 15
      DynDOLOD.exe - default to -memory instead of -speed
      DynDOLOD.exe - added duplicate texture removal to object LOD atlas generation
      DynDOLOD.exe - added thread limit settings for some Occlusion operations
      LODGen.exe - fixed an indexing error
      LODGen.exe - added Threads= to limit number of concurrent LOD generation threads, defaults to number of cores
      3.00 Alpha 14
      DynDOLOD.exe - fixed not ignoring player enable parent for tree LOD
      TexGen.exe - fixed a case of not ignoring case
      3.00 Alpha 13
      DynDOLOD.exe - fixed sometimes leaving ITM records
      DynDOLOD.exe - fixed removing alpha channel from texture if NiAlphaProperty threshold is 0
      DynDOLOD.exe - fixed sometimes setting unresolved material links
      DynDOLOD.exe - fixed not overwriting earlier rules
      TexGen.exe - maximize and trim billboard texture based on render instead of vertex bounding box
      TexGen.exe - do not generate billboard if textures are missing
      LODGen.exe - fixed sometimes not using side-view billboard
      3.00 Alpha 12
      DynDOLOD.exe - fixed wrong load order detection for ESP only generation
      3.00 Alpha 11
      DynDOLOD.exe - fixed sometimes modifying other plugins
      TexGen.exe - added separate MaxSuperSamples options for grass, tree and objects
      LODGen.exe - fixed sometimes not discovering grass billboards correctly
      3.00 Alpha 10
      DynDOLOD.exe - removed a left over debug check stopping things for no reason
      3.00 Alpha 9
      DynDOLOD.exe - fixed sometimes copying wrong overwrite record
      3.00 Alpha 8
      DynDOLOD.exe - fixed sometimes not matching LOD models
      3.00 Alpha 7
      DynDOLOD.exe - fixed sometimes adding a duplicate textures on atlas
      3.00 Alpha 6
      DynDOLOD.exe - fixed not adding master for direct childworld copies
      3.00 Alpha 5
      DynDOLOD.exe - demoted duplicate cell exception to a warning
      DynDOLOD.exe - check for childless worldspaces 
      DynDOLOD.exe - fixed not adding master for enable parent of object activators
      DynDOLOD.exe - improved reading of grass data
      DynDOLOD.exe - added INI setting AlphaFactor= to control internal mipmap alpha coverage
      DynDOLOD.exe - improved normalization of assets paths
      TexGen.exe - ^^which means finding textures with rooted texture paths found in NIF
      3.00 Alpha 4
      DynDOLOD.exe - fixed trying to add references for empty parent models for glow LOD
      DynDOLOD.exe - report missing base record LOD definitions if automatic matching fails
      DynDOLOD.exe - do not add worshippers to cells added by ESP
      DynDOLOD.exe - fixed forced load order resulting in orphaned records 
      DynDOLOD.exe - double check if there are duplicate cells
      DynDOLOD.exe - monitor for duplicate triplets
      DynDOLOD.exe - properly blame ESP not setting MSTT DATA - Flags 0x4 
      TexGen.exe - fixed localization preventing rendering
      TexGen.exe - fixed sometimes writing wrong CRC32 for textures
      3.00 Alpha 3
      DynDOLOD.exe - ignore inconsequential unresovled errors in DLC and paid mods
      3.00 Alpha 2
      DynDOLOD.exe - fixed INI setting typo
      DynDOLOD Help - updated grass LOD settings information for No Grass In Objects version 6

      3.00 Alpha 1
      DynDOLOD.exe - converted all remaining external pas scripts to native code
      DynDOLOD.exe - added ultra LOD as a GUI option
      DynDOLOD.exe - export binary terrain file for LODGen
      DynDOLOD.exe - export grass LOD billboard file for LODGen
      TexGen.exe - converted all remaining external pas scripts to native code
      TexGen.exe - added OpenGl renderer and options to generate object LOD textures and tree/grass LOD billboards from models
      LODGen.exe - added support for reading Skyrim Special Edition CGID grass data files to place grass billboards in static object LOD meshes
      LODGen.exe - PathGrass= path to folder with xy.cgid files
      LODGen.exe - GrassMap= file with simple (NIF_FormID) billboard filename to fully qualified (textures\terrain\LODGen\...) billboard filename
      LODGen.exe - GrassBrightness*= vertex color multipliers to control overall brightness of grass
      LODGen.exe - use optional binary terrain file for pre-pass removing unseen faces for object LOD, TerrainData= as for terrain LOD
    • 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 83 - based on 4.1.3g
      Unzip into a dedicated folder outside of any game and Steam folders or special Windows folders like Program Files.
      (Pro users can merge with existing xEdit installation. Make sure to overwrite older LODGen.exe/LODGenx64.exe TexConv.exe/TexConvx64.exe in Edit Scripts. All other files with the same filenames are the same as the latest version of xEdit.)
      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 or any mod manager folders.
      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 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, SSE-Terrain-Tamriel.esm
      TES5-Terrain-Tamriel-Extend.esm, SSE-Terrain-Tamriel-Extend.esm - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm - 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 DangerousDeraz
      Hello there, Just finished installing STEP for Skyrim SE, Everything looks great and smooth.
      I've one question thou, my brother has the same game but without any of these mods installed on his PC.
      is it possible that i just copy the "modding" folder and "skyrim SE" folder to his PC and it'll work just as it works on mine? or is there another way?
  • 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.