On Tue, Sep 29, 2015 at 1:45 PM Crest Christopher < [email protected]> wrote:
> Sorry I don't understand, it takes the paths as they are from the file > nodes, but it can't correctly move the files and update the file paths ? > I'm just saying that the only bit I checked out, in the source code, looked to be that is reads the value of the path from the file node and then sees if it exists. That's why I asked if it was a relative or absolute path value in the file nodes. > Justin Israel wrote: > > I don't. I haven't tested it. I've only glanced over it from a phone and > saw that it takes paths, as is, from the file nodes. > > On Tue, 29 Sep 2015 3:19 AM Christopher. <[email protected]> > wrote: > >> Justin; do you so happen to know what is wrong with the script ? >> >> >> On Sunday, September 27, 2015 at 2:01:11 AM UTC-4, Christopher. wrote: >>> >>> Yes, they are absolute paths. >>> >>> One thing I didn't mention; the tools Job is to change the file paths; >>> from what I can tell, it changed the file path but the texture files >>> themselves continue to point to the old path; basically it rearranged >>> things, without rearranging things. >>> >>> On Sunday, September 27, 2015 at 12:47:21 AM UTC-4, Justin Israel wrote: >>>> >>>> No I mean the texture paths in the nodes in Maya. Are they absolute >>>> paths? Because I can see how the tool just grabs the value and asks if they >>>> exist as is. >>>> >>>> On Sun, 27 Sep 2015 3:37 PM Crest Christopher <[email protected]> >>>> wrote: >>>> >>>>> Do you mean before I click move in the tool, does it show absolute >>>>> paths ? If so, the answer is no; only relative. >>>>> >>>>> Justin Israel wrote: >>>>> >>>>> It would be nice if the script printed the name of the path it failed >>>>> to handle, as opposed to the file node name. Are the paths in those nodes >>>>> just basic absolute paths? >>>>> >>>>> On Sun, 27 Sep 2015 12:05 PM Christopher. <[email protected]> >>>>> wrote: >>>>> >>>>>> First I Analyse Scene File Textures, in my case I have 58 textures >>>>>> that point to a folder, what I don't understand first about the script >>>>>> is; >>>>>> when I toggle on the 58 textures to be selected there are listings which >>>>>> you can check on, once again, in my case it says; >>>>>> >>>>>> 0 of them exist >>>>>> 58 of them NOT exist(s) I know they exist because they are still in >>>>>> the folder and on my desktop ? >>>>>> >>>>>> Moving along, I click the toggle option for the 58 textures, I then >>>>>> select a target directory, then click move files. This is the result; >>>>>> >>>>>> File Texture Manager Log starts... >>>>>> >>>>>> *************************************************************************************************************** >>>>>> Can_ColorLabel: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> FireKnot_Sculpt:file2: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> Guage_Spec: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> Levels_Texture: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> Paintchip: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file1: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file2: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file3: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file4: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file5: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file6: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file7: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file8: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file9: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file10: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file11: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file12: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file13: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file14: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file15: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file16: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file17: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file18: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file19: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file20: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file21: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file22: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file23: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file25: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file26: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file27: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file33: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file34: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file35: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file36: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file39: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file41: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file42: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file43: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file44: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file45: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file46: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file53: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file54: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file55: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file56: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file57: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file58: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file59: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file60: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file61: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file62: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file63: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file65: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file66: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file67: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> file69: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> p1050723_1: >>>>>> WARNING: Move can NOT be done, could be permission issue or path >>>>>> existence issue. >>>>>> >>>>>> *************************************************************************************************************** >>>>>> File Texture Manager Log ends... >>>>>> >>>>>> *************************************************************************************************************** >>>>>> >>>>>> >>>>>> >>>>>> On Saturday, September 26, 2015 at 6:52:34 PM UTC-4, Justin Israel >>>>>> wrote: >>>>>> >>>>>>> Can you paste any actual output of the error and traceback? It's a >>>>>>> whole lot of MEL code on that script ;-) >>>>>>> Could be bad path logic or something. Or maybe you are pointing it >>>>>>> at a link or network location that it can't handle >>>>>>> >>>>>>> On Sun, 27 Sep 2015 11:19 AM Christopher. <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, hopefully someone can help. I download this tool >>>>>>>> <http://www.creativecrash.com/maya/script/filetexturemanager>, >>>>>>>> it's Job is to analyse the scene for all the textures then move them >>>>>>>> to a >>>>>>>> desired folder, followed by updating the texture paths. Instead of >>>>>>>> that >>>>>>>> occurring, I get an error in the script editor that the move cannot be >>>>>>>> done >>>>>>>> because of a permission issue or path existence issue, the path to >>>>>>>> which I >>>>>>>> want the textures to be moved too have full write and read access and >>>>>>>> the >>>>>>>> folder does exist ? >>>>>>>> >>>>>>>> It's suppose to automate the process of moving textures, it's not >>>>>>>> doing a good Job at that, I know it's roughly a 5-10 year old script. >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "Python Programming for Autodesk Maya" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to [email protected]. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/python_inside_maya/7340ad0e-b26d-4507-a204-00d1bc2f8c13%40googlegroups.com >>>>>>>> <https://groups.google.com/d/msgid/python_inside_maya/7340ad0e-b26d-4507-a204-00d1bc2f8c13%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Python Programming for Autodesk Maya" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/python_inside_maya/26de5735-3a6c-42ce-ac28-2cd65f71a244%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/python_inside_maya/26de5735-3a6c-42ce-ac28-2cd65f71a244%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >>>>> >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "Python Programming for Autodesk Maya" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/python_inside_maya/5PLHueaPxzg/unsubscribe >>>>> . >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2u1i%2BLxvMASzji7JBn%2BHxVTR3fm9iWuJdjEY7jU6oAFQ%40mail.gmail.com >>>>> <https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2u1i%2BLxvMASzji7JBn%2BHxVTR3fm9iWuJdjEY7jU6oAFQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Python Programming for Autodesk Maya" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/python_inside_maya/5607564D.5030403%40gmail.com >>>>> <https://groups.google.com/d/msgid/python_inside_maya/5607564D.5030403%40gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/1449c7c3-9402-4348-b4d0-cab44c45cbda%40googlegroups.com >> <https://groups.google.com/d/msgid/python_inside_maya/1449c7c3-9402-4348-b4d0-cab44c45cbda%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Python Programming for Autodesk Maya" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/python_inside_maya/5PLHueaPxzg/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2XX4K2GHT6QYzYEx3o3soEX1iMPt4v3uqvfeHkoMqckg%40mail.gmail.com > <https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2XX4K2GHT6QYzYEx3o3soEX1iMPt4v3uqvfeHkoMqckg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/5609DF27.2060301%40gmail.com > <https://groups.google.com/d/msgid/python_inside_maya/5609DF27.2060301%40gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA1J_3mRRQ2ySA83F%3D4CccEwrv90FMUmwrtv%2BdR4jRE41w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
