Apple Event: May 7th at 7 am PT
Here's what I did:
Yes I have "Show Overlays" turned on, with Handles, Lines, and Animation Path turned on.
Has anyone experienced this?
I did a cursory Google search for oscOptions and didn't find anything unfortunately. I actually tried doing exactly what you suggested, but it didn't help. I have no idea what caused the oscOptions value to change from 30 to 26, but I'll keep an eye out now. At least I found a fix, which seems to work, at least so far...
So yeah, long and short of it, if it happens to anyone, the fix is this:
I did a cursory Google search for oscOptions and didn't find anything unfortunately. I actually tried doing exactly what you suggested, but it didn't help. I have no idea what caused the oscOptions value to change from 30 to 26, but I'll keep an eye out now. At least I found a fix, which seems to work, at least so far...
So yeah, long and short of it, if it happens to anyone, the fix is this:
I cannot reproduce this behavior.
The control points appear for me when the Motion Path is selected.
You may try deleting preferences. Just like in FCP, Motion preferences can become corrupted and that can cause unexpected behavior.
To delete preferences, hold down command and option while starting Motion and click Delete Preferences.
Thanks Luis. Unfortunately it didn't help.
Some progress however. I found an earlier version of my project in which the handles are showing. I removed all other objects to isolate the issue, and I can't tell why in one project version the handles are missing, and in the other version (the earlier one), the handles are showing.
This is a bit like the "spot the difference" game, but I'm unable to see it!
[Link Edited by Moderator]
I did try, and the two projects appear to work the same for me - i.e., I cannot see the motion path handles either...
I tried to have a look at the contents of the xml.
They start pretty much the same, but then the one where the handles are not visible happens to be much longer than the other.
I am sorry, but I can't figure out anything in there that would explain this strange behavior. Mysterious.
Thanks for taking a deeper look!
I didn't think to open the project file in a text viewer. I ended up simplifying and removing all deltas, until I finally found the culprit. It's the "oscOptions" parameter within the <viewer> object:
<viewer subview="0">
<resolutionMode>0</resolutionMode>
...
<oscOptions>26</oscOptions>
...
</viewer>
It was set to 26, and in the project file with the motion path handles showing, it was set to 30. So I changed it to 30 and that appears to have fixed it.
Can you try it on your end? Also, any idea what this "oscOptions" is, and if you can toggle it within the Motion UI as opposed to directly modifying the project file source?
"OSC" is shorthand for "On Screen Control". The value of the parameter (oscOptions) is not known to me. [It's ironic that when I first read this thread that I was tempted to tell you to dig into the XML of the project file... but I couldn't tell you what to look for.]
However, for a Motion Path behavior, as soon as you click on the behavior in the Layers List, the cursor should automatically go to Adjust Item. If you only select the object the Motion Path is connected to, then all you get is the regular cursor — you still see the path, but you cannot edit it.
Something within your project broke the 'link' from Motion Path to its object (it happens [not often, but...]). Usually when something like this happens to me, I just remove the "faulty" behavior and replace it with a "fresh" new copy. If that works, Save As a new version of the project (don't risk resaving over the "older" version). [I think you already do that for the most part.]
Try to remember the steps you take when constructing your projects — take breaks and save more frequently - it makes keeping track of changes you make... shorter...
If you figure out the oscOptions codes — please post them!
btw I tried linking to a zip file with the two projects, but it got removed by the moderator...
Yes, that happens. But I still got it. I am away from my mac and will test, but maybe only tomorrow.
Oh, cool :) Thank you Luis!
I can confirm that changing the 26 value to 30 also made the controls appear for me.
Apple Motion: Missing motion path handles
