Captivate 8 - Runtime Error R6025 - Pure Virtual Function Call

[lianeng]

My teammates and I have Captivate 8 installed recently and while working on a big project for a client, some of our files got corrupted. We couldn't open them and we'd get a Runtime Error R6025 - Pure Virtual Function Call. Some members of the team could still open those CP8 files but eventually, everyone got the error and we couldn't open the files anymore, even if they were backed up several times.

Anyone have the same problem? We are suddenly having regrets purchasing all those Captivate 8 licenses. Captivate 6 never gave us this problem and it really had to happen with a big project for a client.

[RodWard]

You've already posted this question on another thread a few moments ago.  Please do not double post questions. It's viewed as impolite around here to do so.

[lianeng]

I started this thread with proper tags because my main focus is the Runtime Error R6025. The other thread is about corrupted files. I need this question posted because no one has ever posted about Captivate 8 and this Runtime Error. Hope you understand. Thanks!

[Meganrcmacd · Accepted solution]

Just responded to this in another thread (note we used Captivate 7 so it might be a different error).

We found that when we created files with embedded swf files that existed ABOVE widgets in the timeline, when someone else tried to open our file it broke/we got the runtime error. The original person could still open it for a time, but eventually the cache would clear and they couldn't.

However, if we ensured swf files are BELOW widgets in the source files, it didn't break. In fact, if we found one that was breaking and got the author to move the swf file on the timeline, it would start working for others.

STRANGE! Let me know if this works for you to!

[Srinivasan_T]

Hi,

Thanks Meganrcmacd, the above solution worked perfectly.

[R_H__]

Worked a treat, cheers!