SWF Compilation Failed message

[Chris-BJ]

I was receiving the  "Swf compilation failed. Note: Please verify any of the actionscript keywords is used as user variable name."  message.

So I uninstalled Captivate, restarted the computer, installed a new download file. 

2019 Release - version 11.8.1.219 -

I start the program, choose a blank project, press the F12 key, the program goes through the process and then shows the above error message.

On a Windows 10 Pro for Workstations, version 22H2 OS 19045.3086

Please help

[Lilybiri]

F12 key was to open the SWF output version of a project in a browser. Version 11.8.1 was meant to have taken out all SWF features, but (although I mentioned this during beta release) this one has been forgotten.

The only valid shortcut key for a non-responsive project Preview is now F11, which is the same as Preview HTML in Browser. Don't be confused by seeing 'Preview Project' as well, because it does exactly the same preview and has the same shortcut key F11.

[Chris-BJ]

Thank you for your help. I am now able to preview my project as an HTML.

But, when I go to publish as a video (MP4) I receive the same error. It looks like it fails about at the 75% point.

I went into the project and removed all vaiables (I was not using them) and this is not an interactive lesson.

I also took the project off the cloud folder and am only working in the local folder.

Please help.

[Lilybiri · Accepted solution]

I already suspected that SWF-technology is still used when publishing to MP4 because the slide transitions are functional. Do you have slide transitions?

The message could also be an indicator that something got corrupted in the project. Could you try to hide some slides (maybe those after the 75%)  and see if publishing works in that case? 

[Chris-BJ]

Hello - there were no slide transistions. The only "transition" was a text box that was visible over 4 slides with no fade out/in between each slide (#12-#15).

I did as you suggested and hid all slides from #20 to #25. Then I was able to successfully publish the project. I then selected the next 2 slides to show and republished. I continued with that process until all slides were again showing and was able to successfully publish the entire project with no changes.

So, I don't know what the solution was 🙂 but am glad that the project now successfully publishes to Video.

I will remember this "trick" if I again have an issue with publishing.

[Lilybiri]

You're welcome. That 'technique' is mostly use to find a corrupted slide or item. I am a bit surprised of your result because there seems not to be a corruption. Another weird situation, but your problem is solved!

[Kathy24474360ezia]

I know this is resolved for you, but in case others stumble on this when having the same problem, it was resolved for us at least by changing the location of the Project Cache folder to a local folder instead of a One Drive one. One Drive gave us errors that some of the files generated had names that weren't allowed. Once we changed the cache folder, we could publish fine to a one drive or a local folder.  

[Lilybiri]

Especially in the New Captivate OneDrive needs to be avoided, which was not necessary for me in previous versions. Even the new Captivate Classic has the same 'sensibility'.

[Kathy24474360ezia]

Good to know. We're not using the new Captivate yet, but will be at some point.