KaktusikCZ

two posts, both containing the same nonsense. well done you. Mate, I already explained what i meant in that second topic... The main point of my post was adding the lines to Fallout.ini and Custom.ini , not my guess that Vortex does not deploy texture mods. Please stop being toxic, unfortunatelly my solution did not work for dbsmishra but it worked for me, so atleast i tried... not being toxic. passing bad advice could be considered toxic as in you could cause even more problems getting the OP to edit allsorts of files which is simply not required. your assertion that vortex "ignores" ba2 files is simply wrong, made worse by a further assertion that it will install some ba2 files but not others. this shows a complete lack of understanding about how mod managers work and how to add mods to your game. none of what you suggested is correct, or necessary. the issue with the OP is going to be resolved by the OP eventually going back to a clean install, and following one of gopher's vortex tutorials about how to set it up and get going. it's nothing to do with ignoring some files or making wild edits that are not necessary. it's entirely down to the fact that the OP's setup of vortex isn't optimal. helping people is fine, but you need to know what you're talking about otherwise your well-intended efforts could further derail the OP and then what happens? well going on history, people will blame vortex, as they always do (read the vast majority of posts in these forums). to help, you need to be clear and correct. otherwise you're just adding to the problem. I partly agree, I am a new user of Vortex, but I have been using mod managers for a very long time now and sometimes there were problem with the activation of the mods, so it was my guess that Vortex could have the same problem. I was pretty desperate when I wrote that and of course the problem was somewhere else. Still I think that my advise about the ini files was not harmfull, as the ini file can be restored to original values and it is proven it has helped some people (it may cause longer loading times, but not in every case). I get your point and respect that, although I think i did nothing wrong.

I don´t know if you are using ENB, bui i solved my situation this way. Some of the textures were appearing very low res and some changes from texture mods did not even appear in the game. Your problem is probably different, but I will still post this message. In the end the problem was not in the ini files. The textures were not loading properly due to wrong enblocal settings, so it was a problem with ENB. I edited the VideoMemorySizeMb to 10240, which is as I had read the highest value possible (even if I have 24GB total RAM+VRAM), I sticked to the basic scheme (RAM+VRAM in Mb) - 6144Mb (for game and other processes) = ... (max value is 10240, even if the result is a bigger number) That worked for me and all textures now load properly Followed this, didn´t need to do the [general] part: https://www.reddit.com/r/FO4mods/comments/6b8wfg/enb_is_preventing_some_textures_from_loading_at/

In my Fallout4.ini and Fallout4Custom.ini I've always used an empty "sResourceDataDirsFinal=" and have never had any problems with BA2 texture files as a consequence. Frankly, I don't think this issue has anything at all to do with Vortex. Yep. Both my ini files only have the "sResourceDataDirsFinal= " And the archive section of my Fallout4Custom.ini only has TWO lines, not the same number of lines as the fallout4.ini Custom.ini [Archive] bInvalidateOlderFiles=1 sResourceDataDirsFinal= That's it. In the end the problem was not in the ini files. The textures were not loading properly due to wrong enblocal settings, so it was a problem with ENB. I edited the VideoMemorySizeMb to 10240, which is as I had read the highest value possible (even if I have 24GB total RAM+VRAM), I sticked to the basic scheme (RAM+VRAM in Mb) - 6144Mb (for game and other processes) = ... (max value is 10240, even if the result is a bigger number) That worked for me and all textures now load properly

two posts, both containing the same nonsense. well done you. Mate, I already explained what i meant in that second topic... The main point of my post was adding the lines to Fallout.ini and Custom.ini , not my guess that Vortex does not deploy texture mods. Please stop being toxic, unfortunatelly my solution did not work for dbsmishra but it worked for me, so atleast i tried...

I Sorry for misinterpretation, it was my guess and I was not talking about all ba2 files, just ba2 from texture mods (all other mods deployed through vortex work normally, just the texture mods did not appear in the game before the change in sResourceDataDirs). Taking into account the post about making sure it was deployed properly from HadToRegister about Vortex Deployment.json...

I have / had the same issue with Vortex, Tried changing the sResourceDataDirsFinal in Fallout4.ini and Fallout4Custom.ini (located in documents/mygames/fallout4) which was blank, to sResourceDataDirsFinal=STRINGS\, TEXTURES\, MUSIC\, SOUND\, MESH\ and it partially worked!!! I can see most of the textures from mods now, but I think not all of them, for example Vivid textures are not present, maybe it´s due to it being a ba2 fle texture mod, which vortex seems to ignore and not deploy. So try that, maybe it will work with every texture mod you have :-) Found it here: https://steamcommuni...12931350867828/

I have / had the same issue with Vortex, Tried changing the sResourceDataDirsFinal in Fallout4.ini and Fallout4Custom.ini (located in documents/mygames/fallout4) which was blank, to sResourceDataDirsFinal=STRINGS\, TEXTURES\, MUSIC\, SOUND\, MESH\ and it partially worked!!! I can see most of the textures from mods now, but I think not all of them, for example Vivid textures are not present, maybe it´s due to it being a ba2 fle texture mod, which vortex seems to ignore and not deploy. So try that, maybe it will work with every texture mod you have :-) Found it here: https://steamcommunity.com/app/377160/discussions/0/135512931350867828/

My solution below