Hi again! I have created a slide with multiple layers. On each layer, I have an on screen close icon. Clicking this will take the user back to the base layer. The trigger function is applied correctly and functions seamlessly sometimes. However, other times there is a huge lag after the close icon is clicked before the player goes back to the base layer. Can anybody help? Thanks in advance for your responses.
How are you testing your content? In the past I've found that issues like that can occur when testing over a network connection but disappear when testing on the local drive and/or on the LMS itself.
Hi Harri, thanks for you reply. I am testing on my local drive using the story.html file. I'm connected to a LAN, though I'm not testing over a network itself. I have yet to test it on the LMS itself. Also, out of curiosity, is it a known bug in Storyline? I heard a few of my colleagues have faced the same issue, without being able to find a fix!
To my knowledge it is not a recognised bug although it never hurts to submit files to the Tech Support guys to look over. I have had issues with the 'close layer' trigger since update 5 but I think they may have been caused by the internet connection rather than the file itself as it behaved differently when other people accessed the content from different PCs using different internet connections.
I understand that there are often privacy concerns, however if you send it to articulate support they will respect all confidentiality clauses and may well be able to resolve the issues you are experiencing.
If as Harri said you need to share it with our team, it won't be shared anywhere else so it is confidential. Additionally we always recommend testing the published output within the intended environment to confirm that everything works as expected. Also, if you test from thelocal hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail.
9 Replies
Hi Dev,
How are you testing your content? In the past I've found that issues like that can occur when testing over a network connection but disappear when testing on the local drive and/or on the LMS itself.
Hi Harri, thanks for you reply. I am testing on my local drive using the story.html file. I'm connected to a LAN, though I'm not testing over a network itself. I have yet to test it on the LMS itself. Also, out of curiosity, is it a known bug in Storyline? I heard a few of my colleagues have faced the same issue, without being able to find a fix!
Hi Dev,
To my knowledge it is not a recognised bug although it never hurts to submit files to the Tech Support guys to look over. I have had issues with the 'close layer' trigger since update 5 but I think they may have been caused by the internet connection rather than the file itself as it behaved differently when other people accessed the content from different PCs using different internet connections.
Not sure if I can really submit the file due to privacy agreements between company and client!
Hi Dev,
I understand that there are often privacy concerns, however if you send it to articulate support they will respect all confidentiality clauses and may well be able to resolve the issues you are experiencing.
Oh great, thanks Harri. I'll consider doing that if it doesn't work out.
Also, I tested it on a demo LMS and it seems to work fine. Thanks again, Harri.
Hi Dev,
If as Harri said you need to share it with our team, it won't be shared anywhere else so it is confidential. Additionally we always recommend testing the published output within the intended environment to confirm that everything works as expected. Also, if you test from the local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail.
Thanks Ashley for confirming that testing on LMS is the only sure shot way to understand the functionality works correctly.
This discussion is closed. You can start a new discussion or contact Articulate Support.