Trigger-Bug in Storyline
Apr 17, 2020
Pinned Reply
Hello Everyone! ✨
I'm happy to share that we have released a new update for Storyline 360 (Build 3.74.30180.0)
In this update, we have implemented a fix for:
- Storyline 360 crashing when adding conditions to triggers or publishing to Word.
As a first step, I recommend updating Storyline 360 to the latest version. Here's how:
If you have any questions, please let us know in this thread or privately in a support case.
Have a great day!
35 Replies
Hi Aileen,
Thank you for reaching out and letting us know!
The behavior you are describing doesn't sound quite right, so I am going to open a Support Case so we can take a closer look. If you can share your file and the error report with us, that would help out greatly!
Please be on the lookout for an email from Articulate Support!
HI,
I'm also having the same issue since last update. Articulate just crashing on me all the time for no reason.
I'm using the latest build v3.39.21985
Thanks for contacting our support team about this issue as well, Frederick. I can see that you are working directly with Chester.
Hi, would it be possible to get an update on this, this seems to occur for me on the last update and it is anytime i click on the trigger panel to change the trigger object or action via the dropdown shortcut without going into the full trigger window. This becomes very hard to do multiple motion path triggers.
Hi all,
Thanks for your patience as our team investigated the issue where Storyline 360 could behave erratically or crash when using a non-English interface. We released a hotfix today in Update 3.39.22088.0 that should resolve that issue.
If you run into any other trouble, please do let us know! Our Support Team is ready to help.
Hi Ashley, just to inform you that with the latest update, the problem still persists. So i have to go to the old trigger workflow as a workaround.
Hi David!
We'll want our Support Engineers to take a look at the file if you're still seeing this bug in Update 39 for Storyline 360!
Please use this link to connect with our Support Engineers!
Hi Lauren,
I have submitted case: 02271819
Thanks,
David
Hello David,
I also have the same issue. Are there any news from the support team?
Thanks,
Christian
Hi Christian,
I was able to take a look at David's case and we were unable to replicate the issue and a new laptop alleviated the issue for him.
The first step would be understanding the steps to reproduce the issue and I'm curious if the issue happens in any course you are working on or just this particular one?
If you'd prefer to work privately with our support team, then with your permission, please share your project file. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
Hi Leslie,
I've already written with Vevette Chua and she helped me with this problem.
My company is working with an older version of articulate. The update would fix the problem.
In my case I was able to solve the problem by using the English version.
Thank you for your help and the quick response!
Mit freundlichen Grüßen / Kind regards
Christian Henzmann
Personalentwicklung & Training Deutschland/
Personnel Development & Training Germany
www.lyondellbasell.com
[cid:image001.png@01D2F0FA.E4295550]
Basell Polyolefine GmbH, Brühler Str. 60, 50389 Wesseling, Germany, Amtsgericht Köln HRB 45129
Geschäftsführer/Managing Directors: Tassilo Bader, Stephan Reeker, Frank Alt, Peter Smits
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Gianluca Brescia
Information contained in this email is subject to the Disclaimer and Privacy Notice found by clicking on the following link: http://www.lyb.com/en/about-us/disclaimer
Hi Christian,
Thanks for letting us know Vevette was able to help you find a solution!
By the way, it looks like you may have replied by email where your contact information came through. This Peek video will show you how to edit it out if you’d like!
I am consistently seeing this bug. I am completely unable to switch from Variable to Object in the Triggers > Conditions panel without crashing Storyline 360, v3.44.23192.0.
Microsoft Windows 10 Pro, 64-bit, 16 GB RAM.
Hello Joseph!
It sounds like this issue might be specific to the Storyline course. It would be helpful for us to take a look at the affected file. Do you mind uploading the .story file to us by using this secure upload link?
Lauren,
As I have been able to consistently trigger this crash across multiple Storyline 360 files, to opine the issue might be confined to a single Storyline course would be a bit premature.
A single-slide test file which demonstrates the crash has been submitted.
Hi Joseph!
I see that you've submitted a case with our Support Engineers! My teammate, Jose, recommended that you try a simple repair for Storyline 360.
If that didn't do the trick, I encourage you to continue communicating in your support case so we can find the fix!
Lauren,
I performed the steps outlined in the "simple repair" (disable UAC, uninstall SL360, reboot, reinstall SL360), and a check shows .NET Framework 4.8 is both installed and enabled.
I just created a brand new, simple, file from scratch, and the exact same behavior was exhibited. Storyline crashes when I attempt to switch from (Variable) to (Object) in the Triggers > Conditions panel.
Thanks for the update, Joseph. I've shared this information with Jose in your support case and you should be hearing back from them soon.
Has there been any progress on this issue?
Hi Joseph,
Thanks for following up. I took a look at your support case and do not see where you replied to Jose, so I forwarded the latest reply to you again.
Please let me know if you do not receive it.
Leslie,
To date, I have not received anything from you or Jose. I created and submitted an example file on October 29, but I do not see a way that I can track my submitted tickets.
Thanks for letting me know, Joseph.
Can you check your junk/spam folder to see if there are replies from support@articulate.com? Jose emailed you originally on 10/15 and 10/21 and I emailed you 12/3.
Absolutely zilch. Are you certain you sent it to the correct email address?
Ah, it looks like there may have been an additional letter when you submitted the case. I've forwarded a reply along. We should be good to go now!
Was this ever resolved, I just started using 360 and every time I try to create a condition it is crashing the application?