Forum Discussion
Storyline crashes when trigger conditions added
Good afternoon team. Regardless of content, Storyline reliably crashes when I attempt to add conditions to a trigger.
Clicking the dropdown in conditions will show the options of variables, object...
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!
As I replied in another thread over a year ago, Articulate Tech Support's first suggested "solution," was to disable anti-virus and change my user profile to local admin. As I elaborated on in this post, the era of everyone being a local admin on their computers is over. Internal IT departments find having fewer users (including those within IT) having administrative privileges means less vectors for cyber-attacks. Suggesting either of these as a possible solution demonstrates a profound ignorance of today's enterprise environments.
Articulate Tech Support's second suggested "solution" was to use the keyboard arrow keys to get to the "Object" option. While that does, for the most part, work, it is entirely kludgy and ignores the underlying issues. I pay for software which works, not software which requires jumping through multiple hoops to get it to sorta-work. Software in the latter column is called "beta," aka "not ready for public sale." As an alpha and beta tester for several of the big names before Articulate was around, I know beta when I see it.
Awesome advice Joseph, using the arrow key totally worked! Thank you for the work-around. :-)
Joe, wasn't in great back in the days of your avatar having the insider knowledge of Jamil on the AWARE ListServ!
Yeah, having direct access to Macromedia's engineering team (including Mr. Brew himself) was awesome. They listened, actually responded, and fixed issues, not sit on them for years while offering empty platitudes.
