I use this below line of code for cleaning my file so that does not gives error
in others pc if they don't have that plugin and this remove in ma file headers
also.
# plugin cleanup
plugins = cmds.unknownPlugin(query=True, list=True)
if plugins != None:
for plugin in plugins:
print plugin
cmds.unknownPlugin(plugin, remove=True)
and if this doesn’t work for you then you can try to unload ngSkinTool with
below lines. (it will force unload.)
cmds.unloadPlugin("ngSkinTools", force=True)
If you want to check if ngSkinTool is used in your file or not then you can
run below command.(this will return True/False, that plugin can be safely
unload.)
cmds.pluginInfo("ngSkinTools", query=True, unloadOk=True)
I hope this helps.
Soham.
> On 09-Jun-2020, at 8:01 AM, gerar...@flyingbark.com.au wrote:
>
>
> Hello. I posted this on the ngSkinTools forum but wanted to widen the net a
> little as I'm not sure if its a Maya issue or a problem with the 3rd party
> tool.
>
> I get this:
> // Error: file: C:/Program
> Files/Autodesk/Maya2017/scripts/others/pluginWin.mel line 1429: Plug-in,
> "ngSkinTools", cannot be unloaded because it defines a MPxData derived type
> that is still in use. //
>
> I'm using Maya 2017 v5 and NG 1.7.9 in production and we are hitting a
> problem where the 'requires' line for NG in the maya ascii file header still
> exists ( requires -dataType "ngSkinLayerDataStorage" "ngSkinTools" "1.7.9" )
> despite the custom nodes being removed from the scene.
>
> This is causing problems with files failing to open as NG is not currently
> permitted as part of our studio environment (they are weary of 3rd Party
> tools - but a few of us absolutely love NG's workflow and can't go back to
> Maya's paleolithic solution)
>
> Currently I have written something that saves out the file as ma then line by
> line removes the requires lines but it has to rewrite the entire file and
> they can be big, then the file needs to be reopened. I need another solution.
> Note that when the header is removed, the file reopens fine so to my mind it
> appears to be possibly an issue of something in memory. Also when the file
> has its custom nodes removed and is saved (with header intact), opening the
> file again and unplugging the tool is successful - again making me think its
> something stuck in the mayas memory for that session..?
>
>
> Any advice appreciated.
>
> Gerard.
>
> --
> 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 python_inside_maya+unsubscr...@googlegroups.com
> <mailto:python_inside_maya+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/python_inside_maya/4493fcbc-3b2f-46ae-9bc4-dfff0a2406a5o%40googlegroups.com
>
> <https://groups.google.com/d/msgid/python_inside_maya/4493fcbc-3b2f-46ae-9bc4-dfff0a2406a5o%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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 python_inside_maya+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/python_inside_maya/0AA19505-EAA4-4C03-AF39-841C25EE0E2D%40gmail.com.
