MjPolyTools - possible unused nodes crash problem

[GatorNic]

not sure if this is waht your talking about but...

I use edge loop split and m. edge loop split a lot. I have found that they build up a history on objects and it can't be deleted by using the delete history button. its such a useful tool though I have just gotten use to opening the hypergraph and deleting the history manually after I am either done with the object or the history has become unweildy.

[pixelherder]

the thing is i cant manually delete them either - in the example pic above if i select the nodes and press delete maya hangs...

[devdoka]

the thing is i cant manually delete them either - in the example pic above if i select the nodes and press delete maya hangs...

Both MJ tools and Om toolBox use expressions to create loopsplits.
You need to 'clean up' your scence.
If you use MJ, and say you make 50 loopsplits on your poly mesh, and look in your
expression editor, you`ll see a bunch of expressions there, you`ll need to delete them.
Someone has posted here a mel script that deletes all the expressions, but
unfortunately i dont have it anymore.
On the other hand OM toolbox creates only one expression instead.
I usualy (after hitting del. history) open the hyperGraph, click on show in/out connections
and delete all the nodes i dont need.
I have found that Koshigaya scripts have a nice loopsplit tool, that create your loopsplits,
plus i leaves no garbages.

.

[JakobWelner]

I haven't heard of the exact problem you describe with maya hangs on delete of nodes but I know of the thing with those nodes that can't be deleted through delete history which is a quite weird thing and I havn't seen it myself yet.
Anyways, I've made some smalle changes on the loopSplit tool in the newer versions.. Donno which it is or if it's at all online, but It'll be in the next beta of OMToolbox for sure.
It's a somehow serious bug that we need to fix if it's still there!

Jakob Welner

[MasonDoran]

the best way to clean up your scene is to "Delete All" History....and then export selection....that way only the geometry gets exported....and the dirty nodes are left behind.

[pixelherder]

the best way to clean up your scene is to "Delete All" History....and then export selection....that way only the geometry gets exported....and the dirty nodes are left behind.

this is the problem - these are nodes left behind after deleting history, optimising the scene and trying to delete in the hypergraph. none of which work. As for exporting the selection, thats exactly what i did today :) ... the problem being i lost all my layer information (there were quite a few, so it took a while to set everything up again)

as i said, there are workarounds, but theyre timeconsuming and break up the workflow. If there was a better way round it that'd be great, but if not i'll just have to keep my fingers crossed!

[pixelherder]

I haven't heard of the exact problem you describe with maya hangs on delete of nodes but I know of the thing with those nodes that can't be deleted through delete history which is a quite weird thing and I havn't seen it myself yet.
Anyways, I've made some smalle changes on the loopSplit tool in the newer versions.. Donno which it is or if it's at all online, but It'll be in the next beta of OMToolbox for sure.
It's a somehow serious bug that we need to fix if it's still there!

Jakob Welner

if you can see the image above (i dont think it was showing up earlier) you'll see that the nodes all belong to an "empty" group > in the outliner the highlighted pcylinder28 is left over and doesnt actually have any geometry, but its got all this junk information and cant be deleted.

bizarre, but perhaps not anyones fault. maya moves in mysterious ways!

[JakobWelner]

I've changed the splits to split on the objects shape instead of the geometry which was what it did earlier.. donno if it changes anything, but I havn't heard any complaints about it since.. though only a few has tested it since I think.
Try'n take a look at the splitLoop file in this rar file.. that's the newest version.

http://www.hankoe.biz/jakob/tmp/omtMenuSample.rar

The rest is a new menu system I'm testing and you're very welcome to give it a try as well.. it'll work if you place all the mel-files in your omtoolbox directory..
As it's only for testing just yet, there's some tools I havn't implimented yet, so you may wanna keep your old OMT setup to use these.

*fingers crossed that this was the bug*

[gundog]

i use this on the mj. it'll wipe out all of them in the scene, not just the selected object. so i delete history on any geometry that has it. run this. then i'll delete the hidden node manually or run optomize scene.

DeleteHistory;
\r\nstring $expList[] = `ls -et \"expression\"`;
\r\nstring $exp;
\r\nfor ($exp in $expList)\r\n\tif (`match \"polySplit[0-9]\" $exp` != \"\")\r\n\t\tdelete $exp;

[MasonDoran]

PixelHerder....


"export selection" .>>>>select everything you want to keep in the outliner<<<<<<<

.....that means all geometry and ALL layer nodes and Sets if you have them....

[MasonDoran]

and btw.

the above method doesnt require "optimize scene" because you are basically sending your selections to clean scene.

"Optimize scene" is nice...but it still has some bugs......namely with things like what you are experiencing. It will not delete nodes that it does not recognize....which are usually introduced by plugins. The only way to get rid of all of these is with "export selection"

[pixelherder]

well thanks again to everyone for the replies, looks like i have a few different things to try!

cheers!

[brudney]

i also use mjpolytools as well as jwtoolbox and i also have a similar problem, but i don't think it's anyhow related to these tools.
i have to kill maya (6.01) after trying to start a new scene or load some other file but only when working with some pretty big scenes. it does not happen when there are few objects/polys/nodes in the scene. so maybe that's just maya's another 'great feature' ;)

[pixelherder]

i also use mjpolytools as well as jwtoolbox and i also have a similar problem, but i don't think it's anyhow related to these tools.
i have to kill maya (6.01) after trying to start a new scene or load some other file but only when working with some pretty big scenes. it does not happen when there are few objects/polys/nodes in the scene. so maybe that's just maya's another 'great feature' ;)

thats interesting, because thats exactly what i'm experiencing - its only since i've been working on some fairly big scenes with lots of hi-poly models that i've started to experience this issue.

p.s. hurray for maya :rolleyes:

[JakobWelner]

dirty
I'll suggest that you take a look at OMToolbox instead of using JWToolbox which is the base of OMT. JWToolbox is not going to be updated any further and OMToolbox is under development all the time.. they've got the same features, with some added in OMT and some bugfixes, so OMT should be the choice, unless we have added some serious bugs in our updates?

[brudney]

yeah Jakob, i know, i downloaded OMT some time ago but haven't installed it yet. don't know why really.. maybe because JWT works so fine :)
btw i want to thank you for the JWT/OMT. i also use MJPT 1.4 but what i noticed is that when i try to loop split on a complex mesh, mjpt's loopsplit, besides being pretty damn slow, likes to hang maya, whereas yours loopsplit works like a charm :) selecting edgeloops works better as well. so, thank you :thumbsup:

[JakobWelner]

Heh. OMT's installation is also a bit complicated (like Bonus Tools) which is very sad..
Anyways, if you like JWToolbox, then the only reason for shifting to OMT would be moe features and the current release isn't really that good.

Glad you like the script :D

[toonshady]

Hi folks. I have been using Maya for several months now. Started to take interest in scripting. MJPolyTools is something I use in my poly modeling workflow. I wrote this little tool to aid me in deleting construction history that takes into the account of nodes that are left behind by MJPolyTools. Being so new to scripting, I gone through numerous failed attempts. But here's one seems to work well so far. I am wondering if anyone would like to take it for a spin, and give me feedback.

Here's the script LL_deleteCH (http://www.toonshady.net/media/stuff/LL_deleteCH.mel) or make a button of the code below.

$componentMode = `ls -hilite`;

$currentObj = `ls -sl`;

$getHistory = `listHistory $componentMode $currentObj`;

$nonInterObj = `ls -intermediateObjects $getHistory`;

sets -n cHistorySet $nonInterObj;

delete -constructionHistory $componentMode $currentObj;

delete `sets -q cHistorySet`;

delete cHistorySet;

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.