Skip to main content
Jap0607
Participant
January 25, 2017
Answered

Captivate 7- FMR in SWF Files Suddenly Not Working in Chrome 55 & IE11

  • January 25, 2017
  • 1 reply
  • 319 views

I've created a simple course in Captivate 7.0.1.237 and published to SWF. When I open the SWF (from the htm file) in Chrome 55 and IE11, it hangs up on the FMR slides and just displays a black loading icon over a static slide until the slide ends and it moves on, instead of displaying the actual recording. I've never had this problem before now. I'm working on a Windows 7 Professional computer.

Here's my publish settings:

Output: SWF

Output Options: Zip Files//Flash Player 10

Advanced Options: Force re-publish all the slides

Project Information:

Resolution: 1101x790

Slides: 298

Slides with Audio: 258

Audio Quality: MP3, 96 kbps, 44.100 KHz

eLearning Output: SCORM 1.2

My SWF Size and Quality Options:

Retain Slide Quality Settings is checked

Advanced Project Compression is Checked

Compress SWF File is Checked

I've also tested older courses I built with the same settings in the last year, and they are all having this issue now--when they were working fine before in both Chrome and IE (I did not republish them--I tested the files I published originally). I also had a colleague download this published course and an older one to test--same issues on their computer

Thinking it was simply the file size was too big, I halved the slides in the project, and published again--same issue.

While troubleshooting this particular course, I've adjusted the Flash Player version, compression options, and the force re-publish option to no avail. I've run CleanPreferencesWin.bat and republished. I also set Chrome to allow all flash as a last-ditch attempt to figure out the issue, and the problem persists.

Does anyone have any suggestions?

This topic has been closed for replies.
Correct answer RodWard

If you and your colleague are playing these files locally on your systems (rather than over a web server connection) then I would say the most likely reason for your issues is that your local Flash Global Security settings have somehow been wiped out (probably by some update to your browsers or OS) and you need to re-establish those Flash Global Security settings again so that the publish folder locations are again trusted locations.  You will usually now need to do this separately for each individual browser.

Simply open one of these projects and when it starts playing, right click on the slide area and select Global Settings from the pop up Flash context menu.

When the Macromedia web page opens, click the link to Global Security Settings panel, and set up your publish folder locations as trusted locations.  If you want to save yourself some future surprises, set up the folder at the highest level so that it will contain the folder locations of all projects you publish.

You can also test whether your issue might be related to Flash Global Security by just uploading one of your current projects to a web server and testing it from there.  Since you mention you are using SCORM, you could do this by uploading the SCO to SCORM Cloud.

1 reply

RodWard
Community Expert
RodWardCommunity ExpertCorrect answer
Community Expert
January 26, 2017

If you and your colleague are playing these files locally on your systems (rather than over a web server connection) then I would say the most likely reason for your issues is that your local Flash Global Security settings have somehow been wiped out (probably by some update to your browsers or OS) and you need to re-establish those Flash Global Security settings again so that the publish folder locations are again trusted locations.  You will usually now need to do this separately for each individual browser.

Simply open one of these projects and when it starts playing, right click on the slide area and select Global Settings from the pop up Flash context menu.

When the Macromedia web page opens, click the link to Global Security Settings panel, and set up your publish folder locations as trusted locations.  If you want to save yourself some future surprises, set up the folder at the highest level so that it will contain the folder locations of all projects you publish.

You can also test whether your issue might be related to Flash Global Security by just uploading one of your current projects to a web server and testing it from there.  Since you mention you are using SCORM, you could do this by uploading the SCO to SCORM Cloud.

Jap0607
Jap0607Author
Participant
January 27, 2017

The Flash Global Security Settings was the problem! Thank you so much for your help!