I'm in the process of converting a Presenter course to Storyline with a lot of interactive .swf files published from Captivate 4, AS2. When I try to import the .swf file, I get the error in the image below, something I never encountered when importing the same files into Presenter. The file appears to play OK and interactions appear to work properly. What "may not function properly" and how can I avoid this error in the future?
Thanks for responding. I am adding them separately as .swf - not videos.
I've also encountered a problem where sometimes the interactions work and sometimes they don't. For example, I imported a .swf file and the interactions worked. I went back to Captivate, made some changes, republished the .swf file from Captivate and imported the republished file. The interactions did not work. I deleted the re-imported .swf file, imported the same file again and the interactions worked.
Finally, the default slide trigger is not working. It's supposed to jump to a slide when the timeline ends but nothing happens.
Could these issues be associated with the _root error?
We have the exact same issues but worse with .SWF files. The Previous button will direct the user to the correct slide but the audio doesn't stop, I added a trigger and it fixed the error, however, if the user goes back to the slide with the .SWF video on it, you hear audio and see no video and to make matters worse, when you select NEXT to reach the next slide the audio keeps playing and no trigger whatsoever will make it stop. Our entire project is on hold until they come up with a workaround. I am very disappointed about the .SWF issue as it worked just fine in Presenter 09, feel like we just went backwards and wasted 2 weeks troubleshooting to no avail.
We have the exact same issues but worse with .SWF files. The Previous button will direct the user to the correct slide but the audio doesn't stop, I added a trigger and it fixed the error, however, if the user goes back to the slide with the .SWF video on it, you hear audio and see no video and to make matters worse, when you select NEXT to reach the next slide the audio keeps playing and no trigger whatsoever will make it stop. Our entire project is on hold until they come up with a workaround. I am very disappointed about the .SWF issue as it worked just fine in Presenter 09, feel like we just went backwards and wasted 2 weeks troubleshooting to no avail.
Hi Maya,
Glad to see I'm not alone. I believe the _root error problem was due to a Cp quiz slide. I deleted it and recreqted it in SL and the error went away. One HUGE disappointment, however, is that rollovers created in Cp do not work when imported as .swf into SL and video controls are enabled. I agree that SL should have at least the same functionality as Presenter.
If you'd like, we'd be happy to take a closer look at it. Please submit a case, including your .story file, using the link below so our support team can assist you further:
We have the exact same issues but worse with .SWF files. The Previous button will direct the user to the correct slide but the audio doesn't stop, I added a trigger and it fixed the error, however, if the user goes back to the slide with the .SWF video on it, you hear audio and see no video and to make matters worse, when you select NEXT to reach the next slide the audio keeps playing and no trigger whatsoever will make it stop. Our entire project is on hold until they come up with a workaround. I am very disappointed about the .SWF issue as it worked just fine in Presenter 09, feel like we just went backwards and wasted 2 weeks troubleshooting to no avail.
Did this issue ever get resolved for you Maya? I'm having issues as well with .swf files inserted in Storyline. I have 3 .swf files I'm trying to play back to back with auto advance from slide to slide. They are looping on themselves and at other times not completely finishing before jumping to the next . It's a nightmare. We have given up on Storyline for this deliverable and rolled back to an Articulate solution. I'm just curious if there was a fix on this. And yes, I have the latest updates to Storyline.
No, Articulate did not have a solution for us. We have an idea for a workaround for our .swf issue but due to the time constraints chose not to utilize it on the last training launch, it has yet to be tested in production.
Our second best solution was to launch the training modules which did not have video and subtitles (creating our .swf issue) in Storyline, the modules which contained video and subtitles were left in Articulate where they worked properly.
12 Replies
Hi Diane,
Are you importing the .swf files along with the Presenter slides or are you adding them separately?
Always Happy to Help,
Adrian
Hi Adrian,
Thanks for responding. I am adding them separately as .swf - not videos.
I've also encountered a problem where sometimes the interactions work and sometimes they don't. For example, I imported a .swf file and the interactions worked. I went back to Captivate, made some changes, republished the .swf file from Captivate and imported the republished file. The interactions did not work. I deleted the re-imported .swf file, imported the same file again and the interactions worked.
Finally, the default slide trigger is not working. It's supposed to jump to a slide when the timeline ends but nothing happens.
Could these issues be associated with the _root error?
We have the exact same issues but worse with .SWF files. The Previous button will direct the user to the correct slide but the audio doesn't stop, I added a trigger and it fixed the error, however, if the user goes back to the slide with the .SWF video on it, you hear audio and see no video and to make matters worse, when you select NEXT to reach the next slide the audio keeps playing and no trigger whatsoever will make it stop. Our entire project is on hold until they come up with a workaround. I am very disappointed about the .SWF issue as it worked just fine in Presenter 09, feel like we just went backwards and wasted 2 weeks troubleshooting to no avail.
Hi Maya,
Glad to see I'm not alone. I believe the _root error problem was due to a Cp quiz slide. I deleted it and recreqted it in SL and the error went away. One HUGE disappointment, however, is that rollovers created in Cp do not work when imported as .swf into SL and video controls are enabled. I agree that SL should have at least the same functionality as Presenter.
=Diane
Hi Maya,
If you'd like, we'd be happy to take a closer look at it. Please submit a case, including your .story file, using the link below so our support team can assist you further:
http://www.articulate.com/support/contact/submit.php
Thanks!
Hi Peter,
We have already submitted a case, the support team is working on it but has yet to find a workaround. Running out of time. :(
Hey Maya,
Shoot, sorry for the trouble and the time crunch. Do you have your case number handy so I can check on it?
Case #00301861
Thanks, Maya. Looks like you're working with Cleo on this one. Good luck with the project
Did this issue ever get resolved for you Maya? I'm having issues as well with .swf files inserted in Storyline. I have 3 .swf files I'm trying to play back to back with auto advance from slide to slide. They are looping on themselves and at other times not completely finishing before jumping to the next . It's a nightmare. We have given up on Storyline for this deliverable and rolled back to an Articulate solution. I'm just curious if there was a fix on this. And yes, I have the latest updates to Storyline.
Cindy,
No, Articulate did not have a solution for us. We have an idea for a workaround for our .swf issue but due to the time constraints chose not to utilize it on the last training launch, it has yet to be tested in production.
Our second best solution was to launch the training modules which did not have video and subtitles (creating our .swf issue) in Storyline, the modules which contained video and subtitles were left in Articulate where they worked properly.
Thank you. Your post has been very helpful. We have a pilot on Monday. This has been driving me crazy with the "unpredictable results".
This discussion is closed. You can start a new discussion or contact Articulate Support.