[Maya-Python] Open/New File VERY slow while batching

[Alec Fredericks]

Hey there,
I have a batch script that's running through some raw mocap data and
converting it down to different rigs.
When I modify the file in Maya -- bake things down, delete bits of rig, etc
-- opening up another file or creating a new file takes an inordinate
amount of time.

I'm wondering if it's because Maya hasn't resolved all of the reference
edits and I haven't saved the file before moving on to the new file.
I'm going to test that theory, but I'm wondering if anyone has experienced
this funkiness before and, if so, if you found a remedy.
Thanks,
Alec

[Alec Fredericks]

So it turns out that the problem is making a bunch of changes in Maya that
aren't saved. That must put Maya into a weird state that makes opening up a
file or creating a new file take a very long time.
My solution was to just save a temp file, which takes just a couple of
seconds, and then create a new file, which then happens almost
instantaneously.

Post by Alec Fredericks
Hey there,
I have a batch script that's running through some raw mocap data and
converting it down to different rigs.
When I modify the file in Maya -- bake things down, delete bits of rig,
etc -- opening up another file or creating a new file takes an inordinate
amount of time.
I'm wondering if it's because Maya hasn't resolved all of the reference
edits and I haven't saved the file before moving on to the new file.
I'm going to test that theory, but I'm wondering if anyone has experienced
this funkiness before and, if so, if you found a remedy.
Thanks,
Alec

[Roy Nieterau]

What kind of changes were you making? Do you have a reproducible example to
run? What Maya version did you test?

Post by Alec Fredericks
So it turns out that the problem is making a bunch of changes in Maya that
aren't saved. That must put Maya into a weird state that makes opening up a
file or creating a new file take a very long time.
My solution was to just save a temp file, which takes just a couple of
seconds, and then create a new file, which then happens almost
instantaneously.

Post by Alec Fredericks
Hey there,
I have a batch script that's running through some raw mocap data and
converting it down to different rigs.
When I modify the file in Maya -- bake things down, delete bits of rig,
etc -- opening up another file or creating a new file takes an inordinate
amount of time.
I'm wondering if it's because Maya hasn't resolved all of the reference
edits and I haven't saved the file before moving on to the new file.
I'm going to test that theory, but I'm wondering if anyone has
experienced this funkiness before and, if so, if you found a remedy.
Thanks,
Alec

[Alec Fredericks]

I had a couple of referenced objects and, on one, I deleted a bunch of
constraints after baking keys for joints & controls in both referenced
objects.
I'm thinking that the reference edits just piled up and Maya needed to do
something with them before moving on when trying to create a new file or
load another. In this case, saving the file was enough and, by far, the
fastest way to deal with the problem.
Everything was performed in Maya 2017r5. Since everything I'm working on is
proprietary, I don't have anything to share, unfortunately.

Post by Roy Nieterau
What kind of changes were you making? Do you have a reproducible example
to run? What Maya version did you test?

Post by Alec Fredericks
So it turns out that the problem is making a bunch of changes in Maya
that aren't saved. That must put Maya into a weird state that makes opening
up a file or creating a new file take a very long time.
My solution was to just save a temp file, which takes just a couple of
seconds, and then create a new file, which then happens almost
instantaneously.

Post by Alec Fredericks
Hey there,
I have a batch script that's running through some raw mocap data and
converting it down to different rigs.
When I modify the file in Maya -- bake things down, delete bits of rig,
etc -- opening up another file or creating a new file takes an inordinate
amount of time.
I'm wondering if it's because Maya hasn't resolved all of the reference
edits and I haven't saved the file before moving on to the new file.
I'm going to test that theory, but I'm wondering if anyone has
experienced this funkiness before and, if so, if you found a remedy.
Thanks,
Alec

--

You received this message because you are subscribed to a topic in the
Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/python_inside_maya/FGYsDZ1HZ3E/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
To view this discussion on the web visit
https://groups.google.com/d/msgid/python_inside_maya/c1613dea-7089-4979-b3d5-577960e68a7d%40googlegroups.com
<https://groups.google.com/d/msgid/python_inside_maya/c1613dea-7089-4979-b3d5-577960e68a7d%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.