Jump to content
DoubleYou

Skyrim Tree Settings Guide

Recommended Posts

Discussion thread:

Skyrim Tree Settings Guide by STEP

Wiki Link


This thread is for discussion and improvement of the Skyrim Tree Settings Guide on the wiki.

 

 

Guide scope

This guide is intended to be a guide to the tree configuration settings for The Elder Scrolls V: Skyrim game as set through INI files. Its purpose is geared toward understanding how trees work in Skyrim and optimizing them for individual use.

 


I was going to make this into a thread but decided it was better suited on the wiki.

Share this post


Link to post
Share on other sites

Thanks for your hard work on this DoubleYou.

 

I am a bit confused on a couple of settings though. Specifically the following:

 

SkyrimPrefs.ini

[Display]fMeshLODLevel1FadeTreeDistance=6144fMeshLODLevel2FadeTreeDistance=4096fTreesMidLODSwitchDist=8192

In the step SkyrimPrefs guide, it is recommended to set these settings to 10000000. So then which is better? 10000000 or the tweaks listed above?

Edited by Cameron9428

Share this post


Link to post
Share on other sites

I'm still tweaking to find out what the best values are... the values that show the best detail at the least performance cost. Bethesda just threw high values in the similar settings, which I have copied for now, but lowering them to a more sane value may improve performance at no visual cost.

Share this post


Link to post
Share on other sites

I'm still tweaking to find out what the best values are... the values that show the best detail at the least performance cost. Bethesda just threw high values in the similar settings, which I have copied for now, but lowering them to a more sane value may improve performance at no visual cost.

Yeah I figured. I can't imagine how many hours you've put into testing all of these settings, thanks again for all your hard work :)

Share this post


Link to post
Share on other sites

Hey,

 

"By default, Skyrim will render 20 skinned trees around the player character."

 

We can increase the amount of skinned trees rendered around the player.

 

uiMaxSkinnedTreesToRender=200"

 

If I am right that value put more objects (trees) around my player.

I am a little afraid of some kind of side effect:

 

- Performance (not just FPS, but also higher VRAM usage + more stuttering)

- and clipping trees?

 

I use SFO and I am a little afraid of CTDs because of more SFO trees and also more stuttering.

 

How about these ones?

 

Thank you!

 

Ps: But the default value is not 40 instead of 20?

O, and one more thing. Using these values with DynDOLOD medium preset, which settings do you recommend?

 

fTreeLoadDistance=40000.0000
fTreeLoadDistance=25000.0000

Edited by kranazoli

Share this post


Link to post
Share on other sites

It doesn't put more trees around the player. It just skins them, i.e., gives them better detail. It will indeed have a performance impact, which I mention. Clipping trees? Not sure what you're trying to say there. It does not add trees. That was SpeedTree, which wasn't used in Skyrim.

 

The default value is 40, but everyone has 20 in their INI since that's what all the presets have.

 

There are 4 choices:

 

  1. Use dynamic unskinned trees
  2. Use dynamic skinned trees with tree popping
  3. Use dynamic skinned trees without tree popping
  4. Use static skinned trees

All of these except option 4 can have animated or inanimate trees of course. Option 1 has the best performance. If you think trees look fine unskinned, by all means do so. I'm not sure whether option 3 or 4 is the most performance costly.

 

fTreeLoadDistance? Set it to whatever you like. I'm more of the playing type, i.e., don't stare too much at distant scenery, so I'm more apt to stick with the smaller value.

Share this post


Link to post
Share on other sites

It doesn't put more trees around the player. It just skins them, i.e., gives them better detail. It will indeed have a performance impact, which I mention. Clipping trees? Not sure what you're trying to say there. It does not add trees. That was SpeedTree, which wasn't used in Skyrim.

 

The default value is 40, but everyone has 20 in their INI since that's what all the presets have.

 

There are 4 choices:

 

  1. Use dynamic unskinned trees
  2. Use dynamic skinned trees with tree popping
  3. Use dynamic skinned trees without tree popping
  4. Use static skinned trees

All of these except option 4 can have animated or inanimate trees of course. Option 1 has the best performance. If you think trees look fine unskinned, by all means do so. I'm not sure whether option 3 or 4 is the most performance costly.

 

fTreeLoadDistance? Set it to whatever you like. I'm more of the playing type, i.e., don't stare too much at distant scenery, so I'm more apt to stick with the smaller value.

"It doesn't put more trees around the player. It just skins them, i.e., gives them better detail. It will indeed have a performance impact, which I mention. Clipping trees? Not sure what you're trying to say there. It does not add trees."

 

Okay. So it was because of my misunderstanding that or lack of my english knowledge. I thought this settings put more trees around my character and not "'just" more detailed trees. That was the clipping trees theory. Now, I see.

 

Is there a "huge" difference between 40 and 200? And can I use these values with SFO as well?

 

"The default value is 40, but everyone has 20 in their INI since that's what all the presets have."

 

Yes, but after I read that the default value is 40 and the launcher for instance change this value to 20, I switched back to 40.

 

The more settings I will try out and choose which one is the most suitable for me, but now everything is clear. Or at least, I hope so. :)

 

Thank you!

Share this post


Link to post
Share on other sites

There probably isn't much difference between 40 and 200. I need to start tree counting to get a better number, and I'm lazy. Since the setting is only for the "maximum" amount of skinned trees, you can probably with safety set it to 10000000 and not get much of a difference. I just used 200 since it would be easy to add an extra 0 to the 20 that will already be there, and I noticed no tree popping with 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 DoubleYou
      Step Wiki Users Guide
      Guide Thread  
      This thread is for discussion and improvement of the Step Wiki Users Guide on the wiki.
       
    • By z929669
      @boycad
      Let's discuss your guide work here. It looks like you want to create an unofficial guide based on your own personal vision. This is totally fine, and you can do that using the Step guide infrastructure. Again, this benefits you and other curators (like us) in the long term.
      In response to your reply on the wiki: "badges" that I mention have nothing to do with the wiki or Wikipedia. It's just a forum group you would belong to "Fallout4 Curator" that would give you and others that curate FO4 guides permissions to do certain things on the forum and wiki to support that. It is also a label that all members can see so they know that you are an 'authority' on such matters.
      First step is to create your wiki mod pages as described on all the threads I linked on your wiki Talk page. I am also in the process of creating a guide for curators, but that will take a week or two.
    • 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
      Download
      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. Use this if a mod manager with a virtual file system (like MO) is used.
      Do not generate into any game or any mod manager folders that are part (direct or indirect) of the virtual file system.
      Requirements
      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.
      Noise
      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.
      Test-Terrain-Tamriel.7z
      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.
  • 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.