Jump to content

Recommended Posts

This is an interesting observation and it certainly makes sense given the difference in speed between hard drives and solid-state drives. I imagine this might be more pronounced on 5400 RPM drives as well given the higher rotational latency. I just checked and see I'm still using the default value since I don't have this entry in my Skyrim.ini.

If you use Unofficial Skyrim Patch, the setting is in its Plugin INI.

Share this post


Link to post
Share on other sites

Has anyone noticed a difference with bReturnTo1stPersonFromVanity? I set fAutoVanityModeDelay=5 so the vanity mode camera activates after 5 seconds, and tried this in first and third person but it always returns to the same state I was in previously. In other first, if I am in third person view I remain in third person view after I cancel the vanity mode camera by moving the mouse.

 

 

EDIT: I don't notice a difference with fVanityModeMinDist, fVanityModeMaxDist, fVanityModeMaxDistFlyMult, or fVanityModeMinDistFly. I had expected these to be affected by objects close to the player character so I tested all these by varying my distance away from Half Moon Mill -- standing against the door, at the edge of the wooden walkway leading to the door, and a couple of steps away from the wooden walkway. In all cases the vanity camera switched to the same zoom levels as the house obstructed the view. I also experimented by standing in the open and letting the vanity camera do its thing for about 10 or 15 minutes to see if it would change the zoom disatance, but I didn't notice any changes.

Share this post


Link to post
Share on other sites

You should probably have noted that these settings are in the [Camera] section.

 

Most of these settings have never been tested. Indeed, try googling some of these settings. I've been happy to notice that this guide, with as limited information as it has, is at the top of the list.

 

They most likely do something that we haven't figured out yet. Notice that the ones with "Fly" in them were added with the official 1.8 patch, which introduced Dragonborn combatibility. That is a strong hint that it has something to do with dragons, and I'm presuming perhaps when the player is mounted on a dragon, or perhaps the other settings when mounted on a horse??? Guessing. Bethesda didn't hand out a manual.

Share this post


Link to post
Share on other sites

[VATS]

uVATSRangedPercentSneak=100
uVATSRangedPercentGlobal=100

 

These values do not appear when using the configurator.

 

Trying to use the configurator and follow the guide is a bit of a pain. Configurator sorts on the second letter of the key.

The guide sorts on the first and, as a result, you have to go back and forth. This may lead to more errors when using the configurator or a text editor.

eg.

 

In the guide

 

bDrawLandShadows=0
bDeferredShadows=0
bShadowsOnGrass=0
bTreesReceiveShadows=0
fShadowDistance=0
iBlurDeferredShadowMask=0
iShadowMapResolution=1

 

In Configurator

 

iBlurDeferredShadowMask=0

bDrawLandShadows=0
bDeferredShadows=0
bShadowsOnGrass=0
fShadowDistance=0

iShadowMapResolution=1

bTreesReceiveShadows=0

Share this post


Link to post
Share on other sites

[VATS]

uVATSRangedPercentSneak=100

uVATSRangedPercentGlobal=100

 

These values do not appear when using the configurator.

And they shouldn't. Those two settings were removed from Skyrim in the official 1.6 patch. I didn't think they were popular or even known, so I decided to not even mention them. If there is a popular guide that uses them, I guess I could add these to the guide to explain that they are outdated and no longer do anything.

 

As to the Configurator, it may order the settings and sections differently, but that is at its author's discretion. The INI guide is best understood when arranged lexicographically descending, with each of the prefixes separated. The Configurator has rather randomly arranged sections and mixes up the prefixed settings.  

Share this post


Link to post
Share on other sites

Thank you for the great guide!

 

One small thing:

Set the number of CPU threads Skyrim can utilize
iNumHWThreads sets the maximum number of hardware threads the game can use. Set this to the number of cores your CPU has, doubling that number if it has hyperthreading. The default value is 4, which is perfect for quad-core CPUs without hyperthreading.

fEncumberedReminderTimer=Number of CPU cores, multiplied by 2 if hyperthreaded

There seems to be a type on this line.

iNumHWThreads only sets the maximum number of havok threads. It doesn't allow the game to be truly multy threaded as the important tasks (game logic and renderer) are single threaded.

Edited by Spock

Share this post


Link to post
Share on other sites

Thank you for the great guide!

 

One small thing:

There seems to be a type on this line.

iNumHWThreads only sets the maximum number of havok threads. It doesn't allow the game to be truly multy threaded as the important tasks (game logic and renderer) are single threaded.

Already fixed the typo.

 

And you are confusing iNumHWThreads in [General] with iNumThreads in [Havok]. The [Havok] iNumThreads setting controls how many threads havok can use, like you say, and is often confused in many tweak guides as providing more threads to the entire game. However, iNumHWThreads in [General] does indeed seem to change the amount of hardware threads used by Skyrim. In testing, I set it to 1 and 2, and Skyrim would not load on my system due to not having enough power to start up. It would freeze and stop responding. Increasing this to 3 or 4 successfully allowed Skyrim to boot up. However, I did not extensively test to see whether or not Skyrim used however many threads, but the fact that Skyrim would not load at 1 or 2 proves that it does something major. Setting it to 8, even though my system has only 4 cores and no hyperthreading, did not crash the game and acted the same as 4, so it is possible that increasing the value does nothing, but it very well might improve performance on a higher threaded system. Who knows? No one has truly tested these things.

Share this post


Link to post
Share on other sites

Setting it to 8, even though my system has only 4 cores and no hyperthreading, did not crash the game and acted the same as 4, so it is possible that increasing the value does nothing, but it very well might improve performance on a higher threaded system. Who knows? No one has truly tested these things.

What I was trying to point out was, that a performance gain is highly unlikely. Skyrim can dump some tasks (like ai, physics etc) to other cores. But at the very core, the game logic and renderer are almost certainly single threaded.

You could maybe do more rediculous things with the havoc engine but during regular gameplay the game will be limited by your single thread performance.

Share this post


Link to post
Share on other sites

Well, I presume that very well may be true, but I don't know yet. The extra threads might be useful to other parts besides the logic. All I know is it doesn't seem like it can be set too high.

Share this post


Link to post
Share on other sites

 

  • Added bShowMarkers info. Looks useful for modders. See image below.

 

 

You.

Are.

F******.

Awesome.

 

And thx for the whole guide, I've been adjusting my INI along with your progress on the matter, but stopped about 2 weeks ago. I'll probably re-do it all with all the new stuffs.

Share this post


Link to post
Share on other sites

Tired of Z-fighting mountains? Tired of terrain popping into more detail. Go back to the Oblivion terrain system! LOL.

 

Skyrim.ini

[TerrainManager]
bUseNewTerrainSystem=0

BUseNewTerrainSystem%3D1.jpgBUseNewTerrainSystem%3D0.jpg

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 Mkchief34
      I recently installed the latest Wyre Bash update, 310 Beta 1. I installed it because whenever I would try to save my Bashed Patch esp for Fallout: New Vegas, I would get this particular error message, and the patch itself does not save.
      "< not supported between instances of 'nonetype' and 'int'".
      It would also not register the masters for the patch in the screen section  beside the load order. I have reinstalled Wyre Bash, I have also deleted the previous patch (Which also had the same error), and I don't know what else to do in this case. U have some coding knowledge, but I think it won't help here.
      What should I do? I have attached a screenshot below of the error messsage itself and how no masters show up in the section for them in the GUI.

    • 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 93 - 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 or any mod manager folders.
      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 (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.
      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.
    • By Badfrog88
      I'm retruning back to playing Skyrim after a couple of years absence. I've purchased the AE upgrade and began following the guide. I chose not to use the post-processing option during this build. While running DynDOLOD this message appeared on the screen. I don't believe this is a DynDOLOD problem, but I can't figure out what I need to do to resolve the issue.  Skyrim.esm isn't a master that needs to be cleaned is it? I don't remember reading that it was.
      Any help or suggestions would be greatly appreciated. 
  • 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.