That's probably due to how stupidly Dolphin assigns a hash to a texture. Unfortunately the alternative is breaking all texture packs.
Custom texture issue report thread
|
04-28-2014, 07:20 AM
It seems like turning the texture cache accuracy to "fast" made it more likely that the custom texture would load instead of the default texture. I tried on each setting; on safe, custom textures never loaded, halfway, custom textures sometimes loaded, and on fast, they almost always loaded. Almost. Was this already known (which would mean that I'm really just spewing), or did I actually do something useful?
in a perfect world we would all be piles of sand with no ability to form coherent bodies of body
Unfortunately, it's the opposite result for me: If I switch the texture cache to anything other than safe for this particular texture pack, almost every custom HUD texture stops loading.
I believe the texture pack creator may very well have had some issues with getting the hashes right, but everything I did should have corrected that for the safe texture cache accuracy. I may dump some textures with the cache accuracy set to fast, then use those hashes instead to see if there's any improvement. Also, this only affects the HUD, which would be loading/unloading textures several times throughout the game. Static textures in the world always work without any problems whatsoever. The Texture Format Overlay option sure is fun for that since the default textures will be stamped with their encode information, haha. I'll toy around with the hashes generated from other settings for a bit. With any luck, that will work and I'll be able to fix the texture pack by spending a few hours generating the hashes and renaming the custom textures. *EDIT* I'm beginning to think there's something funky going on with the way that Dolphin hashes the item icons in Wind Waker. It seems like I get new hashes almost every time I boot the game. This is what my boomerang custom texture folder looks like, and it's still not able to load the texture with 100% consistenty. I had it working about 80% of the time with texture cache set to fast, but it would still break if I switched the boomerang out completely and then swapped it back onto the buttons. 04-29-2014, 02:17 AM
Although I've mentioned this several times, and lots of texture packs state they'll only work with one cache accuracy, I've been shot down, and so have others, when we've pointed out that changing the cache accuracy sometimes, but not always, changes the hashes assigned.
My testing of this boils down to when I downloaded razius' SMG HUD pack, and did whatever I was supposed to to get EU textures, they mostly didn't show up. I then renamed a tonne of files to match my dumps, and they started appearing. When I mentioned this to razius, wondering if there was a way to accelerate my manual renaming of things, he said his pack only worked with safe cache accuracy, so I should use that. When I switched to that, all the textures I hadn't renamed showed up, and I'm pretty sure none of the names I did rename did. Anyway, whether this is now generally accepted or not, it could explain some of Kodiack's duplicate textures.
OS: Windows 10 64 bit Professional
CPU: AMD Ryzen 5900X RAM: 48GB GPU: Radeon 7800 XT
People have been shot down multiple times because people keep mentioning stuff like what you just said over and over again without giving easy and precise steps to reproduce the issue. Randomly dropping those notes in a forum thread (even if it's this one) is completely useless to me because I don't want to spend an hour debugging issues that are either invalid or already known. And then particular people (aka: you) keep effectively complaining about how I don't want to waste my time on that, which reduces my motivation on spending any time on it even further.
Either way, I did come to realize that people would probably be more successfully if I not only said that I want reports which don't waste all of my time, but actually explained to them how to do that. So here you are: 1. Delete the "Dump/Textures/00000000" and "Load/Textures/00000000" folders in your user directory if those folders exist. 2. Disable texture dumping and custom textures. 3. Go to a particular scene in which you experience issues with custom textures. 4. Record a fifo log of that scene using instructions on http://wiki.dolphin-emu.org/index.php?title=FifoPlayer . Note that (as explained on that page) you should disable XFB emulation and EFB copies emulation during recording. 5. Close the emulator window; restart Dolphin. 6. If you disabled EFB copies before, you may re-enable them now. 7. Load the fifo log using the instructions on the wiki. Depending on the type of issue you're experiencing, you may do different things now. Say you're having issues with loading a particular custom texture. Then: 8. Enable texture dumping. Let Dolphin dump some textures, then close Dolphin. 9. Locate the texture which was having problems previously. It'll be stored in "Dump/Textures/00000000". 10. Copy that texture to "Load/Textures/00000000" and modify it. Or if you're using a particular custom texture pack, put the corresponding texture in that folder, but take care to use the proper filename (the first few characters will need to be changed). 11. Disable texture dumping, enable custom texture loading. Start emulation 12. Check if the issue can be reproduced this way. If it can, upload debugging information to a good file hoster (i.e. one that doesn't limit download speed to 50 kbps AND which won't remove the file within few months AND which doesn't require me to whitelist javascript on anything but the top domain) - debugging information is a) the fifo log you recorded b) A single or a few example textures (NOT more than 10) which are causing problems, with their correct filename c) if it's not obvious to even the blindest people, explain where I need to look for the custom texture (actually, screw that "if". Explaining it no matter how obvious it is will save needless confusion) So... yeah, that's pretty much it. 04-29-2014, 04:50 AM
That's actually a lot more helpful. You can't exactly expect the average forumite to know that's what you want if you ask for steps to reproduce the issue and a link to the texture pack - most of the time on the forum, detail just means details of any non-default settings, and which bit of the game you have to get to (and only if it isn't every single frame since the wrist-strap instructions which has the problem. Anyway, I don't have time right now, but I'll try and get you the right FIFO logs at some point in the future.
OS: Windows 10 64 bit Professional
CPU: AMD Ryzen 5900X RAM: 48GB GPU: Radeon 7800 XT
... whatever, creating this thread was a waste of time. I wish some people had followed my first post more closely and at least tried to think a bit what I was talking about rather than being like "huh, whatever man, any report is better than none". Anyway, thanks to anyone who tried to help, I guess. Particular thanks to those who did bring up good reports, even though I was not able to work of them due to a lack of access to the affected games.
Closing this thread. If anyone wants to see an issue related to custom textures solved: Create an issue here, but make sure to thoroughly read this first, and then put some more thought into how to save the developers some time, thanks. (do note that this is not a direct reply to the previous post, which was written almost two weeks ago anyway) |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)