[Troy Grady]

Good find, thanks. This worked a couple times and didn’t work another time. This is still a huge bug in Motion that occasionally makes project files unusable and I really wish they’d squash it. Tough to file a report for because it’s so sporadic but will see about doing so.

[Troy Grady]

Interesting find, thanks Alex! I’ve never seen anyone mention the ghost layers issue before — and actually call them “ghost” layers, no less. Will look into this. But yes, that screenshot is precisely the issue I’m describing.

[Troy Grady]

It appears to be project-file specific, but we’ll trash the prefs for old time’s sake. Beggars can’t be choosers at this point!

[Troy Grady]

Thanks guys-

Mark — Every version of Motion we’ve used since 2009, including the most recent update!

Don –Thanks for the heads up. It does seem like project file corruption, but in our case it is frequently so bad that copying layers no longer works, and simply causes a crash.

Admittedly we do a *ton* of complicated 3D stuff in Motion, and the project files get large quickly. This is no excuse for instability at a fundamental level though, but it may explain why we see it more often than others do. As a result, we compartmentalize across multiple project files whenever possible to minimize bloat, and are nearly OCD in our backup habits.

[Troy Grady]

Ok now that’s just embarrassing. At least I could be forgiven for missing the “convert-to-keyframes” option, because I only rarely do that. But your solution… totally works! And I do it all the time, for static object coordinates — just not with keyframed objects, since I’m normally a motion path / behaviors junkie.

Thanks for the great replies everyone!

[Troy Grady]

Ha — convert to keyframes. Genius. You win the internet today!

Thanks!

[Troy Grady]

Yep. The action of the box tool doesn’t appear to be any different than the standard select tool in this regard. I can drag up or down, and constrain motion either horizontally or vertically, but the vertical movement doesn’t snap. I’ve busted out my 8th grade permutations math to try every combination of modifier keys I can think of, hoping for easter egg snapping behavior, but haven’t found any!

[Troy Grady]

Thanks for the speedy response Mark! Yep, I see that you can drag the curve, but there’s no snapping. The resulting values are only ballparks. What I’m looking to do is a move a whole curve relatively by a specific amount, or move the whole curve to a specific value.

e.g. Adjusting keyframe *timing* in this respect is fantastically useful. Selecting a range of points and doing either “+100” or “+/delete/100” will move the selection either forward by 100 frames, or to the 100th frame.