I am trying to create a muti-path branch (with more than two options) that will score based on the path the user takes, allowing the user to gain some points when they don't answer correctly at first.
The scenario is as follows, with each choice a distinct slide:
Choice 1 - best answer (10 pts) -> jump to end of interaction with 10 points Choice 2 - good answer (5 pts) -> jump to Choice 2 follow-up Choice 3 - wrong answer (0 pts) -> jump to Choice 3 follow-up
(Choice 2 follow-up) Choice 2a - right answer (+2 pts) -> jump to end of interaction with 7 total points Choice 2b - wrong answer (+0 pts) ->jump to end of interaction with 5 total points
(Choice 3 follow-up) Choice 3a - right answer (+1 pts) -> jump to end of interaction with 1 total points Choice 3b - wrong answer (+0 pts) ->jump to end of interaction with 0 total points
At the end, I would like to see a total score out of 10 maximum points.
I have this working by using click-boxes instead of question slides, with all click-boxes associated to the same question. The only probelm is that the total points is showing, in this case, as 18 - in other words, all click boxes associated with the question count toward the total, even though, as you see, there is no way to get more than 10 point (that is, by choosing the best answer first).
I realize that, as we often do, I am trying to push Captivate with respect to quiz complexity. :)
I also realize that, if there is no other solution, I could set the question to report points instead of percentage to the LMS, and it will work for my needs, most likely. Unfortunately, I would then need to design any interaction for 100 pts total, or adjust LMS score settings for each course. This is not a good path when considering maintenance - changing interactions may require recoding scores in the LMS or Captivate piece.
Anytime you're using Captivate in ways the Captivate developers hadn't planned, things get sticky in a hurry. :)
If I understand you correctly, everything works *except* the way the score is displayed. If that's the case, I'm not sure what you can do, as the score display is pretty hard to customize. Your suggestion about using percentages sounds reasonable to me.
If you want to get really hardcore you could edit the ActionScript files that ship with Captivate:
These files handle all of that stuff, from tracking code to slide displays and LMS communication. I've messed with them from time to time. The downside of modding them is that if anyone else in your team uses Captivate, they'll need to have the same ActionScript mods in order to publish. Non-standardized installations are difficult to maintain/manage in a group environment.
It is not so much how the score is displayed, but how the score reports to the LMS. (I think you know what I mean.) This will work, and I definitely won't be messing with the Captivate source AS files for this.
Thanks, Phillip. As usual, this is the place to go when I have an advanced Captivate question.