Maya 2017 / 2018.1 -> File Path Editor issue

[SEQUENZ | Gerstenmaier]

Hi,

we have a strange issue with the File Path Editor (FPE) in Maya 2018.1 (but also in Maya 2017) under Windows 7:

When we are logged in as a normal user, the FPE shows „green light“ wether the paths of the textures in the scene are available/exiting or not. It is also not possible to repath any texture („Repath currently resolved files“ is checked) - it simply just happens nothing. When we log in as Administrator everything works like expected. 

First thought that it is a file permission thing as the files all come from a co-worker. But it is the same when I create a totally new scene, add a texture to a material and change the name of the texture on the hard disk. Still everything green in the FPE! It also has nothing to do with VRay as it is the same with a Phong shader.

Does anyone has any idea why this is happening?

Or anyone knows a May 2018.1 compatible repath script?

Thanks,

Lars

---

SEQUENZ, Berlin I con...@sequenz.com I +49 - 30 - 610 739 61 | www.sequenz.com | https://www.linkedin.com/company/sequenz

[Steve Davy]

File Texture Manager is still my go-to. Not sure if it works with 2018 though.

---

From: maya...@googlegroups.com <maya...@googlegroups.com> on behalf of SEQUENZ | Gerstenmaier <gerste...@sequenz.com>
Sent: Tuesday, October 10, 2017 9:46 AM
To: maya...@googlegroups.com
Subject: [maya_he3d] Maya 2017 / 2018.1 -> File Path Editor issue

 

--
You received this message because you are subscribed to the Google Groups "maya_he3d" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maya_he3d+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[SEQUENZ | Gerstenmaier]

Hi Steve,

thanks for the reminder. Thought that this old dinosaur doesn’t work anymore. But it is still pretty alive after a little modification:

https://www.youtube.com/watch?v=7BRunKHiv6M

Attached is the modified version which works like a charm with 2018.1

Crazy that the native function doesn’t work like that. 

Lars

[Steve Davy]

It's still working in 2016.5 (though you do get that "Try It" warning every time). I will download the modified version -- glad it's still functional.

I'd also highly recommend Morgan Loomis's Python scripts for executing MEL and Python scripts within Maya. They create custom menus within the UI, making organizing and running external scripts like FTM massively easier than any other method (e.g. shelf buttons) I've found.

Shout out to Morgan!

---

From: maya...@googlegroups.com <maya...@googlegroups.com> on behalf of SEQUENZ | Gerstenmaier <gerste...@sequenz.com>

Sent: Tuesday, October 10, 2017 10:36 AM
To: maya...@googlegroups.com
Subject: Re: [maya_he3d] Maya 2017 / 2018.1 -> File Path Editor issue

 

Hi Steve,

thanks for the reminder. Thought that this old dinosaur doesn’t work anymore. But it is still pretty alive after a little modification:

https://www.youtube.com/watch?v=7BRunKHiv6M

FTM Reconecting Multiple File Textures www.youtube.com Save a lot of time and headaches when rendering in a local or cloud render farm. In this Tips & tricks video John Paul Giancarlo will show you how to identif...

Attached is the modified version which works like a charm with 2018.1

Crazy that the native function doesn’t work like that. 

Lars

--
You received this message because you are subscribed to the Google Groups "maya_he3d" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maya_he3d+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

---

SEQUENZ, Berlin I con...@sequenz.com I +49 - 30 - 610 739 61 | www.sequenz.com | https://www.linkedin.com/company/sequenz

[Steve Davy]

Speaking of which, can anyone tell me why a line of MEL in my userSetup.mel file that worked in 2016.5 no longer works in 2017 and 2018?

The line is to call Morgan's script UI script:

python("import ml_toolbox;ml_toolbox.main()");

Previously putting this into userSetup.mel would auto load it at Maya startup. It no longer works this way, although if the same code is run from the script editor, it loads correctly.

I have another script in the same file to load Deadline client, which is working, so the file is being read.

---

From: maya...@googlegroups.com <maya...@googlegroups.com> on behalf of Steve Davy <stevi...@hotmail.com>
Sent: Tuesday, October 10, 2017 11:56 AM