We opened a .story file using the new March 2019 version of Storyline 3. The .story file had been created using the May 2018 version of Storyline 3. The triggers are garbled on the base screen and on screen layers. We can click and edit the individual triggers. It does not happen on all screens. Suggestions? See attachment.
Hi there, Tracy. We've seen this issue from just a handful of customers, and undocking/redocking the trigger panel helped restore it.
We haven't been able to nail down this bug yet, but I'm going to add your details to our report. We'll update you with any new information in this discussion!
Thank you Crystal! I opened the same file and it did not garble. The developer who brought it to my attention closed his .story file and reopened it - and the issue went away. Several other developers in our organization said it has happened intermittently to them in other Storyline 3 versions. One of them found a pattern - it seems to only occur on the “Change the state of” triggers . The next time we will use your tip and undock/dock the trigger panel.
Thanks for sharing those details! We've added this discussion to the report our team is investigating and we'll keep you posted here.
Also, since you mentioned sharing files, I wanted to check that you're all working on those .story files from a local drive (vs. sharing them on a network/shared drive). The network/shared drive is one of the items known to cause odd behavior ultimately leading to corruption, so following these best practices should help prevent other odd behavior.
I had this issue a couple of months ago with a project converted from Storyline 2 to 3. I submitted a support ticket, but was told it was not reproducible. I figured it was related to the conversion, so didn't think too much of it.
However, I noted it last week with a short course which was created from start to finish in Storyline 360.
Thanks for the update, JP. We're trying to narrow down the causes of this behavior in Storyline 360 and Storyline 3. Thanks for using the workarounds in the meantime.
Remember when text would overlap in the triggers panel? Well, that issue is now fixed in Update 3.30.19518.0 for Storyline 360! Click here to see what's inside and here for how to update Storyline 360 to see those goodies!
And just to clarify: this isn't fixed in Storyline 3 just yet, but we'll update this discussion as well as the Storyline 3 Version History page as soon as it's ready.
If we can be of any other help, please don't hesitate to let us know!
We just released the newest version of Storyline 3, Update 7 this morning! This release includes a fix for when the text would overlap in the trigger panel.
The next step is to update Storyline 3 by downloading the latest update here.
As always, we are happy to answer any questions you have by posting in this discussion or you can contact our Support Engineers directly.
7 Replies
Hi there, Tracy. We've seen this issue from just a handful of customers, and undocking/redocking the trigger panel helped restore it.
We haven't been able to nail down this bug yet, but I'm going to add your details to our report. We'll update you with any new information in this discussion!
Thank you Crystal! I opened the same file and it did not garble. The developer who brought it to my attention closed his .story file and reopened it - and the issue went away. Several other developers in our organization said it has happened intermittently to them in other Storyline 3 versions. One of them found a pattern - it seems to only occur on the “Change the state of” triggers . The next time we will use your tip and undock/dock the trigger panel.
Hi Tracy,
Thanks for sharing those details! We've added this discussion to the report our team is investigating and we'll keep you posted here.
Also, since you mentioned sharing files, I wanted to check that you're all working on those .story files from a local drive (vs. sharing them on a network/shared drive). The network/shared drive is one of the items known to cause odd behavior ultimately leading to corruption, so following these best practices should help prevent other odd behavior.
I had this issue a couple of months ago with a project converted from Storyline 2 to 3. I submitted a support ticket, but was told it was not reproducible. I figured it was related to the conversion, so didn't think too much of it.
However, I noted it last week with a short course which was created from start to finish in Storyline 360.
I'm working from a local C: drive.
I will keep the workaround in mind.
So FYI, it's not going away. Thanks, JP
Thanks for the update, JP. We're trying to narrow down the causes of this behavior in Storyline 360 and Storyline 3. Thanks for using the workarounds in the meantime.
We'll update you here with any new information!
Hello, everyone!
Remember when text would overlap in the triggers panel? Well, that issue is now fixed in Update 3.30.19518.0 for Storyline 360! Click here to see what's inside and here for how to update Storyline 360 to see those goodies!
And just to clarify: this isn't fixed in Storyline 3 just yet, but we'll update this discussion as well as the Storyline 3 Version History page as soon as it's ready.
If we can be of any other help, please don't hesitate to let us know!
Hey All!
An additional update to share!
We just released the newest version of Storyline 3, Update 7 this morning! This release includes a fix for when the text would overlap in the trigger panel.
The next step is to update Storyline 3 by downloading the latest update here.
As always, we are happy to answer any questions you have by posting in this discussion or you can contact our Support Engineers directly.
This discussion is closed. You can start a new discussion or contact Articulate Support.