Texture Dumping/Loading Troubles

[ThorhiantheUltimate]

Hey guys, I just needed to ask a question about the system for dumping and loading textures.

So, Ive dumped, edited, and loaded a few textures before for a game or two in dolphin in the past, and lately I decided to start messing with Custom Robo again. In the past I was successful in loading my edited textures, but right now I can't seem to get my custom gun texture to load at all.
I first tried to do this in linux (on version 4.0-608, I compiled it from source on Arch Linux), but the custom file never got loaded (I double checked that the option was enabled). The game ID for the folder was correct (GXCE01) and I compared the texture's name to the original dumped file and they were the same. After zero success, I attempted to try it out in windows with no success. I redumped the original in the windows build (4.0-607) and it gave me a different name for the texture ID. I changed the custom texture's name to this new name, but it still refused to load in game. I tried stock 4.0.2 and I had the same result.

Everytime I tryed I made sure that the option was checked on, and that it was inside of the textures folder in the load folder of Dolphin's directory. These dumps have all come from my fully functioning CR US Dump.

I just wanna say thanks in advance whether or not anyone can help me lol.

-Edit: Oops, posted in wrong place, thanks for moving it to support

[degasus]

Have you changed the texture hash accurency? I know it's dumb, but the name of this custom texture is different per setting.

[ThorhiantheUltimate]

(01-21-2014, 08:22 PM)degasus Wrote: Have you changed the texture hash accurency? I know it's dumb, but the name of this custom texture is different per setting.

No, I haven't changed that setting. I will check for differences when I get home later today.

[neobrain]

Try redumping your textures without changing the "Dump textures" option while running the game. In other words, enable "Dump textures" before running the game and leave it untouched after.

[ThorhiantheUltimate]

(01-22-2014, 03:39 AM)neobrain Wrote: Try redumping your textures without changing the "Dump textures" option while running the game. In other words, enable "Dump textures" before running the game and leave it untouched after.

I did do this after I found that already loaded textures do not dump (probably because they get intercepted at a certain point in the loading process?) I'll try again for you Neobrqin, lol. I won't be home for a few more hours unfortunately. I'll post my results then.

[ThorhiantheUltimate]

So, I tried everything you guys recommended. It never worked. So basically, I am getting different texture names across Windows and Linux (Unless something changed between revisions 607 and 608 that would cause the name change, since Arch is running 608 and Windows is using 607 and stock 4.0.2).

Weird thing is, I went ahead and double checked the names again, they were the same. I went ahead and retyped the name here in windows, and to my surprise, with the same name, it finally worked. I wonder whats going on here on my side XD. Ill check on Linux here in a sec, I have to reboot.

-Edit, not switched into linux yet, but im going to grab a ToS texture pack and see if it works in the Linux Build.\

-Linux Update: I have went ahead and loaded the ToS texture pack into Arch Linux, it works :/ ALso, after re dumping (I NEVER changed any settings, just the check box for dump texture/ load texture when needed, and texture Cache setting was the same as Win7) I got the same ID that I did from windows. I went ahead and retyped the name for the texture, and it did not work. I triple checked, and retyped several times to no success. I went ahead and copied the name and pasted it onto the custom texture file's name, and it proceeded to actually work. Im wondering if GNOME is screwing with me right now.

I still can't figure out why Dolphin was giving me different texture IDs earlier....

[pauldacheez]

>I still can't figure out why Dolphin was giving me different texture IDs earlier....

The game probably has a certain texcache setting in its .ini; opening the Graphics config switches it to whatever you have set. I wouldn't know how that affects it when you have dumping enabled, though.