Executables can have textures (and other files) in them, but they are directly accessed by code and thus harder to "find".
For example, Pokémon XD Gale of Darkness has some GTX textures in its .DOL file that it "loads" during startup.
Since we can't really rely on trying to search for possible textures by searching for magic values (since formats like GTX doesn't have one), maybe we would have an separate table that for a given executable (identified by file size and some hash) it would show where a texture is located in and what format (via filename?), so that those can also be extracted.
Executables can have textures (and other files) in them, but they are directly accessed by code and thus harder to "find".
For example, Pokémon XD Gale of Darkness has some GTX textures in its .DOL file that it "loads" during startup.
Since we can't really rely on trying to search for possible textures by searching for magic values (since formats like GTX doesn't have one), maybe we would have an separate table that for a given executable (identified by file size and some hash) it would show where a texture is located in and what format (via filename?), so that those can also be extracted.