replacing the PVRTexTool executable should work. You can see the command line arguments that we pass to the tool by printing all argv.
I did some hacked integration of etc2comp. So far it looks like etc2comp is a lot faster than our current solution in ‘Best’ quality, but slower for ‘Normal’ and ‘Fast’ (etc2comp with effort 0 is slower than PVRTexTool with etcfastperceptual).
I did not have a look at image quality at all.
Not sure yet if we will ever ship this, finding a solution that is fast in ‘Normal’ has higher priority.
I see. “Best” would definitely require a confirmation dialogue as 90% of the time it’s not even worth the time. Or just remove it, it is slow even on serious hardware configs!
By “replacing”, do you mean brutally renaming one exe to the other? Do parameter match? I didn’t investigate, but for now I think “Normal” is good enough. I should really make a comparative test between a single “Normal” and “Best” compressed image.
Yeah, replacing the exe with another. Parameters don’t match. I don’t recommend it and it will most likely break with a future Unity version, maybe even patch release. But in case you would have been blocked by this…