Conversion from Storyline 1 to 2 - interaction issue! Input needed please!

Hi Sue,

Guess if you follow the West Coast Eagles your hair is already at a premium, but that's a whole other story.

 I have found the occasional bug when converting from SL1 to SL2 as well.  Try opening a new project in SL2 and then import the offending slide and see if that works. If it does, import the rest of the project into the new file.

Not sure if that will work but worth a go.  Let me know what happens.

 Steve Lyne

Tamworth, NSW

Go The Swans!

Hi Steve

thanks for getting back to me (...perhaps - bloody Sydney supporters :P )

I "think" I have worked out what is happening - but I don't understand why.  It seems on conversion to SL2, any grouped objects I have, that have a "Jump to Slide" trigger, stop firing, even though the triggers appear identical on both versions.

When I add the exact same "Jump to Slide" trigger to all objects in the group individually - it works. Very annoying.

I will however, try that as a test and see if it will retain the original behaviour on import. Shall let you know! 

Thanks mate

PERTH, WA

Go Eagles! :p (although I DID cheer for Sydney this year in the GF *sigh*)

Sigh indeed!!!

Yes, that issue certainly rings a bell.

Steve

Hi guys,

I also have issues with questions that were perfectly working on SL1 and are not working on SL2. Description of the issue: impossible to click on the answers of the Multiple Choice Question.

Very strange fact: if I do a preview of the concerned slide only, it works. But as soon as I do a complete preview of the whole project it doesn't work anymore...

Maybe a kind of bug of SL2 that will be solved in a next update? I hope so , because I admit I am a bit lost and don't know how to solve this kind of issues.

Kind regards,

Patrick

Hi everyone!

I do see a similar issue that our QA Team is working on.

I will add this thread for their awareness and so that any updates can be shared here when applicable.

I do not see where any customer files have been shared regarding this issue, so if you are interested in sharing with support, please do so here.

Same problem: file attached.

Hi Jane!

Can you explain the issue you are having with the file that you shared?

Try to preview the slide with the doors. It stalls after the first scenario. There are five.

Yes, I'm seeing that now during preview. I'm going to do some further testing, but do you have a file that worked correctly in Storyline 1 prior to upgrading?

I’ve upgraded every file, and I don’t know where the old copies are stored (by Articulate when it says they’ll save an old copy). However, I did find out that E-Learning Bros. updated the interaction recently to be compatible with SL2. So, now I’m trying to reproduce all of my layers. I’m almost done, but I have one lingering problem. I can’t “see” the audio track from the old slide so that I can move it to the new slide. I can hear it, but I can’t find it. It’s not on the timeline. Thanks so much for trying to help me.

I found the audio on one of the layers. Sometimes I feel like a complete idiot. BTW, I love STORYLINE, even if I struggle due to my own lack of skills. Thanks you for all of your help!

The backup file is typically saved in the same location as your regular project file. Does this mean that you were able to get all of your issues resolved?

Yes, I just dumped the old file instead of trying to figure out the incompatibility with SL2. Whatever caused it, E-Learning Bros fixed it in their updated file.

Oh, that's great! Thanks for the update Jane :)

Hi all,

I wanted to provide an update here, as Storyline 2 Update 8 was just released, and included a number of fixes which you can see in the release notes available here. The item you all may be particularly interested in is how it fixed the issue where trigger conditions wouldn't work properly when upgrading a project from Storyline 1 to Storyline 2. You can download the latest update here, and after downloading and installing the latest update you’ll want to republish any existing content to ensure that the updates and fixes are applied.

Let us know if you have any questions, either here or by reaching out to our Support Engineers directly.