Skip to main content
Known Participant
February 20, 2024
Question

Captivate 12 "Something went wrong"

  • February 20, 2024
  • 1 reply
  • 691 views

HI,
Been using the "All new" Captivate this week for a project. Primialrily because it seems to have a better repsonsivness workflow than classic.

Done a quick test with about 8 slides, and it all seemed to work. So have since built out the full app totaling 76 slides
How ever, no when I preview, or publish it and run it on SCORM Cloud, I have only managed to get a maxmium of 5 slides in before I get a " Something went wrong!" message.
But other than that I get no other messages or errors, unless I am looking in the wrong place for logs?

Any one have any idea what may be causing it?
Is this a know bug

My app is fairly simple.
Using Image blocks for layouts, and putting interactions on the buttons to change states and go to next slide.

Ay insight would be greatly appeciated!
Cheers!

This topic has been closed for replies.

1 reply

Lilybiri
Legend
February 21, 2024

Your test on SCORM Cloud proves that something is corrupt in the Captivate file.

The normal troubleshooting workflow is to try to find the culprits. You could try to hide a majority of slides and upload them in small bunches to try to identify the cause but it is a lot of work. In former versions I would recommend to copy/paste the slides one by one to a new project which uses the same theme. Importing Preferences is not possible AFAIK in the new version.

My first suspicion would go to the interactions, I also got several issues with them.

Known Participant
February 22, 2024

Hi Lily

Thanks for getting back to me.

I will have a go at going through the slides and removing my interactions to see try work out what is happening.
I have only been getting as far as slide 6, so will start there.

Just for reference
My inteactions only have like 3 conditions to them.
On my Question slide its is just " Adjust Variable x from 0 to 1" "Jump to next slide with 0.5 delay"

My answer slides are " Check is variable X is equal to 1" change state of Button to state 2, else use state one" 
Ands this is duplicated for the about of answers per question.

Will post back with my findings.

Lilybiri
Legend
February 22, 2024

It is a lot of steps back for interactions, due to the loss of advanced/shared actions where you could see the full interaction in one glance, and the Advanced Interaction overview panel to find bugs in one place. Especially when you are using a combination of conditional actions, where the sequence is so important. I really don't know why they make it so hard. Due to the type of consultancy jobs I have done, it was often possible to find probable bugs in minutes, in the new version it takes hours to analyse all interactions in a - for me - very complicated UI for that type of work. I'm sure this type of problem could have been solved very quickly in CP2019 in a much shorter thread than now is already here and still without solution.