can't load textures to shader because of AEfileTemplate and no mentalray

can't load textures to shader because of AEfileTemplate and no mentalray

Anonymous
Not applicable
739 Views
1 Reply
Message 1 of 2

can't load textures to shader because of AEfileTemplate and no mentalray

Anonymous
Not applicable

Just keeps getting better. I have nothing in the scene related to mentalRay anymore ( scene from Maya2014 opened now in maya2017). Trying to change the texture on a regular ole Maya shader and get this error when opening the file:

Error: file: C:/Users/DELL/Desktop/Perry v Kia/Girl2.ma line 85: Unable to dynamically load : C:/Program Files/Autodesk/Maya2017/bin/plug-ins/Mayatomr.mll
The specified procedure could not be found.

and when actually trying to reload the texture ( after altering it in Photoshop) on the maya shader it won't let me because of this lovely error:

Warning: file: C:/Program Files/Autodesk/Maya2017/scripts/AETemplates/AEfileTemplate.mel line 978: Unknown object type: mentalrayTexture //

Ok..you don't want us to use mentalRay anymore but I am just trying to use the maya software shader. I see NOTHING in my tiny scene of mental ray. No materials, no shader groups. Is the file just corrupt now because it did at one time have a mentalray affiliation

 

740 Views
1 Reply
Reply (1)
Message 2 of 2

Anonymous
Not applicable

Update:

deleting prefs got my hypershade window to appear again. And redoing all the prefs I have set wasn't so hard the second time around. edited out some code in the AEfileTemplate.mel  to stop one error and I can now hit the "reload" button on a texture shader rather than navigate to reload it. Also found that Optimize Scene/delete unknown nodes clears out mentalRay ghosts so I can open the files again without the pop up warnings. Getting there, putting out one fire at a time. Some of the lines hardcoded into scripts concerning mental ray are nothing more than a heads up, while others have been interfering with basic functionality. I see light at the end of the tunnel - hopefully not the headlights of an oncoming semi. Once I start creating NEW files rather than opening 2014 files I think things will be fine