Textures Packs Combining

[nilllzz]

So possible fix that in future?
Or bigger quality textures will always require to be at top?

There's nothing to fix cause it's not a bug.
The problem you are having are the different resolutions for the same textures from different ContentPacks (=> extensions.dat are overwriting).
The extensions from all ContentPacks are loaded before anything else is happening, and then the textures are loading in the order of the ContentPacks in the menu. That means is going to take the texture from the first ContentPack it finds the texture in. If it finds it in a lower resolution ContentPack but defined by the extensions.dat from a higher resolution ContentPack, it tries to load much larger textures that are not existing in the smaller ContentPack. Likewise, it will result in some cropped and cut out versions of the larger texture pack if that one is in front but the smaller ContentPack defines the extensions.

You really need to do a case-by-case test if the ContentPacks are compatible. This is ONLY an issue though when the resolutions of defined textures that are existing in both ContentPacks are different.

 

[SViper]

There's nothing to fix cause it's not a bug.
The problem you are having are the different resolutions for the same textures from different ContentPacks (=> extensions.dat are overwriting).
The extensions from all ContentPacks are loaded before anything else is happening, and then the textures are loading in the order of the ContentPacks in the menu. That means is going to take the texture from the first ContentPack it finds the texture in. If it finds it in a lower resolution ContentPack but defined by the extensions.dat from a higher resolution ContentPack, it tries to load much larger textures that are not existing in the smaller ContentPack. Likewise, it will result in some cropped and cut out versions of the larger texture pack if that one is in front but the smaller ContentPack defines the extensions.

You really need to do a case-by-case test if the ContentPacks are compatible. This is ONLY an issue though when the resolutions of defined textures that are existing in both ContentPacks are different.

Roger that.

 

[nilllzz]

Roger that.

The problem really is that the game doesn't know what to do in the end because you would be throwing textures of different resolutions at it. Then it looks at the exceptions.dat and sees "ah, I need the large resolution" and tries to load a texture that has a large resolution. Problem is that in your cases with the missing texture, the small texture ContentPack is being prioritized, and having the texture in the same path resulting in the game loading that texture but with the wrong resolution.

This is why you should either not have textures in two differently sized ContentPacks, load them in the right order, or not use differently sized ContentPacks together at all.

 

[SViper]

The problem really is that the game doesn't know what to do in the end because you would be throwing textures of different resolutions at it. Then it looks at the exceptions.dat and sees "ah, I need the large resolution" and tries to load a texture that has a large resolution. Problem is that in your cases with the missing texture, the small texture ContentPack is being prioritized, and having the texture in the same path resulting in the game loading that texture but with the wrong resolution.

This is why you should either not have textures in two differently sized ContentPacks, load them in the right order, or not use differently sized ContentPacks together at all.

Roger that.