Python cmds.emit crashes Maya (2017 U3)

[Anonymous]

Hi, I've got a problem with maya crash when I try to use emit command.

Even using a docs example crashes maya:

cmds.particle()
cmds.emit( object='particle1', position=((1, 1, 1), (2, 2, 2)), attribute=('velocity', 'rgbPP'), vectorValue=((1, 2, 3), (2, 3, 4), (.5, 1, 0)), floatValue=.1 )

I found post from 2009 on cgtalk, but without any replies.

MEL example works:

particle;
emit -object particle1
          -position 1 1 1
          -position 2 2 2
          -attribute velocity
               -vectorValue 1 2 3
               -vectorValue 2 3 4
          -attribute rgbPP
               -vectorValue .5 1 0
               -floatValue .1;

Edit: Did check that on Maya2015 SP5 - same crash result. 

Any hints?

[Anonymous]

Hi, I've got a problem with maya crash when I try to use emit command.

Even using a docs example crashes maya:

cmds.particle()
cmds.emit( object='particle1', position=((1, 1, 1), (2, 2, 2)), attribute=('velocity', 'rgbPP'), vectorValue=((1, 2, 3), (2, 3, 4), (.5, 1, 0)), floatValue=.1 )

I found post from 2009 on cgtalk, but without any replies.

MEL example works:

particle;
emit -object particle1
          -position 1 1 1
          -position 2 2 2
          -attribute velocity
               -vectorValue 1 2 3
               -vectorValue 2 3 4
          -attribute rgbPP
               -vectorValue .5 1 0
               -floatValue .1;

Edit: Did check that on Maya2015 SP5 - same crash result. 

Any hints?

[Anonymous · Accepted solution]

That example crashes in Maya 2017 as well. Looks like it might just be a broken command.

As a work around you could use the mel command in python via maya.mel.eval.

[Anonymous · Accepted solution]

That example crashes in Maya 2017 as well. Looks like it might just be a broken command.

As a work around you could use the mel command in python via maya.mel.eval.

[Anonymous]

Well, it seems broken.

I found a topic -> http://forums.cgsociety.org/showthread.php?t=773410 showing same issue in 2009 - that's 8 yeas ago.  

It seems impossible that there is an particle emit bug that gets unnoticed for almost a decade.

I checked pymel implementation and it seems broken as well.

[Anonymous]

Well, it seems broken.

I found a topic -> http://forums.cgsociety.org/showthread.php?t=773410 showing same issue in 2009 - that's 8 yeas ago.  

It seems impossible that there is an particle emit bug that gets unnoticed for almost a decade.

I checked pymel implementation and it seems broken as well.

[Anonymous]

I did run some more tests  and it seems that maya.mel.eval is an only option at the moment.

I found some additional strange behaviours with python "emit":

- emitting particles with attributes crashes maya

- emitting particles only with position works ok for "legacy" particles

- emitting particles only with position makes particle .pt[0] always at origin {0,0,0], other particles are ok - happens with nParticles

Usimg maya.mel.eval works like a charm for particles and nParticles as well.

It's some nasty bug out there, but for the time being I've got a workaround.

[Anonymous]

I did run some more tests  and it seems that maya.mel.eval is an only option at the moment.

I found some additional strange behaviours with python "emit":

- emitting particles with attributes crashes maya

- emitting particles only with position works ok for "legacy" particles

- emitting particles only with position makes particle .pt[0] always at origin {0,0,0], other particles are ok - happens with nParticles

Usimg maya.mel.eval works like a charm for particles and nParticles as well.

It's some nasty bug out there, but for the time being I've got a workaround.