TexFix Mod 1.12.2 (optimizes computer RAM)

TexFix Mod 1.12.2 is a mod that removes unwanted TextureData from ram - Minecraft loads all textures after GPU compilation and uses them there, but duplicate textures remain in ram and waste memory, so this tool Clears duplicate textures. This tool saves a lot of data that would otherwise be wasted, especially when using texture packages. In addition, this tool depends on the specific client. It is also compatible with 99.999% of mods (even with FoamFix).

Effects can take up 1 MB for the entire game, as well as 10 GB for mods using high-textured sprites and a variety of textures. In addition, mipmapping levels increases the memory used by the selected level by + 1x. For example, if you use 4th level mipmapping to save 300 MB of memory, you will save up to 1.5 GB of memory.

How it works:

After downloading, the mod looks into the texture manager and removes all non-animated sprites from RAM to reduce the amount of RAM used.

This has no effect on the game of vanilla Forge. However, mod packs usually have more textures, and I've seen packs with 40,000 textures. Here is an example:

1.10.2 vanilla Minecraft contains 729 textures (1.12 - 795) and does not contain animation.

So here's a list of how much you can save:

16x textures = 1KB per texture = 729KB vanilla = 5MB for 5k textures = 39MB for 40k textures

32x textures = 4KB per texture = 2.8MB in vanilla = 20MB in 5k textures = 156MB in 40k textures

64x texture = 16 KB per texture = 11 MB in vanilla = 78 MB in 5k textures = 625 MB in 40k textures

128x texture = 66 KB per texture = 46 MB in vanilla = 312 MB in 5k textures = 2.5 GB in 40k textures

256x textures = 262 KB per texture = 182 MB in vanilla = 1.2 GB in 5k textures = 10 GB in 40k textures

512x textures = 1MB per texture = 729MB in vanilla = 5GB in 5k textures = 40GB in 40k textures

Of course, this assumes that all textures have a certain size, but even if there is a mixture, this data is still there and does nothing, saving a little memory! Because they are already in the GPU and used there. These effects are also enhanced if mid-mapping is used. You can expect to save more memory when using mid-mapping because it creates duplicates to generate this data (this does not appear in the log).

After loading the texture, the tool log will show: X number of fixed textures, Y number of saved MB (Z number of bytes).