(05-13-2014, 05:37 AM)Bighead Wrote: neobrain, if you don't mind I have a few questions regarding the matter. I won't even pretend to understand how texture dumping/loading works in Dolphin. So excuse any ignorance I display with them. I'm hoping you can help me to understand.Yes.
First, I'm assuming by your post that changing the accuracy affects the outcome of the file names?
(05-13-2014, 05:37 AM)Bighead Wrote: Second, if it does, how does Dolphin know to load the correct file names? (Actually you can just skip this one if you don't want to explain.)Whenever a game is loading a texture from a chunk of RAM data, we create a hash from that (tl;dr: we generate a number from the texture data) which is hopefully unique enough to identify each texture. We generate the hash by picking a few random(-ish) texels from the texture and performing some cryptography on them. The number of texels involved in that calculation is exposed in the GUI as "texture cache accuracy". The generated hash is used for the filename used when dumping or when loading custom textures.
Point is: If you pick too few texels, you end up with identifying different textures with the same hash, but if you pick too many texels performance suffers.
(05-13-2014, 05:37 AM)Bighead Wrote: No need for a solid technical explanation, throw a "googoo gaga" at me if possible. Considering this happens at all, to me it seems that Dolphin is searching for a specific name to replace a texture with. Unless there are multiple names that could fit that hole? I'm a bit confused because I don't have a clue in the least how any of it actually works.googoo gaga. Hope this was helpful :p Don't hesitate to throw more questions at me.
Soo guys, what do you think about forcing texture cache accuracy to safest when texture dumping or custom texture loading is active? That might slow down things drastically, but it's ultimately the only good solution we have currently.