11-18-2010, 03:11 PM
That's actually what has become the default .obj exporter from at least Max 2009 forward interestingly enough.
The ONLY downside is that it doesn't do relative paths for textures so you have to edit that in your .MTL file if you want the textures to show up on import. I didn't realize this for some of my early models so a lot of my early rips have this issue, but its not really major and just takes 2 seconds to fix after import so I wouldn't force you to fix it.
Basically it makes it so that Max looks for textures in "C:/Users/Whoever/Documents/Your Model folder/" rather than the folder its currently in. Not really a big issue since it keeps the Materials intact and still gives you the original names of the textures though.
And yeah, your model imports fine now otherwise. Good job with it.
The ONLY downside is that it doesn't do relative paths for textures so you have to edit that in your .MTL file if you want the textures to show up on import. I didn't realize this for some of my early models so a lot of my early rips have this issue, but its not really major and just takes 2 seconds to fix after import so I wouldn't force you to fix it.
Basically it makes it so that Max looks for textures in "C:/Users/Whoever/Documents/Your Model folder/" rather than the folder its currently in. Not really a big issue since it keeps the Materials intact and still gives you the original names of the textures though.
And yeah, your model imports fine now otherwise. Good job with it.