When I preview my individual slides, the entrance animations work fine, but when I preview the whole project or publish it to a local hard drive, a lot of the animations appear jerky, especially on the first slide.
Thanks Leslie, I found that thread before but it seemed to be talking most about LMSs. I'm working locally on mine and so it didn't really help.
I've attached my file for you to look at if you don't mind. The problem seems to be mostly on the first page. It's my first attempt at using the software (SL2) and I thought I'd have a play about with the flat design template I found.
Thanks for that. It seems to work fine in IE, although it does take a while to load to get past the page where you click the log-in button. But in Chrome, I'm still getting the jerkiness, especially on the second and third occasion you visit the learning objectives page.
Yeah, using the same version. I've tried it again this morning and the first page is running fine now, but the 2nd and 3rd time I get to the L.O. page, it's still jerky. In Chrome that is.
Hi Tom! If you'd like for us to continue to investigate, it may be helpful to understand some more about your computer as well as perhaps a screen cast of what you are seeing. Please submit a case to support so that we can take a look.
One last thing. In the story I attached earlier, I cannot get my head around the conditional state changes in one of the slides.
In slide 1.8 there is a layer called 'Advert Tile'. The photo in the box has 4 states and I am trying to replicate the effect where the user can click the left or right arrows (hotspots) and scroll left or right through the states.
I'd tried to use the conditions to say 'if state 1 and the user click the hotspot go to state 2' then added 'if state 2 and user click hotspot go to state 3' and so on, but I've only got it to sort of work.
Is the order of the conditions important? I changed them around a bit and it seemed to help, but still isn't perfect.
12 Replies
Hi Tom!
I have actually seen this reported before, although it doesn't appear that we reached a concrete solution.
Can you check out this thread and let us know if any of this is applicable or assists you?
Hi Tom,
Can you confirm you're also working locally on your .story files? Also is this in SL1 or SL2?
Do you have a sample project we could take a look at?
Thanks Leslie, I found that thread before but it seemed to be talking most about LMSs. I'm working locally on mine and so it didn't really help.
I've attached my file for you to look at if you don't mind. The problem seems to be mostly on the first page. It's my first attempt at using the software (SL2) and I thought I'd have a play about with the flat design template I found.
Thanks for your help,
Tom
Hi Tom!
Do you see the same behavior in this published output:
http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/stp1965og23bk2m1bo91puerpr2iu4/story.html
Hi Leslie,
Thanks for that. It seems to work fine in IE, although it does take a while to load to get past the page where you click the log-in button. But in Chrome, I'm still getting the jerkiness, especially on the second and third occasion you visit the learning objectives page.
Thanks for your help again,
Tom
What version of Chrome are you utilizing Tom? I just do not see it in Version 38.0.2125.111
Yeah, using the same version. I've tried it again this morning and the first page is running fine now, but the 2nd and 3rd time I get to the L.O. page, it's still jerky. In Chrome that is.
Hi Tom! If you'd like for us to continue to investigate, it may be helpful to understand some more about your computer as well as perhaps a screen cast of what you are seeing. Please submit a case to support so that we can take a look.
Thanks Leslie, will do
Thanks Tom!
Sorry Leslie,
One last thing. In the story I attached earlier, I cannot get my head around the conditional state changes in one of the slides.
In slide 1.8 there is a layer called 'Advert Tile'. The photo in the box has 4 states and I am trying to replicate the effect where the user can click the left or right arrows (hotspots) and scroll left or right through the states.
I'd tried to use the conditions to say 'if state 1 and the user click the hotspot go to state 2' then added 'if state 2 and user click hotspot go to state 3' and so on, but I've only got it to sort of work.
Is the order of the conditions important? I changed them around a bit and it seemed to help, but still isn't perfect.
Thanks again,
Tom
Hi Tom,
Order of conditions and triggers are import and you can read more about the trigger order here.
This discussion is closed. You can start a new discussion or contact Articulate Support.