Runtime problems in Browser

[annek33152065]

Hi there,

I created an alternative memory-game: A field with cards 6x4. You'll get a peek for 1 second where 3 cards are hidden. If you find these 3 cards on click within 10 seconds - you win and you'll get routed to the next slide.

The problem is: I published it for HTML5 and if I run it, it takes a lot of time to load this memory-game (1-2 seconds).

The first prototype was created in Articulate Storyline 2 and worked with triggers for the individual cards.

In Captivate I had to work with variables and if-conditions. It is also a responsive project. Is it possible that the slide with the memory game is overloaded? All of these cards are pictures. Or is it a problem with the script (maybe loading the variables and chcking if they are 1 or 0 takes to much memory).

I had no problems in the preview...maybe I published it the wrong way. I have no idea what went wrong.

Thank You

[Lilybiri]

I suspect indeed an 'overload'. How did you set up the actions: using shared actions to replace advanced actions can help, using states as well, but there are more possibilities. I don't think it is due to publishing at all. You offer too little details to help. Long time ago I created a memory game as well, in the most recent version (CP9) it would be much easier and load quicker:

Concentration Game - created exclusively with Captivate - Captivate blog

[rchil]

1 -2 seconds doesn't sound that bad. Maybe you should add a pre-loader graphic. Also, check the size of you images, make sure the file size/pixels per inch is not excessive.

[Lilybiri]

For web it is not ppi that is important but the total size in pixels. However, a game like the one described here will not be that big in file size. Having a lot of advanced actions and variables can slow down a published file a lot, it is not only the file size or the resolution of graphics that are the culprit. It is also not about preloading in this case....sorry to correct you. I just don't want other users to be confused. This is probably only a one or two-slide file, pretty small. A multitude of decisions in advanced/shared conditional actions will probably be the cause, and that should be streamlined.