Fantastic! You spoil us - thank you!

Wooty woot! 😁

I just want to update Lara home level so I made neweqiv file, but with that one I have some mixed textures .Why is that?

Hmmm! In what way mixed?

Well, some textures are replaced by others. I have Sold out version of TR and everything work fine with my original equiv. file. When I made new one (from my original and your version one) and replace original one with it, I got textures that are mixed. I haven't this problem with JC textures and equiv file in his version. Here it is.

Have you tried getting the tool to check your pack for repetitions?

The only other thing you can do really is trace what's being mixed up through the equiv file.

Well, when I generate repets.log file from my textures pack I receive file that shows many repeated textures, but when I visual compare each of them they are not the same. For example many textures of the letters are shown like they have copy in textures that are totally different of them. You can check it by yourself.

Repeats don't mean the textures are the same. It means Glidos is being told - by the mapping file and the equiv file - of mulitple replacements for a single texture.

What about if you run the test with your original equiv file?

It's the same thing. I receive the same repets.log file.

That's the problem then. The original equiv file, when used in conjunction with your mapping file is providing multiple mappings for textures.

I may be able to take a detailed look later.

The eror has been caused by equiv file. It seams that Glidos mix my equiv and new one even I renamed it. So there can't be more than one equiv no mater what is it name.

Glidos will read all the files to see what's inside them. So if you can't disable an equiv file by renaming it. You need to take it out of the folder.

... sorry if that makes no sense: I may have misunderstood what you said.

Glidos will read all the files to see what's inside them. So if you can't disable an equiv file by renaming it. You need to take it out of the folder.

Exactly. It's OK now. 😀