A general question on a finished project. I'm using Captivate 5 on an "average" PC running XP.
I have a project of around 90 slides, most with audio but with simple animations. Pictures fade in and out and some instructions on how to use a system in general. Nothing advanced so to speak.
I feel the project runs a bit slow when I have published it and click through it. When I click a button it takes a while for it to jump to the disired slide and so on.
I set the preloader to 100% and also added a "loading-slide", that doesn't do anything, in the beginning of the project to let it set.
Any ideas on how I can make it run better?
Thanks in advance.
without looking at your project...
1) what rod said. if you're branching and jumping far forward there is some lag while those 'future' slides are built.
2) on your buttons that go to the 'next' slide, are you using 'continue' or 'jump to slide' or 'go to next slide?'
3) i find some pc's struggle with text animations, eliminating them improved performance. If you have any of those, might be worth experimenting to find a sweet spot.
4) Optimizing your graphics and sound files may help, again, takes some experimentation to find where the quality is 'good enough' yet still speedy enough.
those are my thoughts, again, without looking at your project.
Thanks for the replies.
On the "home screen" of the presentation which is also the first slide, you have a lot of different options on what you would like to click on, so it's more branching than linnear.
One thing I noticed is that the option in the top left corner, which most people are probably gonna click first is in the very end of the project in Captivate. So you reckon it would flow better if I perhaps moved that to the first couple of slides in Captivate?
I'm mosty using "jump to slide", is that an issue as well?
The project has a coupel of text animations, but mostly png.-files fading in and out.
Thanks for the help.
OK. That's what I was thinking the issue might be.
In a Captivate published project, even though YOU might think of it as a branching project, as far as Captivate is concerned it's still just a group of slides in a long line numbered from 1 to whatever. When you click to jump to a slide that is somewhere down the line from your current slide, the Flash Player has to render not just the slide you are jumping to but also all of the slides in between. If there are a lot of slides between your start point and the target, then that rendering will take time. It might be several seconds in some cases.
If you want to speed up the rendering time, try to structure your branching so that the user will be jumping the smallest number of slides.
Great. This is why I love the Adobe Forums. This will help me a lot in the future. I usually don't do projects with this many slides, gets a bit confusing keeping track of all the navigation when you push +100 slides.
I'll try to optimize the amount of slides you have to jump.
Thanks for the help.
Does it work to bump a thread like this?
Thought I would ask you again about optimizing a Captivate project. The project I mentioned earlier in this thread ended up being around 125 slides and the project is running quite slow. When launching it, it takes several minutes before it (for example navigation and animations) runs in a user friendly way.
So my question is, how could I optimize this? Is it correct to assume that a project will run slower the more slides it has? How much does animation, audio and compressing the project and so on play?
How do you guys do when creating bigger projects?
Europe, Middle East and Africa