Editing motion trail Maya 2018

[Anonymous]

Hi,

Motion Trails in 2018 on my characters went haywire.

Moving points causes them to "run away" on Z axis.

Undo stopped working - point goes back to its original position but character handle does not return. 

It happens only on some IK handles and in specific axes. 

2017 works fine.

Anyone has similar issues?

[kelly_hynes]

Hello,

Yes, this issue is logged.

MAYA-84833 Motion Trail : Cannot translate keys on Motion trails easily

It has been fixed by the development team.  Just needs validation from QA.  Should be in the next update release  and/or full public release.

Kelly

[Anonymous]

Hello

Unfortunately the problem still exists after update. Some motion trail points translate in opposite direction than intended. 

[Anonymous]

Here is a file demonstrating. Try grabbing any motion trail point and move it. It works fine in 2017.

[kelly_hynes]

Hello,

The original issue as reported, is in fact, fixed.  I just checked in Update 1.  There seems to be something specific to your scene file.  Possibly, this is a new defect.  You say it is working fine in 2017, however, the file you sent will not load in 2017 or updates.  I have this error:

// _Error: line 0: _Error reading file.

I can log a new defect for the development team to investigate, however, I would like to see the scene working and triage a bit more on my side first.

Any more details you can provide would be helpful.

Regards,

Kelly

[mspeer]

Hi!

@kelly_hynes , the upload scene-file is a Maya 2018 file, so you need to open it in Maya 2018 first and save as it as .ma .

I can see the problem in Maya 2018 , but not in Maya 2017 update 4.

[Anonymous]

Hi

Sorry.

Uploaded 2017 file. Saved with 2017.4.

[kelly_hynes · Accepted solution]

Hi again,

I logged a new defect:

MAYA-87284 Motion Trail: Cannot move motion trail keys for this scene

I have asked that this be fixed for next release.

Apologies for the inconvenience.

Kelly

[Anonymous]

i'm using maya 2018.4 has the issue been fixed yet? right now i still seem to be experiencing the same thing

[Anonymous]

Hi,

I'm having the same problem on my student version of maya. It's been happening with every file, and my maya is fully updated (2018.4). It's making it ten times more difficult to finish my animation work on my laptop. I go to an art school, so I have the paid version of maya available on their computers. I don't have this problem on their computers when using the same file. Someone please solve this. It's absolutely ridiculous. For now I'm bypassing this issue by using the graph editor to change my points and moving the objects instead of the points themselves. Kind of defeats the purpose of an EDITABLE motion trail.

[BenediZ]

Same problem in Maya2018.5...

EDIT: Hm, now after I once manually moved the object and played a while around, it work as it should

Can't say why... It had in my case also an aim constraint, which I deleted and added once again.

Maybe it has something to do...

[Anonymous]

I was able to fix this issue for myself by going into the Move Tool (W), then going under the Tool Settings and changing the Axis Orientation from Component to Object.

[JPelphrey]

Another possible fix: Change Maya's linear working units to centimeter. (Maya Preferences > Settings > Working Units > Linear:  centimeter) This prevents editable motion trail points from 'running away' when translated. Feels like a bug that editable motion trail points don't translate properly in any other working unit.