@Leotichidas
Yeah, sorta wrong. The 128 byte header isn't from the res folder. It is a one that identifies a texture and its atributes. All DDS texture files have a 128 byte header. In that 128 the texture format(there are a lot of different formats out there), width, height, etc are specified. You were on the right track. That chunk file you found. That IS THE TEXTURE. It is just missing the 128 byte header with the DDS information and the file extension DDS.
See.
http://gyazo.com/2951968d0438cfdb58da7e04678e797c It definitely a texture I just don't know what format and size. I used to know how to figure out the format and size from the chunk file itself. If i remember right the size of the chunk can tell you what file format and dimensions of the texture, thus the 128 byte header. Hmm....that chunk file is quite big...I have a few of the common chunk sizes and corresponding DDS headers but that chunk file is double the size of any chunk size I have information on in my script. There might be something else going on or it might just be a really big texture. No more old consoles, now more low res textures??? IDK i'll look into it. That might have just so happened to be a bad texture to grab for an example.
OH yeah, the texture tool that is in the screenshot.
Download TextureFinder.v21.zip from Sendspace.com - send big files the easy way Its pretty useful for stuff like this.
PS. If you find a res file and you get the chunk files name from it but can't find it in either chunk folder they might have used the same obfuscation techniques they did for some BF4 textures/audio. So if the res says chunk is 5f1884a69186ad05a810e63693330f8b
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
5f 18 84 a6 91 86 ad 05 a8 10 e6 36 93 33 0f 8b
You would then need to but the bytes in this order
3,2,1,0,5,4,7,6,8,9,10,11,12,13,14,15, 16
and that would be the chunks name. ....I think I don't know if I remember that right. Its been a while.
PPS. Sorry if that made little to no sense, I'm not great at explaining things like this some days.