Kutter: Thanks. Yeah, I just forgot to edit out the boolean question (arrg), as part of this list was cut and past. Thanks. Layers don't help at all ... it particularly bogs down when importing a Poser object or animation. I have found that maximizing the window (single-window display) and closing the timeline helps tremendously. I use Windows2000 (aka the best OS that ever graced a hard drive), so I wouldn't say it is bad at handling resources, or anything else for that matter. In fact, it handles memory and resource quite elequently when you think about it. It even tames such rogue programming abominations as Poser and the like. Anyway, I'm straying off topic blathering about my like of WIN2K ... the point is, you shouldn't have to do this at all. As I said, Win2k and every other app I own simply does not do this. And I use some heavy duty apps. I can be using my real-time video editing solution and play countless MP3's, other videos, etc and they all get along just fine. (Talk about CPU intensive!) The point is, Vue doesn't know how to share CPU cycles correctly. Thanks again though, at least someone is responding. -Tim