July 25, 2019
Swf Compilation failed Note: Please verify if any of the actionscript keywords is used as user variable name.
Comments
(8)
July 25, 2019
Swf Compilation failed Note: Please verify if any of the actionscript keywords is used as user variable name.
Newbie 1 posts
Followers: 0 people
(8)

Hi- I just downloaded my free trial and recorded my first software simulation. When I try to preview it, I receive this error message. I uninstalled and reinstalled Captivate, but it didn’t help. Any ideas?

I’m anxious to get started but am at a dead stop until I can resolve this.

Thanks in advance.

8 Comments
2019-11-27 19:41:45
2019-11-27 19:41:45

Is there an answer to why I am unable to publish to video, when the file has no actionscripts and I get this error?  Just upgraded my computer to windows 10 I’ve had nothing but captivate issues!!

 

Like
()
(1)
>
julieh90022040
's comment
2019-11-28 08:31:02
2019-11-28 08:31:02
>
julieh90022040
's comment

Can you please clean the Preferences and offer more details if you really want help. Are you on Windows or Mac, first question because the most recent version of CP is not compatible with Catalina. Captivate works fine with Win10.

Do you want to publish to mp4, the only video format available for output? Not interactive, would be strange if you get that same error, although it may mean that you try to upgrade an older project, and the used theme has not been upgraded neither. Or you are using deprecated functionality? Do you run Captivate with the setting ‘Run as Administrator’?

Like
()
2019-07-29 12:58:31
2019-07-29 12:58:31

Here is my solution from a while back that I posted on the Adobe Elearning Forum

Like
()
2019-07-29 12:54:20
2019-07-29 12:54:20

Along the lines of what Lieve said, have you tried to publish in HTML 5 format only? Unselect the .swf format and uncheck the zip files box when you select publish to my computer. If that works then go to the output folder and try to launch the file. I would consider moving away from .swf based projects at this time simply because more browsers are starting to block it by default as well as most company security policies.  Without knowing your specific target market I would humbly suggest moving away from flash-based output as you may end up having to republish and rework content when adobe flash hits end of life here in the near future.

Like
()
(3)
>
Wayne Armstrong
's comment
2019-07-29 13:03:10
2019-07-29 13:03:10
>
Wayne Armstrong
's comment

@Wayne The problem stated in the question is about Preview, not about Publishing. It is very annoying and confusing for newbies that all Preview methods except F11  are using temporary SWF output which complicates the situation more and more since we are getting near the end of Flash player.

Like
()
>
Lieve Weymeis
's comment
2019-07-29 13:20:55
2019-07-29 13:20:55
>
Lieve Weymeis
's comment

Lieve Weymeis I don’t disagree. My point still stands that moving away from flash if possible would probably be best practice. Also stands to reason that if the preview is having the issue so will publication. Having options and different approaches to solving a problem is one of the benefits of being on the eLearning forum. Thanks for being such an active member.

Like
()
>
Wayne Armstrong
's comment
2019-07-29 13:49:07
2019-07-29 13:49:07
>
Wayne Armstrong
's comment

Sure, Wayne. I just didn’t want to overload a newbie and try to give him a direct answer to his question. I have not published to SWF since years.

Like
(1)
2019-07-29 08:21:52
2019-07-29 08:21:52

Software simulations means you are in a non-responsive project.  Can you please try the ‘Preview HTML in Browser’ (F11) method? Is that showing a preview? The other methods are all based on the creation of a temporary SWF output, and Flash Player may be disabled in your browser.

Like
()
Add Comment