A little about Captivate 2 vs. Captivate 3

Well, I lost about three hours of work as Captivate 2 crashed on me (repeatedly) on a larger branching simulation I’m developing. This prompted me back to my personal Macbook Pro to work on my day-job project in Captivate 3.

Captivate 3 seems to be a bit better with memory management as an application and it “feels” more stable. I don’t know if it actually is or not, but I haven’t crashed yet, and I’m running via Parallels instead of native on my desktop. So that’s good for starters, right?

Turns out, importing Powerpoint has a minor, albeit interesting difference between Captivate 2 and 3, and that’s in how Captivate deals with any custom animation on a given PowerPoint slide. In Captivate 2, it ignores the animation so if you have a bunch of images stacked on top of each other with animations that make them appear and move (I don’t do it, but lot’s of other people do) — well, they’re just stuck there in a big glob when you import such a slide in Captivate 2. Not so with Captivate 3 — it actually respects your animations and your timing.

Now, the next question for me was working with Articulate. If you import audio via Articulate and then time animations to it using Articulate’s set of tools — and then import said slide into Captivate 3, Captivate 3 will ignore all custom timings you put in and it doesn’t import the audio.

I don’t know how much use people might have for this, but I often will create “Engage” type of activities with Captivate, importing slides from Powerpoint so that my Articulate projects have a unified User Interface — so the thought of being able to synchronize audio with animations in Articulate, to export to Captivate 2 to create tabbed interactions has been appealing.

But there are always slower, alternative ways of doing the same thing. 😉

2 replies on “A little about Captivate 2 vs. Captivate 3”