Maya Output window going crazy

[soviut]

When opening a scene file in Maya 8.5 64-bit, with the Craft plugin loaded, the output window goes crazy, spitting out every single node name from the scene as the file opens. This slows the file loading process significantly.

Unloading the Craft plugin results in none of the above and loads the scene much faster.

Any suggestions?

[Carl Buhre]

When opening a scene file in Maya 8.5 64-bit, with the Craft plugin loaded, the output window goes crazy, spitting out every single node name from the scene as the file opens. This slows the file loading process significantly.

Unloading the Craft plugin results in none of the above and loads the scene much faster.

Any suggestions?

Hello Soviut,

I just tried this in the 32-bit version and it's the same thing there. I usually don't work in scenes containing that many objects so this hasn't been a problem but it's most likely related to Craft Director Tools scanning scenes loaded for CDT objects that results in that output info for some reason. We will look into it, thank you for reporting this!

[soviut]

I just tried this in the 32-bit version and it's the same thing there. I usually don't work in scenes containing that many objects so this hasn't been a problem but it's most likely related to Craft Director Tools scanning scenes loaded for CDT objects that results in that output info for some reason. We will look into it, thank you for reporting this!

Thanks Carl. Is there any reason the plugin spits out every single node it scans? Was that intentional or perhaps just a debug trace message left in from development?

[Carl Buhre]

I just tried this in the 32-bit version and it's the same thing there. I usually don't work in scenes containing that many objects so this hasn't been a problem but it's most likely related to Craft Director Tools scanning scenes loaded for CDT objects that results in that output info for some reason. We will look into it, thank you for reporting this!

Thanks Carl. Is there any reason the plugin spits out every single node it scans? Was that intentional or perhaps just a debug trace message left in from development?

I spoke with the developers and it's alternative #2. It's fixed and will be released with the upcoming update. Thank you again for reporting it.