Too much textures/files in data

[mikeeee1231]

Have you tried turning your archiveinvalidation off and then on again? I spend a lot of time pushing the game to see how far I can get and I've never seen black textures as a result of overloading it. You could also try setting EnableUnsafeMemoryHacks to false, that's what mine is set to.

I have other problems when setting it to false so that's why i left it on.

And i could try the archiveinvalidation but i'm not sure i remember how using ModOrganizer 2, any idea?

 

And do you have way above 80gb of files just in textures? Because i do, how much do you have approximatively in your texture folder?

 

 

Compressing only helps with the space taken up on disk. The compressed file still has to be unpacked in memory for rendering so it has no effect upon the video demands.

 

My suggestion would be to "optimize" all your added texture files to be the same size (1024x1024 or 2048x2048, depending upon your display requirements. Go for the smallest available without compromising visual quality. If you aren't using a 4K or very large and high resolution screen display, you aren't really going to see the differences above 2048. On smaller screens you probably can't see anything significant above 1024.) Perferrably this would be by installing a smaller image size set or by reducing their size instead of enlarging them.

 

-Dubious-

 

I use a 4k TV, but i guess it is better for them to be smaller and not as beautiful than having black textures almost everywhere.

Edited August 25, 2019 by mikeeee1231

[JimboUK]

 

Have you tried turning your archiveinvalidation off and then on again? I spend a lot of time pushing the game to see how far I can get and I've never seen black textures as a result of overloading it. You could also try setting EnableUnsafeMemoryHacks to false, that's what mine is set to.

I have other problems when setting it to false so that's why i left it on.

And i could try the archiveinvalidation but i'm not sure i remember how using ModOrganizer 2, any idea?

 

And do you have way above 80gb of files just in textures? Because i do, how much do you have approximatively in your texture folder?

 

 

 

 

I have 94GB in the texture folder, it's on an SSD through which really helps. I don't know how MO2 works, I still use FOMM. If you're using MO2 I wouldn't try using FOMM's archiveinvalidation, they may work in different ways and mess things up.

 

The reason I questioned the memory thing is I have NMC's large textures along with a load of other stuff and I was playing at 8K with 8xAA for a few hours just to see how well it ran, it was a bit stuttery which suggests the game was overloaded but no black textures.

 

How much VRAM do you have? I know the game acts up when you run out of it.

[mikeeee1231]

 

 

Have you tried turning your archiveinvalidation off and then on again? I spend a lot of time pushing the game to see how far I can get and I've never seen black textures as a result of overloading it. You could also try setting EnableUnsafeMemoryHacks to false, that's what mine is set to.

I have other problems when setting it to false so that's why i left it on.

And i could try the archiveinvalidation but i'm not sure i remember how using ModOrganizer 2, any idea?

 

And do you have way above 80gb of files just in textures? Because i do, how much do you have approximatively in your texture folder?

 

 

 

 

I have 94GB in the texture folder, it's on an SSD through which really helps. I don't know how MO2 works, I still use FOMM. If you're using MO2 I wouldn't try using FOMM's archiveinvalidation, they may work in different ways and mess things up.

 

The reason I questioned the memory thing is I have NMC's large textures along with a load of other stuff and I was playing at 8K with 8xAA for a few hours just to see how well it ran, it was a bit stuttery which suggests the game was overloaded but no black textures.

 

How much VRAM do you have? I know the game acts up when you run out of it.

 

 

I have 16gb of ram and the gtx 1080 ti so about 10gb of vram, should be enough shouldn't it? Should i grab 16gb so i could have a total of 32gb of ram and 10 vram?

 

And i wonder, does it really work to turn on and off archiveinvalidate many times? Why would it change anything? How many times should i do it?

 

 

Edit: Just to add, it is also on an SSD.

 

Edited August 28, 2019 by mikeeee1231

[JimboUK]

We have the same GPU so that rules that out and you have plenty of RAM. Toggling archiveinvalidation off and on again is a known fix for texture oddies, it might be worth asking in the MO2 comments how to do it.

[mikeeee1231]

We have the same GPU so that rules that out and you have plenty of RAM. Toggling archiveinvalidation off and on again is a known fix for texture oddies, it might be worth asking in the MO2 comments how to do it.

 

All right, I will try that, thanks for the reply.

 

But just wondering, how can toggling archiveinvalidation on and off again changes anything? This isn't the first time I hear about that, but why exactly is it like that?

[dubiousintent]

In essence: "ArchiveInvalidation" (AI) uses it's own "BSA" file mechanism to redirect the engine that normally looks to the vanilla BSAs for specific files to instead look for the "loose files" installed by mods under the "Data" folder structure. (The vanilla BSA files do not have "loose file" counterparts otherwise.) When you toggle AI, it updates the list of which files should be redirected. When you add or remove "loose files" that are supposed to replace those used from the vanilla BSAs, if the list is out of date because you failed to toggle, the redirects are wrong.

 

I say "in essence": because when I look at the Fallout.INI file list in "SArchiveList=", the AI BSA file listed doesn't actually exist as a separate file in the game Data folder. Yet with some manager implementations (specifically "ArchiveInvalidationInvalidated"), such a file does exist (at least in rudimentary form). The presence of more than one such AI filename in that list means you have conflicting implementations of AI, which can itself lead to problems.

 

-Dubious-

[mikeeee1231]

In essence: "ArchiveInvalidation" (AI) uses it's own "BSA" file mechanism to redirect the engine that normally looks to the vanilla BSAs for specific files to instead look for the "loose files" installed by mods under the "Data" folder structure. (The vanilla BSA files do not have "loose file" counterparts otherwise.) When you toggle AI, it updates the list of which files should be redirected. When you add or remove "loose files" that are supposed to replace those used from the vanilla BSAs, if the list is out of date because you failed to toggle, the redirects are wrong.

 

I say "in essence": because when I look at the Fallout.INI file list in "SArchiveList=", the AI BSA file listed doesn't actually exist as a separate file in the game Data folder. Yet with some manager implementations (specifically "ArchiveInvalidationInvalidated"), such a file does exist (at least in rudimentary form). The presence of more than one such AI filename in that list means you have conflicting implementations of AI, which can itself lead to problems.

 

-Dubious-

 

Leading to the kind of problems I'm having right now? Wouldn't the textures already be black right from the start if it was the case? I'm not sure I understand too well about this specific part but I will try it, If it does not work I will simply optimize the textures hoping it will be enough.

 

Thanks a lot for the help guys, hopefully it will help with the problem I have.