Hello Rod, I am unsure what you are disagreeing with? I fully understand the legacy of Captivate as I've been there every step. I am unsure why you brought that up. I think you are misunderstanding or I have not explained this issue well enough. This course was developed entirely in Cp6. I have not done a significant amount of testing throughout development... basically building new slides each day. Anyhow, when I ran a rare test earlier today, I was shocked to notice the course was unresponsive; taking nearly five minutes before the first slide would show. Naturally I thought corruption. But through hiding slides and publishing older saved project revisions, I noticed a disturbing trend that project responsiveness. For instance, clicking the navigation buttons went from instantaneous down to just over five seconds per click as test through the published versions. Curiously, the following remain unaffected (responsive throughout all revisions): - Custom TOC button (a custom/advanced conditional action - if cpCmndTOCVisible = 0 or 1....) - Effects Everything else has become quite unresponsive (or gradually more unresponsive through the revisions): - BACK/NEXT buttons, - HELP button (a Jump to Slide x action) - Timeline events within a slide If this was a problem with preferences, I should not be able to solve the problem by publishing earlier versions or even hiding slides in the most recent revision. Additionally, I should not see this same issue on three different systems. But because I am willing to try anything, I cleared out the preferences and restarted Captivate and believe me, I am really disappointed to report that it did not help. Please understand, I am not necessarily blaming Captivate... as it could very well be something I have done that has simply made responsiveness worse as I added more slides. Figuring out what that is could be a huge challenge. 😞
... View more