SL crashes when using markers

Hi Harri,

Have you tried this function without the grouped triggers?  Somehow, grouping markers causes issues in preview and after being published.

Hi Brian,

I'm not too sure what you mean by this. I haven't grouped any of the markers I've just set triggers so that clicking one will affect another one's state.

Can anyone else shed any light on this matter???

Hi Harri,

Can you share your .story file here so that we can take a look? Or if you'd prefer not to share in the forums, please feel free to submit a Support case. 

Hi Ashley,

Here's the troublesome slide (apologies but I've had to remove the marker content)

If you click any of the orange markers, the other orange markers should change to their visited state...however this doesn't happen, instead SL crashes.

Hope that makes sense

Hi Harri,

Thanks for sending along your file - this is certainly a tricky one. What I tried (to no avail) was first importing it into a new Storyline file - still crashed. Second, I tried setting each marker to only change their state based on one other marker (instead of the multiple option you have set) that did not crash Storyline. So then I went and created additional object triggers for each marker, with only one other markers state to look at to decide to change...and crash again. 

So with that, I've gone ahead and submitted a Support case on your behalf (case # 00349444 ) and I'll follow along to keep the thread updated. 

Hi Ashley,

Thank you. I really hope this can be resolved as I don't want to force learners to view 4 identical markers but I can't remove them as the client wants the duplicate markers onscreen.

Thanks again

I hope to too Harri - and I'll follow along to keep the thread updated. 

Hi,

Just to update the thread....

I've had a response from the Tech Support guys......I did indeed break Storyline :(

It's been reported to the Quality Assurance team for review but for the time being there is no fix or workaround....

I guess I'll need to look at different ways of approaching this client request

Another update from me - just in case anyone else encounters this issue.....

I found a workaround that appears to function.

1- set up true/false variable

2- change variable to true when user clicks on the 4 orange markers (4 separate triggers)

3- change state of markers to visited when variable changes

Thanks Harri for both the updates - and I'm glad our Support team figured it out. Thanks for also sharing the work around for others!