Unfortunately I've just discovered the RAM Preview issues of Motion. That's a non-starter for me. I probably use the RAM Preview feature of AE more than anything else. Without those previews, constantly, it's impossible to gauge what I'm doing, how it feels, its audience perception/impact etc.
I do motion graphics mockups of UI dynamics, so there's no way I can tolerate not having a 60fps preview near instantly available, all the time, as fast as is realistically possible of the machine I'm on.
Rendering out to a file everytime in need of a preview, then quicktime viewing it from Finder (the seemingly suggested workaround to this abhorrent problem) just doesn't cut it. Way too many extra steps.
Absolutely stunned this issue hasn't been the first fix priority, and fixed in something like this. It gives me the impression that nobody making the software actually uses the software. Which is something I can say about many aspects of AE, as well.
Unfortunately I'm stuck on a Mac at the moment, so can't use my beloved 3ds Max for this project. Back to AE.
For anyone coming to this thread and considering using Motion over AE, consider this: MOTION... doesn't do stable frame rate previews, under ANY circumstances, on ANY machine, of ANY power or ANY amount of RAM.
In 2014. That's un-farken-believably poor form.
If you can live without accurate frame rate previews, then that's the kind of app Motion is, the one you can use for things where actual "motion" is not inherently important to the perception. And that's irony, I guess.