Empty layer creating a crash and a corrupted file

I have an empty layer in my project. I don't know how it got there. I can't delete it. If I try to delete it, move it, etc, Motion crashes, my project gets corrupt and will then crash Motion if i try to open the project.

I tried cutting the group with the bad layer out of my project, pasting the group into a new Motion project (which got rid of the bad layer), and then pasting the group back in to the original file. Upon saving and re opening, this yielded another file which crashed Motion.

Anyone know how to fix this?

Please see attached image

A couple of suggestions. Close Motion and try trashing your preferences. Reboot your mac.

Tried it, no luck.

Same issues remain

Did more digging. I cut all the layers out of the original project and pasted them into a new file.

This yielded the result seen in the attached screenshot. Somehow a path to an image became corrupted, yet I can't find away to relink or update paths like you can in Indesign & Illustrator?

Is this feature in Motion, but I'm just not finding it?

Thanks!

43 views and the only response is the standard "reboot it all" one?

I can't be the only one who's seen this before.

If you need to relink a object/media go into the Media TAB command - and right click the file and select reconnect.

Easy, select the group containing the empty layer, delete the group, undo, the empty layer will now be a normal layer.
It's some sort of bug, easy to fix though.

I've had the same problems. Here are some related support threads.

One
Two
Three

Since Motion 5.1 I haven't had these problems. What version of Motion are you using?

Looks like the 5.1 update might have fixed the issue for me as well.

Glad it's working better for you!

That problem caused me to lose all my hair...

Grr, it's back and with a text layer now

Luckily, this fix did work.

"Easy, select the group containing the empty layer, delete the group, undo, the empty layer will now be a normal layer.
It's some sort of bug, easy to fix though."

thx!

Darn it! I was hoping that this would go AND stay away with 5.1.

I haven't had it happen to me...yet