Forum Discussion

KirstyTeare's avatar
KirstyTeare
Community Member
3 months ago

Issues when in Preview - Storyline

Hi All  I am having issues when I set a slide to preview, I have checked and worked out that when I have this trigger: Set state of: text box to State1, when Object 1 intersects with Object 2 set u...
storyline 360
KirstyTeare's avatar
KirstyTeare
Community Member
3 months ago

Hi all, I have been checking some more and found that whenever I add a change state from an object intersect, the trigger either does not work at all, or stops the preview from working. 

Any help would be appreciated.

EricSantos's avatar
EricSantos
Staff
3 months ago

Hi KirstyTeare,

Thanks for sharing these details and for digging into what’s happening. What you’re describing sounds like it could be related to a confirmed bug in Storyline 360 where a slide appears blank in preview if an intersect trigger is applied to an object that’s part of a group.

Could you check whether the object you’re targeting with the intersect trigger is grouped with another object? If so, try assigning the trigger to the group instead of the individual object. That should let the slide preview correctly while our team works on a fix.

I really appreciate the time you’ve spent troubleshooting this. It’s a big help in tracking down issues like this one.

  • KirstyTeare's avatar
    KirstyTeare
    Community Member
    3 months ago

    Thanks Eric. 

    I have found a work around by using the trigger of when the object enters the screen, although not the smoothest way, it is working. 

    I have sent the project into the team also so hopefully a fix can be found soon! 

    Thanks for the reply! 

    • EricSantos's avatar
      EricSantos
      Staff
      3 months ago

      Hi KirstyTeare,

      Thanks so much for sending your project to our support team! I can confirm that Carlo linked your case to the known bug where slides appear blank in preview when an intersect trigger targets an object within a group.

      It’s great that you found a temporary workaround using the “object enters the screen” trigger, that’s a clever approach while our team continues to work on a fix.

      We’ll keep this discussion updated once the fix is released. Thanks again for sharing your file and helping us confirm the issue.