I’m trying to figure out if there is a way through script to remove a requirement to an obsolete plugin from a file without having to save it as ASCII and manually removing the requirement line.
This requirement isn’t associated with any unknown nodes in the scene. I can delete everything possible from the scene, save it and still get the missing plugin error when loading up the file.
2nding Amorano’s comment. I’ve never found a way. Thankfully they are always in the first few lines and easy to hack out. The exception is MentalRay. That thing is plugin fungus.
We’re finding that there are certain things that act like a virus. The current offenders are:
elastikSolver
Turtle
The elastik thing hasn’t been used in years but with referencing and passing files around, the node is required in a lot of our files but hasn’t been used in forever. And Turtle, holy god, help me get rid of this thing. It creates nodes and shelves even with the plugin unloaded. I need some Maya Penicillin
[QUOTE=TheMaxx;23023]We’re finding that there are certain things that act like a virus. The current offenders are:
elastikSolver
Turtle
The elastik thing hasn’t been used in years but with referencing and passing files around, the node is required in a lot of our files but hasn’t been used in forever. And Turtle, holy god, help me get rid of this thing. It creates nodes and shelves even with the plugin unloaded. I need some Maya Penicillin[/QUOTE]
Yeah, we wrote a script that wraps Turtle usage to deal with that. Artists must use Turtle by launching the tool and when they close the UI it cleans up the Turtle nodes correctly. You can’t even do that with MentalRay because it adds extra attributes to your shader nodes