Jump to content

Recommended Posts

Not sure if I somehow screwed up LOD generation, screwed up otherwise or if something is wrong with FO4LODgen but I noticed that when I load the generated files (packed into ba2s of course) along with the esps and FO4LODGen - Main.ba2 from the provided resources that some textures suddenly become really blurry when I approach an object and only after closing in further the correct textures are being loaded again. This does not happen without the generated LOD files active and the correct textures are being loaded even at a distance.

 

Here is an example of what I mean, when I fast travel to this location (Tenpines Bluff) the green steel beam textures for the bridge are relatively sharp at a distance , but once I get a little closer they become very blurry and low resolution all of a sudden as you can see here:

 

At a distance: ZbLSiEk.jpg closer up: 0nQKImd.jpg

 

 

Only when I get even closer it finally loads the textures that were present on the middle section of the bridge the entire time. Any idea what might be going wrong here? I've ran the LOD generation multiple times without different results. This effect is reproducible each time I load the game and go to this location (haven't tried others yet) and doesn't occur without the generated LOD files. My gpu's Vram is 6GB (GTX 980ti) and as you can see in the screenshots, it isn't full yet and there wasn't any more loading going on when I took them.

 

I initially ran FO4LODGen with default values (4096x4096 Atlas size, 100 Alpha, 512 max texture size, 1.1 uv and default compression settings, nothing else checked) but even changing atlas size up to 8192x8192 and max texture size to 1024 didn't change anything. Any ideas?

 

Also, what INI settings do you mean here? I know about the issue with loose texture files and what ENBoost is and how to use it, just not sure what specific INI settings you are referring to here:

 

I assume Fallout 4 modders know all about this issue with loose texture files, the involved INI settings and ENBoost.

I hope I've given all relevant information, if not I'm more than happy to provide them of course and I hope you guys can help me solve this problem :).

Edited by El_Rizzo

Share this post


Link to post
Share on other sites

Do not forget to remove the loose files after packing them into a BA2.

 

If you packed all atlas textures into a BA2 and still got this, it could be that the blurry texture(s) are not on the atlas but used directly and probably loose. You would need to check the BTO in nifskope for this.

 

AFAIK the INI settings related to this problem are bForceUpdateDiffuseOnly, iTextureUpgradeDistance0/1 and iTextureDegradeDistance0/1. In case ENB is used verify ENB memory settings are correct. There are a lot of posts for Fallout 4 and blurry textures discussing all the options.

Share this post


Link to post
Share on other sites

 

Do not forget to remove the loose files after packing them into a BA2.

I did, the output files were generated into an entirely different folder than my mods directory and I moved the 2 created BA2s (main and textures) into the mod folder manually and I made sure that they are loaded dead last (all my big texture mods are packed into BA2s).

 

 

If you packed all atlas textures into a BA2 and still got this, it could be that the blurry texture(s) are not on the atlas but used directly and probably loose. You would need to check the BTO in nifskope for this.

Like I said, all my big texture mods are packed into BA2s and I made sure that the esp loading the Lodgen output files is loaded dead last. The only texture mods with loose files are very specific and small ones, none of which have anything to do with landscape, bridges or buildings, I double checked that already :). But how would I go about finding the corresponding BTO file? Or will I simply have to open each one until I find the right one? :D

 

 

AFAIK the INI settings related to this problem are bForceUpdateDiffuseOnly, iTextureUpgradeDistance0/1 and iTextureDegradeDistance0/1. In case ENB is used verify ENB memory settings are correct. There are a lot of posts for Fallout 4 and blurry textures discussing all the options.

Alright, I knew about those before, I thought this referred to some INI tweak specifically for Fo4LODgen.

Edited by El_Rizzo

Share this post


Link to post
Share on other sites

This is a general Fallout4 problem with lots of discussions about it. I am not spending much time with FO4. When I did vanilla game tests with no other mods (meaning no physical texture folder) and putting the LOD atlas textures into BA2 it fixed for me.

 

Use player.getpos x and player.getpos y in console and divide by 4096. That will give you the cell coordinates of the area. BTOs have their LOD level (number of cells in one direction) and lower left cell coordiantes in their file name.

 

If all fails, you can try not create an atlas when generating Commonwealth/Sanctuary to see if it makes a difference. It will then use the vanilla atlas. I haven't created the default mapping for other worldspaces yet.

 

Alternatively remove all mipmaps from the atlas texture.

Edited by sheson

Share this post


Link to post
Share on other sites

 

This is a general Fallout4 problem with lots of discussions about it. I am not spending much time with FO4. When I did vanilla game tests with no other mods (meaning no physical texture folder) and putting the LOD atlas textures into BA2 it fixed for me.

Wouldn't be the first time Bethesda screwed something up regarding LOD ::D: The thing is, without using Fo4Lodgen or even with just the content from your provided resources, this blurry LOD does not occur and LOD is just fine. It is of course missing the Objects added by the generated files, but the LOD that is there doesn't get blurry, only when I use the generated files. I do use texture mods that replace the textures used for bridges, but FO4LODgen should read them, or am I mistaken?

 

But I'll try your suggestions and will report back with my results, thanks for your reply and suggestions, much appreciated! :)

Share this post


Link to post
Share on other sites

Alright, so without creating an Atlas it works as intended, the new Objects/improved LOD Objects show up and it looks like this:

 

Before:

o89slh.png

After:

 

o89slh.png

 

What I noticed is the texture resolution when I also generate a texture atlas along with the LOD objects, without the atlas the textures look like this:

 

316p9jm.png

 

When I also create a texture atlas during generation it gets blurry and looks like this:

 

2l8yr1l.png

 

 

So apparently texture atlas creation generates really low res textures that are lower quality than the vanilla ones, is there any setting to change the quality of the textures? I've already tried setting the atlas size to 8192x8192 and max texture size to 1024 with the same results. I've made sure that there are no loose files causing it, so I've really got no clue what is going wrong here :(

Edited by El_Rizzo

Share this post


Link to post
Share on other sites

So apparently texture atlas creation generates really low res textures that are lower quality than the vanilla ones.

That is not what is happening. LOD textures are not resized when put on the atlas.

 

The HWOverpassLOD_d.DDS is 256x256, so makes it onto the atlas textures regardless of what "Max texture size" drop down is set to. The "Atlas size" does not matter either. Lower sizes only mean it might create more than one atlas texture.

 

I already explained what is happening. It is caused by loose files, (default) INI or ENB settings or whatever.

 

If I remember right, removing the mipmaps from the textures can be used as a workaround. Then there are no lower resolution mipmaps the game can accidentally fall back to.

Edited by sheson

Share this post


Link to post
Share on other sites

 

That is not what is happening. LOD textures are not resized when put on the atlas.

Okay, good to know, was just an uninformed speculation on my part :)

 

 

The HWOverpassLOD_d.DDS is 256x256, so makes it onto the atlas textures regardless of what "Max texture size" drop down is set to. The "Atlas size" does not matter either. Lower sizes only mean it might create more than one atlas texture.

I assumed that was the case but since I'm a layman when it comes to LODs I was just trying different settings to see if there is any change. Just out of curiosity, is there any downside or maybe even upside to having more than one texture atlas in general?

 

I already explained what is happening. It is caused by loose files, (default) INI or ENB settings or whatever.

 

 

But I don't have any loose files that could cause it ... all the mods that contain textures affecting anything in those screenshots are packed into BA2s. I even went ahead and packed every last small mod that had any loose files left into BA2s even though those only contained textures for completely different things (eyes, super mutants etc.) and even after making sure that I have absolutely zero loose files left (I mean it, zero), the results were the same. My data folder is also squeaky clean since I'm using Mod Organizer 2 for Fallout 4 (and ran Fo4LODgen through it ofc.), so there aren't any lingering files in there either (I manually checked as well of course).

 

As for INI settings and ENB, I don't use ENB for Fallout 4 and there are no leftovers of it either and my INIs are properly set up, I have bForceUpdateDiffuseOnly= set to 0 and increased the values of iTextureUpgradeDistance1= ,iTextureUpgradeDistance0= , iTextureDegradeDistance1= and iTextureDegradeDistance0= according to the numerous suggestions on the topic like this one and the result was exactly the same and I know the ini settings were applied because the Vram usage increased by over 1GB with those values.

 

Furthermore, I even generated LOD with all my mods disabled and only the vanilla and official DLC files active + your resources files and when I load the game (still only with vanilla + Fo4LODgen related files active) with the generated output files packed into BA2s of course and loaded by one of the ESPs from resources, the result was still the same. So even with no possibility of mods interfering and properly set up INIs I get the super blurry LOD textures with a generated atlas.

 

I would be more than happy if the issue is on my end so I can fix it, but I don't see how that is the case after all the different scenarios I've ran and the fact that it even happens with vanilla only files :confusion: .

Edited by El_Rizzo

Share this post


Link to post
Share on other sites

The downside of more than one atlas are additional draw calls. It is usually negligible in this context.

 

The BA2 you are creating may have the wrong settings or options. It needs to be "DDS" format and only contain Textures. Maybe compression plays a role. Find and follow a guide how to pack textures.

 

Maybe not adding Textures\ to sResourceDataDirsFinal helps.

 

The texture format should not matter. The vanilla game use DXT1 or DXT5 for diffuse and ATI2 for normal/specular. You could also try if BC7 makes a difference, but would have to use an external tool to convert.

 

Removing the mipmaps from the atlas texture should work in any case and is probably the best option at this point.

Edited by sheson

Share this post


Link to post
Share on other sites

 

The downside of more than one atlas are additional draw calls. It is usually negligible in this context.

Good to know, thanks for the explanation! :)

 

 

The BA2 you are creating may have the wrong settings or options. It needs to be "DDS" format and only contain Textures. Maybe compression plays a role. Find and follow a guide how to pack textures.

I've read guides on how to create BA2s before, since I packed all my mods into BA2 files ;) and yeah, I selected DDS format and only the Atlas textures are in it, the meshes are in a separate BA2 with "general" as the format. I left compression for both BA2s at default and didn't touch any of the other settings as the guides recommended to leave them alone. I will try without compression for the textures BA2 and will report if that by chance solves it.

 

 

Maybe not adding Textures\ to sResourceDataDirsFinal helps.

I didn't add them to sResourceDataDirsFinal, I load the 2 BA2s via an esp (all following the naming convention for BA2s ofc) and placed it dead last in my loadorder to make sure it doesn't get overwritten.

 

Removing the mipmaps from the atlas texture should work in any case and is probably the best option at this point.

 

 

I would certainly like to try this, but have no idea how to do that :P Do you happen to have a tutorial at hand on how to remove mipmaps from the texture atlas? I don't have photoshop, but I do have GIMP with the necessary DDS plugins and also paint.net.

Share this post


Link to post
Share on other sites

I would certainly like to try this, but have no idea how to do that :P Do you happen to have a tutorial at hand on how to remove mipmaps from the texture atlas? I don't have photoshop, but I do have GIMP with the necessary DDS plugins and also paint.net.

The GIMP save dialog for DDS should have an option to generate/not generate Mipmaps. So load texture in GIMP and then save with the Mipmap option disabled.

Share this post


Link to post
Share on other sites

Yeah I figured it out myself by loading the texture into GIMP and messing around, but thanks for the fast response and help! ::): and yeah that worked, as you predicted. Also, it seems the game really doesn't like uncompressed texture BA2s, when I created an uncompressed BA2 for the atlas textures (DDS format selected ofc.) it simply would make all LOD invisible and parts of the bridge were popping in as I moved closer :turned: even B.A.E. crashed when trying to extract it, so that isn't an option.

 

Thank you so much for patiently helping me with this issue! Still weird why it happened in the first place though :confusion:

 

Oh and just in case you don't check that thread so often, I also have the issue with Fallout4 - Voices.ba2 mentioned here on the AFK forums, I have to move it out of the data folder if I wanna run FO4LODgen otherwise it crashes on me each time and my game language is English, both text and voice in case it is relevant.

Edited by El_Rizzo

Share this post


Link to post
Share on other sites

Oh and just in case you don't check that thread so often, I also have the issue with Fallout4 - Voices.ba2 mentioned here on the AFK forums, I have to move it out of the data folder if I wanna run FO4LODgen otherwise it crashes on me each time and my game language is English, both text and voice in case it is relevant.

If you have the time, what is the timestamp and exact size in bytes of your Fallout4 - Voices.ba2?

 

You need to use a windows command prompt and the "dir" command or 3rd party file managers to get the exact bytes. Windows Explorer will always simplify the number.

 

Not that important, a next version of LODGen will just skip the file, since nothing useful for LOD is in there anyways.

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
      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 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.
      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 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.
      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 DoubleYou
      Discussion topic:
      Power Armor HoloHUD by mluppov
      Wiki Link
       
      Vanilla > Fallout 4 HD Overhaul > Power Armor Hud No Transparency > Power Armor HoloHUD
       
       
  • 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.