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!
53 Replies
I have a fresh install of Storyline on a fresh install of Windows 10 and it's constantly crashing when editing triggers. I have a test project that is only 1 slide, nothing complicated.
Very disappointing.
Hi Jonathan!
I'm sorry for the trouble! I want our Support Engineers to work with you directly to determine what is getting in the way. Our Support Engineers are available 24/7 in a support case. I'd recommend uploading your .story file to their team so they can start by testing your project. You'll hear from them as soon as their testing is complete.
Having the exact same issue when trying to add a condition to a navigation trigger on a sequential menu. Any updates on this problem?
I am also having this issue, along with others on my team, and literally every time we even *touch* the condition box in the trigger wizard it crashes Storyline. It's been a year since this issue was reported, what is the fix?
Hello Jason and Maranda!
If you still see this issue while working in the latest version of Storyline 360 and Windows, we'll need our Support Engineers to step in! You connect with them 24/7 in a support case. After submitting a case, you'll hear from them shortly on next steps!
I did and had 2 techs working on it. The final suggestion (after jumping through every other hoop) was to use the arrow keys when selecting a condition type, rather than using the mouse. The problem was not fixed, but that work-around does work. In the event anyone else is having this issue with no hope in sight, using the arrow keys worked after the following did not.
Miranda, try using your arrow keys to select your condition type in the trigger panel. It worked for me when nothing else would.
I am having this same issue on Windows 10 Enterprise, Version 1909, OS build 18363.1679 and using Storyline 3 Update 12. When I go to edit a trigger via the panel, Storyline force quits... it doesn't bring up AutoRecovery upon relaunch either.
I did follow the steps that Lauren Connelly shared via Cleo.
I had success in creating the new project, importing the old file, and also creating a new scene (then copy/paste over the old scene to the new one). I deleted all the current triggers, then added back triggers I needed- a bit tedious/cumbersome, especially if it's a project with many triggers— a fix would be appreciated!
Submitted a case, thanks.
Hi! This has been an ongoing issue for me. My Storyline shuts down completely when setting up a trigger with an object condition. Jason's suggestion is the only solution I've seen here.
Yep, still an unacceptable issue. We have team license, 14 seats, that is up for renewal in 29 days. Serious thoughts of going in another direction.
Help! I am having this problem! i've been doing some workarounds, hoping that updates would fix it, but not so far. Huge problem, please help.
I do not get this error if I am setting a condition using a variable; it only happens when i try to set a condition with an object -- for example, "if the state of button 1 is selected" -- i can't even select an object; the moment I hit the "objects" tab in the conditions drop-down, it crashes.
My Articulate is usually current -- i made sure it was updated this morning. Windows 10.
Using the arrow keys worked for me! OMG, first time in a year that i have been able to set object conditions... Thank you for sharing!
But a work around is not an excuse to Articulate not fixing a known bug.
I'm having the same issue as the people above. Come on, it has been 2 years since the first report!
n
This is still happening, is there a real fix yet? I can't create any trigger with a condition, which is seriously hindering my designs.
I'm sorry this is plaguing you, Sara.
I've started a case on your behalf to connect you with a support engineer and work with you one-on-one to help troubleshoot.
Be on the lookout for a reply with the next steps soon!
Good afternoon,
This issue started, for me, this morning. I used Jason's suggestion about the arrows and it worked agree that this issue needs to be fixed!
Hum, it appears this has been an on-going problem for over 2 years!? I can't understand why such a simple thing as adding a condition to a trigger would crash Storyline? It looks like my only option is to open a support ticket.
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.
Use the arrow key. Yeah, it would be nice to have that fixed, but it's not that big a deal to push a different button, and it completely solved the problem for me.
Awesome advice Joseph, using the arrow key totally worked! Thank you for the work-around. :-)
Temporary work arounds are OK, but going on a two year work around is unacceptable. And further unacceptable with the forthcoming price increase.
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.
I notice from the conversation above that there is not a lot of helpful information coming back from Articulate on this software problem.
From my own experience and judging by the traffic on this issue across many threads, this has been going on for years with repeated promises that it will be fixed in future upgrades but it is still happening despite the so called solutions and workarounds, none of which have worked for me.
This is not a random thing. It happens every single time I try to create conditions using Object or Window, and it happens the instant I click on either of those two options. It can't be a phantom, it must be a fundamental error in the program. Please fix it.