Forum Discussion

KevanNorr's avatar
KevanNorr
Community Member
2 years ago

Triggers that reference the Normal state broken again as of the July 27 update

This bug reappeared in the July 27, 2023 (Build 3.78.30747.0)

July 18, 2023 (Build 3.78.30680.0)
Fixed: Triggers that referenced the normal state stopped working.

I have a project that was delivered in May that uses radio buttons and specifically uses a condition that checks the Normal state in order to play a layer on user click. The project had an update yesterday on totally unrelated slides and when posted to their LMS the client reported that these slides no longer functioned properly. The project was built using the latest Storyline update (July 27, 2023 (Build 3.78.30747.0))

I went through and verified that the slides work as intended in every version before the July 27 update. I was unable to install the July 18th version as it was not available in the list.

I'm not sure where to issue bug reports but I thought you might like to know about it.

storyline 360
  • Jürgen_Schoene_'s avatar
    Jürgen_Schoene_
    Community Member
    2 years ago

    you can here open a support case

    to clarify

    • 3.78.30747.0 (07/27/2023) don't work
    • 3.78.30680.0 (07/18/2023) unknown*
    • 3.77.30587.0 (06/22/2023) is ok

    if you upload a small example .story file with the error - I can test it with more versions*

    * I have in my archive all SL versions since Jan 2022

  • KellyAuner's avatar
    KellyAuner
    Staff
    2 years ago

    Hi Kevan,

    Thanks for reaching out and I'm sorry to hear you're experiencing this issue!

    I see you connected with my teammate, Lianne, in a support case, and they confirmed this has been logged as a possible software bug. In the meantime, a workaround is to try using a different state aside from the 'Normal' state.

    I hope this helps!

    • Jürgen_Schoene_'s avatar
      Jürgen_Schoene_
      Community Member
      2 years ago

      if this the well known very old bug with checking "normal"

      then the workaround is to check e.g. with "not selected"

      (but this error can not be in this case - SL 3.77 apparently not shown the error)

Related Content