Skip to main content
L
LWDavidson
Known Participant
April 12, 2024
Question

New Captivate 12.3 Not Opening Up Large Captivate Files

  • April 12, 2024
  • 2 replies
  • 1909 views

Dear Community,

While I work with Adobe Support on this issue (see below), I'm posting here as well.  Perhaps someone has experienced a similiar issue when updating their New Adobe Captivate to the recently-launched version (12.3) and can provide me with some guidance/insight.

 

Since updating to the 12.3 version, my project files are not opening properly.  The software program buffers and then generates the following error message ("An unexpected error has occurred, which may cause Captivate to behave unexpectedly. You can restart Captivate with backed-up project.").  I have tried but cannot figure out how to restart my project with the BAK files.  I tested it out with a work colleague of my mine; they can open the same project file on their computer.  They did not update their Captivate to the latest 12.3 version.

 

I have tried to uninstall and reinstall a fresh version of Adobe Captivate.  However, the fresh online version seems to be with the 12.3 updates.  Still experiencing the same error message.  Also, the project files that are ‘not opening’ and generating the error message are rather large (around 2,000 MB).  I’ve tested the updated 12.3 Captivate with some smaller project files (200 MB) and they are opening properly.  No error message.

 

I am using Windows 11 Enterprise, version 21H2.  The project files in question are located within a OneDrive work account.  I know cloud computing can cause issues for Adobe Captivate; however, I didn't have a problem with them before this update.  Also, the smaller project files that are opening properly are still located within that OneDrive cloud folder.  I have since moved the larger problematic files to a non-cloud folder on my C:/drive.  Still cannot open them.

 

Thanks in advance for any guidance you may offer.  This has completely halted my work.  So frustrating.

    This topic has been closed for replies.

    2 replies

    L
    LWDavidsonAuthor
    Known Participant
    April 25, 2024

    For anyone who might have been following this issue, I am going to share the results in this post thread.  No explanation behind the phenomenon, but it was a 12.3 version issue.  As soon as I was able to convince Adobe Support to share with me CP 12.2 (before I updated), all of these large 'problemmatic project files' became accessible once again.  I can open them up, edit, and have been able to reduce down to a manageable size with the 'remove unused items' option under the File dropbox.  Brought the files down to around 950 MB each.  

     

    Took two weeks to solve and a halted timeline in development, but hey, lessons learned I guess?  Do not update while in the middle of a build.  I never had to consider that before with other programs.  Sigh.  Oh well.     

    Lilybiri
    Lilybiri
    Legend
    April 26, 2024

    This ia partially due to hiding that functionality. In Captivate Classic when the Project Library had too much unused items a warning appeared automatically. BTW you had full control over all the warning messages and could override the defaults, which is now lost as well.

    Often wrongly told as a solution for output which is too big: deleting unused items will NOT decrease the file size of the output folder. I even read it here recently and had to correct it.

    Lilybiri
    Lilybiri
    Legend
    April 12, 2024

    I never had issues with OneDrive neither, until this version. I would move them outside of the location which is synchronised with OneDrive to check it out. It is very annoying but I don't use OneDrive anymore for Captivate projects in that new version.

    Those files are HUGE, that is not normal. Are you using a lot of video, audio? What is the size of the output folder?

    L
    LWDavidsonAuthor
    Known Participant
    April 12, 2024

    You are correct @Lilybiri, the project does include embedded video.  They are episodic.  The video itself is around 405 MB.  You will have to clarify for me.  I'm still learning Adobe Captivate.  Which folder is considered the 'output' folder?  Are you referencing within the SCORM package (or what is published)?  Or something else?   

    L
    LWDavidsonAuthor
    Known Participant
    April 12, 2024

    @Lilybiri, as the expert and top contributor in this community, perhaps you can help me better understand a quirk of Captivate.  Or I am misusing it somehow. 

     

    I've just realized, looking into this issue, that the project files keep getting bigger and bigger.  Again, what I am building is episodic--a distance learning on-demand course for ESL students.  So Episode 1, 2, 3, etc. etc.  Each episode includes a preview, the embedded episode video itself (as I mentioned before, around 405MB in size), and two checkpoints to check for comprehension of the story in the video.  An entire episode captivate file is between 30-35 slides in total.

     

    Because the episodes are very formulaic, and what I originally built in Episode 1 can be used like a template for Episode 2, Episode 3, etc, my workflow for this project so far has been the following...

    1) Upon completion of one episode, 'save as' that file and then create the next episode file from the previous one.  So change the file name (from Ep 1 to Ep 2).

    2) Change the content within it (i.e.: different episode video, different comprehension questions, different previous episode images, etc.).

    3) Once done, repeat Step 1 and 'save' as' to the next episode file (from Ep 2 to Ep 3).  Rinse and repeat.

     

    I have realized each episode captivate file increases in large increments.  Episode 1: 1,700MB.  Episode 2: 2,400MB. Episode 3: 3,600 MB. Episode 4: 4,600MB. Episode 5: 5,500 MB.  What the heck is going on here?!  Is this somehow related to cache files not being cleared when I am essentially copying all episode material into a new file?  My project has 16 episodes in total.  This seems completely unmanageable. 😞  I also don't want to build each episode from scratch--and all of the interactive components within each slide.  Especially since they are so formulaic.        

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices