SWF playing error

[Guest]

Hello,

I've created moving balls in Adobe Animate CC 2017 and then exported into SWF file. The animation is based on Action Script 3.0. I've a problem when imporing the file in Adobe Captivate as the file won't play. The file in the following link:

Dropbox - balls2.swf

[Lilybiri]

How did you import? Normal work flow is with the Media button, Animation.

[Guest]

Yes, but when it imports, it shows white rectangle only and the SWF is not played.

[RodWard]

Make sure the publish folder location has been set as a trusted location in your browser's Flash Global Security settings.

[Guest]

I did that before but the problem still exist

[Lilybiri]

How did you test: with Preview in Browser (F12) or after publishing? Is the animation set to play automatically or did you insert a button to start playing?

[Guest]

I used both methods (preview in browser) and after publishing. The SWF file plays automatically. You can see it in the link I posted/

[eLearning Guy]

I'm seeing a similar issue when testing your swf in a blank project here. Notice that it does play correctly when previewed within the Captivate editor (i.e., press the space bar when viewing the timeline in Cp). But does not work on preview or publish.

Which version of Flash Player is the swf published to? If possible I would drop it down to a lower flash player target and see if that helps, though doubtful. Another thought, which I think is more likely the culprit - are you targeting the root timeline with any actionscript? It's been years since I bothered publishing anything to Flash but I do recall that being an issue, as basically you're loading your root timeline into a new one generated by Cp at runtime.

If you can post the source .fla I can take a look.

Mark

[RodWard]

Pressing the spacebar (or even F3 key) in the Captivate Edit view window is NOT an effective test of how an SWF project plays when published.  You are just playing the timeline, NOT publishing to SWF by doing this.

I still think there is a strong possibility your issue with the published SWF not playing is due to Flash Global Security.  But a lot of people don't realise that it's gotten much more complex recently to set this up on your system.  Setting it up in the Flash Player Manager app in the Control Panel DOESN'T mean that it is automatically set up for each and every browser you are using on your system.

The best test is to upload the Flash content to a web server and test it from there.  If it plays from a web server, your issue is Flash Security when played locally.

In many browsers nowadays you have to manually configure the Flash security by using the web-based tool provided (originally) by Macromedia.  To get to this web tool you need to start playing the content in a browser, then right-click on the browser window and choose Global Settings from the context menu.  When you do it this way, you are directly configuring it for the specific browser you are using at the time.  But even with this tool it's a little unintuitive to configure a folder as the trusted location.  The quickest way is just to type in the path to the highest level folder that will contain all of the content you might ever want to test.  If you set up a special Publish folder on the C drive and always publish into that, then this task will be a lot easier.

[Guest]

As I commented before, I've no problem with the security folder as I'm using the trusted one as set in Flash setting in the control panel.

Yes, the SWF file works with browsers such as Firefox or Explorer. You can check the that file was uploaded in the question!.

[eLearning Guy]

The reason I mentioned that it works in the Cp timeline preview is to verify that the swf itself functions properly. The first step in troubleshooting this type of issue is to ensure that the actual swf in question is valid, and it is.

[Guest]

Kindly see the .flv file as bellow:

https://www.dropbox.com/s/7kp3zi2tdutlylv/balls.zip?dl=0

Thanks

[eLearning Guy]

I took a quick look at your project and...

Here's the bad news: it's definitely something conflicting with Captivate. My guess is the physics class being used (as I type this, I should have tested that in a separate project to verify, but I didn't think to do it).

The good news (somewhat) - a workaround - you can:

• Publish your project as an OAM file and import as an HTML5 animation in Cp. This isn't as smooth as swf though, but it does work.
• You can publish your project to include an html wrapper, zip up the output (so a zip containing the html, swf, com directory), copy it to your local deploy folder, then in Cp use a Web Object to load it into your project. I prefer this method over OAM. Another thought - if you can just host it separately, you could always push the project to a server and then just insert the URL into the Web Object. That would result in good performance.

Hope that helps. If you're really set on sticking with just the swf import, then try emailing Captivate support and provide them the file. I doubt you'd get a quick resolution, but maybe worth a shot. There was nothing in your .as code that would obviously conflict, though of course the physics class' stage manipulations may conflict with the stage as it is instantiated by Cp at runtime.

mark