Jump to content

DoubleYou

Step Admin
  • Content Count

    4,943
  • Joined

  • Last visited

Community Reputation

19 Great

About DoubleYou

  • Rank
    Wiki Stepper

Profile Information

  • Gender
    Male
  • Favorite Mod
    SkyUI

Contact Methods

  • Discord
    DoubleYou#5815
  • Nexus Mods
    Vuud

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have an issue sometimes where there is a weird overlay on the map menu. It seems like it might be connected to weather, but I'm not sure. It only happens sometimes, so most of the time it isn't an issue. Does anyone know what this is?
  2. I see that the 2.0 settings have mipmaps used for lod4 and lod32 but none of the others. I might understand for lod4, but why lod32? In my testing, adding mipmaps to the lod textures actually increased VRAM consumption.
  3. It isn't a waste of resources because you will not see any lod32 anywhere except for the map, and there are so few textures used for lod32, the VRAM difference is splitting hairs. For all of Tamriel, it is merely 16 diffuses and 16 normals -- 32mb VRAM @ 1k resolution. Versus 8mb VRAM @ 256.... I don't think anyone is needing the extra 24 mb that badly. Actually, the vanilla game uses 2k textures for lod32. Edit: The vanilla game uses 256 for lod32. I'm not sure why the xLODGen hover says it uses 2k.
  4. This was unclear to me, as I mentioned in my first post on the subject. I'll have to compare using the 2.0 settings. The banding I mentioned on Discord on the map? If so, that is unrelated. I'm unsure of any other banding you may be referring to. I'm at 2560x1080, as are my shots, which will actually become smaller for you guys. 1024 would probably be ample on HD. For me, I appreciate the extra detail of 2048.
  5. xLODGen settings used as described in the current STEP 1.0 guide. This baseline uses lod4 @ 512, lod8 @ 512, lod16 @ 256, and lod 32 @ 512. Compares: In-game LOD as seen from the top of High Hrothgar looking down toward Windhelm Map TLDR: I recommend setting lod16 to 512 resolution and lod32 to 2048 resolution.
  6. Not currently. The beta version gets close. It will not modify any setting unless you change it, but it will remove any ini setting that is invalid, and it will sort your ini file. Comments will remain on the beta version. Otherwise, you will need to make the edits manually, which would seem to be within your capability.
  7. I'm still working on getting the best solution to this. Currently tweaking DynDOLOD generation to a lower standard from high, as the entire reason this stuttering exists is because the grass lods in lod4 are just so dang expensive. Sacrificing some firstborn lods in lod4 and tweaking down the density of grass lod is my plan, but I need to do a lot of experimenting to figure out and understand exactly how this all works. Another thing I might try is making lod4's primary existence be for grass lod, and turning down the TerrainManager setting (fBlockLevel0Distance) for it low, maybe just 9 cells ~36864, and making lod8 higher quality to make up for the loss of lod4 distance.
  8. I think we should at least increase the size of lod32 so that the map can benefit. It won't really show up in the worldspace anyway.
  9. Despite the content pointing to this thread, our guide xLODGen settings differ between the current guide and the dev guide and the settings I am seeing in this thread. Also, is it just me, or does the texture size recommendations seem random? I would think that the higher level LOD should, generally speaking, have a larger resolution than the lower level LOD to account for the effective doubling of their respective sizes (e.g., 4 lod4 squares fit in 1 lod8 square, so for the resolutions to be equal, the size would double for each lod level).
  10. Yeah, I was getting some huge frame drops from NGIO today. I normally stay very close to 72fps, but it would suddenly dip down to 35 for a second because of loading all the extra LOD, which is not okay. I'd rather not even have grass LOD if I have to endure that kind of issue. I was able to tweak my INIs down to where the dip would only hit 50 fps every once in a blue moon, which is somewhat acceptable, but I'm not even on an ENB and having that kind of issues on rather good hardware.
  11. You just gotta keep lowering LOD settings until it disappears, or lowering the settings for the generated LOD. NGIO is very performance demanding. I have big frame drops myself if I don't play along.
  12. I just looked into this a bit. It seems that with the new Grass LOD loaded into Object LOD, some systems will not be able to quite keep up with the generally accepted TerrainManager settings used by most people. These settings can be tweaked within the DynDOLOD MCM menu, and the most important one is the first block distance. [TerrainManager] fBlockLevel0Distance=35000 fBlockLevel1Distance=70000 fBlockMaximumDistance=250000 fSplitDistanceMult=1.5 Tweaking these settings, especially the first one, will help users the most with their new Grass LOD performance. Just some quick tweaking on my setup, I changed mine to the following, and I'm getting much better performance. I'll be playing with this more to see what kind of balance I can strike up.
  13. Ok. I must be misunderstanding then. Correct path IS Data\Grass. Loaded it up the other way and no grass lol.
  14. I never knew to do this. I thought NGIO would yell at me if it was in the wrong place. I have it inside the Data\Grass folder. So the directory structure should be Data\SKSE\Grass?
  15. Ah. I didn't know that about the grid system. It's great to hear such good feedback! Keep up the good work!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.