I'm building a course with a colleague and we are experiencing an odd problem. The starting slide in a scene has 10 images. Each image has a trigger assigned so that on click, the user is taken to a different slide that explains the image. Everything was working correctly until a final save when slides and triggers got scrambled.
I've deleted all the triggers and began relinking everything, now. when I build a trigger for 1 object, it copies that trigger to all the other objects. When I try to change, the same random copying occurs.
We are using Storyline 2.
I've also tried working around this by using Hotspots and the same problem occurs.
The first thing I'd want to check is that you're working on local project files as described here. You may want to look at importing it into a new file as detailed here.
If the behavior persists, I think we'll want to take a look at how you've set up these triggers and objects to see if there is anything else that could be interfering with it.
We are working with a local file and I've also tried importing into a new file on a new computer (also working locally) and the problem still persists.
Here's the course file. Any suggestions on what is causing the issue would be welcome.
Thanks for sharing the file here with us. I took a look and saw scene 2 had an initial slide with a number of images all set to jump to different slides. All the triggers were assigned to individual objects and worked normally for me. I did see the slide was set to advance automatically which jumped to another slide at the end of the timeline. Perhaps that's part of the issue you're seeing? If I'm looking in the wrong spot could you share a bit more information on how this should look or what area I should investigate further?
Okay- I have the original developer testing and he's still getting errors. I've suggested he repair his version of Storyline 2. The file is working for me, now.
If it's working for you and me, it may be that particular developers set up and repairing and ensuring he's working locally are the next best steps. Also double check that you're both using the same update, the latest is Update 7.
Thanks Mary - by the developers version do you mean running as an admin or installing the latest update? I'm glad to hear it's working, but also just want to make sure you're good to go going forward!
We had to have our IT department reinstall a "clean" copy of Storyline with the latest updates. Seems like something got corrupted during the original install.
10 Replies
Hi Mary,
The first thing I'd want to check is that you're working on local project files as described here. You may want to look at importing it into a new file as detailed here.
If the behavior persists, I think we'll want to take a look at how you've set up these triggers and objects to see if there is anything else that could be interfering with it.
Hi Ashley,
We are working with a local file and I've also tried importing into a new file on a new computer (also working locally) and the problem still persists.
Here's the course file. Any suggestions on what is causing the issue would be welcome.
Thank you.
Hi Mary,
Thanks for sharing the file here with us. I took a look and saw scene 2 had an initial slide with a number of images all set to jump to different slides. All the triggers were assigned to individual objects and worked normally for me. I did see the slide was set to advance automatically which jumped to another slide at the end of the timeline. Perhaps that's part of the issue you're seeing? If I'm looking in the wrong spot could you share a bit more information on how this should look or what area I should investigate further?
Hi Ashley,
Thanks for checking. That was the correct spot perhaps the auto jump was what was causing the error. I will check.
Feel free to keep us posted Mary - but everything looked normal on this end.
Okay- I have the original developer testing and he's still getting errors. I've suggested he repair his version of Storyline 2. The file is working for me, now.
If it's working for you and me, it may be that particular developers set up and repairing and ensuring he's working locally are the next best steps. Also double check that you're both using the same update, the latest is Update 7.
We were finally able to resolve the issue by reloading the developers version of Storyline. Thanks for the help :)
Thanks Mary - by the developers version do you mean running as an admin or installing the latest update? I'm glad to hear it's working, but also just want to make sure you're good to go going forward!
We had to have our IT department reinstall a "clean" copy of Storyline with the latest updates. Seems like something got corrupted during the original install.
This discussion is closed. You can start a new discussion or contact Articulate Support.