Forum Discussion
States No Longer Working After Latest Update
I'm hoping that this is an easy fix.
I installed the most recent update to Articulate 360 and my Storyline is misbehaving big time.
I have several modules (due NOW) that were set to change state when the user clicked, then jump to a slide. At the end of that section, the Learner returns to the Main Menu.
Well... the state is not saving. I go back and it is not changed. It was working fine before the update. Any advice?
18 Replies
Since it worked before, I suggest you revert to the previous version. You can do that from the Articulate 360 app.
I also suggest you report the issue directly to Articulate. You can do that here: https://access.articulate.com/support/contact
Judy, i have the same problem and still do. My projects were due last year. It actually has driven me to madness as I feel I am losing my mind and tears, and sometimes it works fine then sometimes it doesn't.
Articulate told me that it was a problem on my end. Sent a few tickets from different slides (No longer working on OneDrive, Updated RAM, Updated memory, Clear articulate cache weekly, and dropped some money and now working on a Macbook as opposed to PC). I've redone the slide and still have the same problem. Sometimes the states change and sometimes they don't when viewing in ScormCloud.
I had state behavior attached to Next button turning to normal state for the student to proceed with the class. I have now removed the Next button tied to changing states and will publish my class that way to at least put something out there in training land. Meanwhile I do need to figure out what the problem is.
When you went back to a later update did your state problem stop or have you found a resolution?
I haven't had any problems with states. I simply replied to Kristina about what she could try.
Kristina, i have the same problem and still do. My projects were due last year. It actually has driven me to madness as I feel I am losing my mind and tears, and sometimes it works fine then sometimes it doesn't.
Articulate told me that it was a problem on my end. Sent a few tickets from different slides (No longer working on OneDrive, Updated RAM, Updated memory, Clear articulate cache weekly, and dropped some money and now working on a Macbook as opposed to PC). I've redone the slide and still have the same problem. Sometimes the states change and sometimes they don't when viewing in ScormCloud.
I had state behavior attached to Next button turning to normal state for the student to proceed with the class. I have now removed the Next button tied to changing states and will publish my class that way to at least put something out there in training land. Meanwhile I do need to figure out what the problem is.
When you went back to a later update did your state problem stop or have you found a resolution?
Hi, could you post your story file?
I would love too, but can't post on a blog. I am wondering if it is the file size, 486 MB, (it was bunches bigger, but i compressed video) is causing the issue, and that my IT infrastructure doesn't like that. I asked client if I could break file up into two classes, but that was a hard no.
I've also tried to have states change when:
- linked to cue
- linked to beggining or end of timeline
- linked to a variable changing
- linked to media/video ending
and, the slide still acts inconsistent, with state changes. They will work here, but not there and then I reset course and then they don't work here, and will work there. Nothing changed that i am doing except resetting the course in ScormCloud to retake.
**I may have found a sorta solution. I had many assets "show until the end". When I adjust those from "showing until end" and then have the layer "hide when timeline complete" it appears to have fixed the problem. Does that make sense to you?
Hi JenWest​!
So sorry to hear you've been having trouble with the playback of States in Storyline!
I see that you had previously been working with my teammate Darrell, through a support case. It looks like he replied to your e-mail with a test link to be used for further troubleshooting. It's possible that e-mail slipped by. No worries! I am resending it again for your reference, so you can reconnect with Darrell.
We can continue the conversation through your case!
It has been a crazy roller coaster with this class I have trouble remembering what I did each day with this course. I can assume that Darrell's link for a slide to my class worked once, then didn't because I'm still here trying to fix the issue - which I believe I found a go-around. I will discuss this in the Articulate case chat, and also update chat here. Tx
I am having the same issue from an accessibility standpoint. The slide has a button on the main slide that goes to a layer on that slide. The user clicks a button on the layer that returns them to the main slide. The button on the main slide changes "appearance wise" to the visited state, however JAWS is not recognizing the visited state for that button. The only way to recognize the visited state by JAWS is to go to another slide and then return to the slide, at which point JAWS will state the button is visited.
Tried everything I can think of but nothing is working to get JAWS to recognize the button is visited when returning from a layer.
Hi BelindaSpohn​!
Sorry to hear that JAWS is not dictating your Visited Button States consistently!
The behavior you shared sounds similar to a bug we fixed in Storyline 360 version 3.103.35242.0. This bug prevented screen readers from announcing Alt Text in the Visited State of Buttons or Shapes. Does the issue still occur when publishing your course from version 3.109.36125.0?
If so, it would be helpful to see a copy of the .story file that's giving you trouble. Do you mind uploading that here in the discussion or privately through a support case?
Looking forward to hearing from you!
I am experiencing the same issue. It occurs both when building and once publishing.
Lorena, what is crazy about it is this was not a problem in the past. Something changed in fall. I've dumbed my project down to deal with my issues. Killed jumping to other slides and back and brought as much as I could on the same slide (can't use transitions then:() Removed a lot of hover states i didn't feel necessary (this seemed to have helped a bunch). Also removed the hover triggers.
Yes! I've been using slide layers instead, but it's more work to set up.
I am experiencing the same issue. It occurs both when building and once publishing.
