Motion 5.0.6 is out - you might want to wait to upgrade...

Yes! the most simple kind of setup imaginable!!

Two rectangles start out in the same place in space (0,0,0). The blue one is moved back to z: -1000 and turned into an emitter. 3D is set. The larger white rectangle is angled on the Y-axis. Image 1 shows the emitter's relationship to the white rectangle from a over the top view (in Active Camera). There are no intersections, it appears as the emitter is over the rectangle wihen it it is supposed to be on the same Z-axis.

This image shows no intersections when I count at least 7 blue rectangles should be intersecting the white rectangle.

This is the layer list -- I've even added a Camera to make sure it's all 3D.

Here: I move the white rectangle *above* the emitter (no other changes, playhead still in the same position on the timeline):

And this is the result -- obviously the same as having the emitter rasterized.

At some point today, when I have time, I'm probably going to do a complete manual uninstall of Motion and try re-installing it.

ok - that did it... but why should it be the opposite of the way it was set up before?. I could completely ignore that setting, now I have to make an effort to manually change that every time I create a 3D emitter... 😝

What Motion *used* to do is remember some user settings — for example, the Fill Color of a new shape. Awhile back, this did not require setting a color in the HUD (like it has lately.) There is a good chance that the original default value could have been Local 3D; but it USED to remember what I previously set it at. It no longer does... even within the same project.

Also, Motion will now not remember that I don't want the inset view (which is going to annoy me to no end) -- it keeps turning it back on, every new project (and my preference is set to "Manually.") I haven't had to deal with turning off inset view since I first got Motion 5.0 (or when I had to trash preferences... which almost never improves anything for me.)

There seems to be some annoying changes to the UI -- most of them seem to be aimed at beginners whom I would guess complain about Motion bogging down, so Apple has set up playback optimizations. That means several extra steps in my workflows now that are going to slow me down... things I have gotten to the point of taking for granted. I used to have Motion setup the way I liked to work. Now, I will basically have to re-setup my work preferences with every new project.

Overall (annoyances aside, a little more brain dead and a little less "Mac-like"), it does seem to be handling a bit more smoothly... but I haven't finished kicking the tires yet.