Page MenuHome

Fix T59675: Motion path frame numbers at wrong positions
ClosedPublic

Authored by Jacques Lucke (JacquesLucke) on Dec 20 2018, 3:01 PM.

Details

Summary

I don't really understand why the positions were multiplied with ob->imat.
It worked in some cases because ob->imat was not updated at that point (I think).

Motion path coordinates are always in world space, right?

Diff Detail

Repository
rB Blender

Event Timeline

I can't see a reason for this use of ob->imat either.

This revision is now accepted and ready to land.Dec 21 2018, 6:05 PM
This revision was automatically updated to reflect the committed changes.