Repointing file textures

[user_deleted]

Hello:
I was wondering if it would be possible to write a MEL script to repoint all the file textures in my scene. For example... I do alot of work on Wintel machines and then render on Irix machines. When i put my scene.mb on the irix machine, it obviously doesn't know where d:projecttextures is. I would like to write a script to change this d:projectstextures to /user/blah_blah/textures/. Or is there an easier way to do this. Thanks!

rep_stosd

[klod]

Hello,

You can do that easily: save the file in ascii (.ma), take a text editor, and replace the strings.

Hope this helps,
Klod

[terraformers]

hi

you can try the script @
http://www.aliaswavefront.com/en/Community...TexturesWin.mel

there is also a nice a nice howto for the script @
http://www.aliaswavefront.com/en/Tmpl/Maya...l&style=normal#

hope this helps
lars

[gon]

It,s easy if you forget all the string until sourceimagewhatever.tga. Even if you change one path to another, if you open the poject in another PC or Silicon, the textures will not reload because they don

[gon]

It,s easy if you forget all the string until sourceimagewhatever.tga. Even if you change one path to another, if you open the poject in another PC or Silicon, the textures will not reload because they don

[glocker]

check out the mel command dirmap.

It's very useful for doing things like NT/UNIX texture path changes. Also NT/NT drive letter changes.

let maya do the remapping for you.

g-

[morrisolmsted]

I posted a script that helps with this by mimiking the Power Animater Texture Reference Editor. It is called "editRefs_2.mel" and can be downloaded from Highend3D in the Mel scripts section called Rendering and Shading.
Use the search and replace fields to find and replace any type of string. To make the replace work, simply have your curser in the replace field and hit the right most ENTER key. Let me know if it works for you.

Hope this helps

Morris Olmsted
3D Designer @ Idol Minds LLC
molmsted@idolminds.com

[coop]

I've been working on a similar but unrelated issue - in my case, I'm gathering all of the textures for a scene along with the scene file into itself, organizing it into it's own project directory, and putting it into a ZIP file.

While my MEL script was working great to do all this, every time I unpacked the file and tried to open the scene, it couldn't find the textures, because they all had full paths back to their original locations.

One would think you could just reset the .ftn attributes on the texture nodes to relative pathnames (i.e. "textures/somefile.tif"), but what I found was if I did this, Maya immediately re-translated it into an absolute pathname and stuffed that into the .ftn attribute - ack!

After inspecting some other .ma files that worked the way I wanted, I eventually discovered that if you use a full path to the texture file, but with a double '/' to seperate the part of the path that's the project, from the part that is the texture filename, it will automatically repath them when you open the scene in a new project location.

So for example, I would set my texture filenames to something like: "c:/path/to/my/project//textures/somefile.tif", and when I opened this scene from another directory location it all worked great, the parts before the // would get retranslated by maya into the location of my new project.

I don't see anything anywhere that documents this behavior, has anyone else seen a similar type of issue, or is this a known "feature"? This turned out to make my problem of moving scenes (with textures intact) from one computer to another a lot harder than I expected.

--Coop

[glocker]

Yes, that is the way maya works with the double slashes. It is documented in one of the faq's from the online docs. However, I can't find the actual doc page right now.

g-