Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
IMPORTANT: Using these tools (version 1.3) can lead to massive scene bloat!
There is a serious bug in the way the 'Slide' functionality has been implemented on the split tools.
These tools create an expression that connects to the polySplit node in the mesh construction history.
When the mesh or construction history is deleted, the following is supposed to happen:
1. The connections from first history node to the mesh shape are broken.
2. Because the history node has no output connections, it deletes itself and in turn breaks the connections to the next history node.
3. This behaviour repeats for the entire history chain which causes all history nodes to be deleted.
HOWEVER:
Because an extra 'expression' node has been created along the chain, the polySplit node it is connected to still has ouput connections (to the expression node) which stops the automatic deletion from happening and in turn stops the rest of the history chain from being deleted!
Optimising scene size will not fix this.
Deleting all construction history will not fix this.
I have a 21MB scene that is still 20MB in size after everything visible in it has been deleted and optimise scene size has been run with everything checked. It contains around 3000 expression nodes connected to polySplit nodes and there are around 2000 'hanging' history chains that contain on average 50 history nodes each..!
This obviously isn't good and I now need to stop all our internal teams from using these tools...
:o(
As I progress more into character modelling I find myself using more and more features within this script. "Connect Verts/Edges/Faces" is fast becoming a favorite.
