# Multi texture obj files? [closed]

Im downloading some free 3d models off the internet to test things in my game. When I download the package, it gives me a bunch of texture files and the obj model. What I dont understand is what I do with those textures? Are they used as source image files within the object? If so how can I export the uv map of the model with all these textures on it? Ive been trying to get a working example of this and havent been able to. Can someone guide me in the right direction? I edit my files with blender, and realize this question is a little bit off topic, but im lost!

EDIT:

Example of the textures I am using now:

## closed as off-topic by Josh♦Jan 21 '15 at 16:55

This question appears to be off-topic. The users who voted to close gave this specific reason:

• "Questions about "how to get started," "what to learn next," or "which technology to use" are discussion-oriented questions which involve answers that are either based on opinion, or which are all equally valid. Those kinds of questions are outside the scope of this site. Visit our help center for more information." – Josh
If this question can be reworded to fit the rules in the help center, please edit the question.

• the obj may have material tags, it'll point to which texture to use – ratchet freak Jan 19 '15 at 18:45
• Okay, that makes sense! So I guess my real question is how can I export the uvmap to png to actually use in my code. Rather than having 5 different files? – Kyle Jensen Jan 19 '15 at 18:52
• Ive looked at some blender tutorials but cant seem to find what I need – Kyle Jensen Jan 19 '15 at 18:52

An .obj model file may come with a companion file with the extension .mtl. Such a file is a material library that contains entries mapping from a material name to properties, including texture filenames to use for things like diffuse and specular.
In your obj-file, there are mtllib a.mtl directives to indicate the material library to use, and usemtl aaaa directives to select which material in the library that applies to the next occurence of the directive, or the end of the file.