64-Bit Storyline 360

I know EXACTLY that same feeling of being scared of losing work due to these weird errors. It's genuinely frightening because the impact on deadlines can be heartstopping. Time wasted, edits to be reapplied, possible file corruption - it's genuinely concerning how often these little heart attack moments occur with this programme. 

From the screen going white with a giant red X through it; the thumbnails being completely blank occasionally; the weird glitch when a master slide is deleted but it doesn't update on the screen; the innumerable copies of files that sudden;y appear in the folder due to some hiccup with autosave that eventually yields to Eric's issue above; to the "We are sorry" modal that pops up whenever the format tool is used - all contribute to a never decreasing nervousness that this app is unstable and could crash at any minute.

And never, ever, update until a few weeks later in case something new gets broken.

Come on, folks. Let's halt with the 'features' and just build this baby to be super solid, utterly reliable and a joy to use. Because this ain't it. 

It's a heart-attack and a very pissed-off client away from being the death of me, sometimes.

Hi Everyone,

Thanks for the continued feedback on your experiences with Storyline. Our goal is to empower you to confidently build courses without the fear of errors appearing as you work. 

We’ve kept a focus on improving memory performance, fixing errors when we spot them, and sharing best practices that help avoid erratic behavior. 

We recognize the desire for a 64-bit version and will continue to advocate on your behalf as we evaluate this feature.

In the meantime, I encourage you to connect with our support team as you begin to experience low memory or performance issues. Often, they are resolved with suggestions from our team.  We want to help get you moving forward with your projects as quickly as possible.

Hi Becca,

I'm on version 12: 3.12.24693.0 .  Still receiving the error intermittently.  I did a free install and still getting the issue.  I uploaded the log files to the support team.

Eric

Hi Diarmaid, great response and conveyance of the feelings I've had myself lately.  You mentioned the issue I'm having may be due to autosave.  Do you recommend disabling autosave?

NOOOOOOOOOOOOOOOOOooooooooooooooo………..

That is not what I would suggest at all!!!!

In fact, it’s knowing that Autosave IS working that despite all the frustrations and panic, I kind of know that the most I will lose is 10 minutes of work. Unless it’s a catastrophic glitch that has occurred in the past (Storyline 1 & 2 were "hilariously" shonky).

No. Absolutely keep Autosave on.

I only mentioned it because I would receive the error message you get, and think “oh, that’s weird", and I would notice that in my folder there’d be 5-10 extra copies in there already and my only conclusion is that Storyline glitched at some point, and started saving individual copies instead of autosaves. It’s only a theory.

Do not take any advice from me. I don’t trust my own advice.

Hi Diarmaid

Thanks for the clarification.  I will not be removing that functionality.

I can't even make a minor change now and save.  :(

Hello Eric,

You originally mentioned that you uploaded the log files to the support team. If you have the case number, I'd be happy to take a look.

If you do not have an email confirmation with the support case number and you sent the error message, this does not auto-create a support case. You can reach our team directly here.

Are they are any benchmarks out there to show how articulate performs at different processor speeds? Renders projects with multiple cores?

I know that articulate is only 64-bit and can only access 4GB of RAM, but until that happens, what is the optimum hardware for performance?

Hi Ren,

With the greatest of respect, this isn't a desire for 64-bit, it's an essential need. Users have been asking for this for a very long time as more of us hit that ceiling of performance. The time for advocation and evaluation are long passed, in my very humble opinion, and it is now the time for action.

Many of the solutions suggested to "work around" the limitations of the application either do not resolve the situation or cause the author to carry out tasks that further delay or hinder the development flow.

This thread started 4 years ago. We hear the same excuses today as we did then. Many of us moved to the Articulate 360 program in the hope that it would support further improvements and allow us access to rapid deployment of fixes such as the one required here. And yet, we often get new features that are welcome but seem to add to the burden of running a 32-bit app in a 64-bit environment.

FWIW, I am running Storyline 360 on an Intel Xeon 3.2GHz Quad core, 8MB Cache system with 32GB of 2400MHz DDR RAM, an NVIDIA Quadra P2000 5GB graphics card and SSD storage drives for OS and data.

I get the same level of Storyline performance as I do on my i5 based laptop.

Until Storyline is dragged into the present, it will continue to perform poorly in whatever present day environment you run it in, regardless of system spec :-(

Thanks for the reply! Too sad. Time is money so would be at the top of my feature list. Specially for those with scene-heavy programs.

Hi all. I'm going to be upfront and say I don't know a great deal about the ins-and-outs of computer tech. However I have been trying to diagnose why I've been having lots of memory related crashes (being told there is insufficient memory when I try to save on a daily basis) since my workplace provided us with new laptops.

Am I understanding this thread correctly - that Storyline 360 isn't really designed to run on 64 bit machines, and this could be a possible cause of my issues?

Our new laptops are 64 bit and I'm currently trying to find out if our old laptops were 32 or 64 bit.

Basically, a 32bit operating system can only address up to 4GB of system RAM, sometimes less if there is reserved address space. Currently, Storyline is a 32bit application and runs on more modern 64bit operating systems in a 32bit emulation mode. This process is not visible to the end user and the application performs as you would expect, but because of the limit of the 32bit architecture, the application can't address the increasing amount of RAM required.

Like you, I ordered a new desktop (Xeon 3.2GHz quad core processors, 32GB RAM, 5GB GPU, SSD) specifically to increase performance across all my authoring tools. So I was beyond disappointed when Storyline performed no better on it. After a bit of investigation, it turns out the issue was the application being 32bit.

Many applications that you run today may still be 32bit but applications like Storyline, by their very nature, will consume large amounts of RAM and even if you have 32GB, Storyline is only able to access up to 4GB of it. This means that when dealing with resource-hungry material such as video and audio, things get... a little slow :-(

As you can tell from the age of this thread, this has been an ongoing issue for some time...

I hope that helps?

I would think at least a faster processor would help somewhat. Only got 1.6ghz 4 core here.
Would I be correct about that?

Matthew McCrorey
Agiliti | Sr. Learning and Development Specialist
Direct: 952-826-7831
www.agilitihealth.com

This helped so much, I understand the issue now! Thank you for explaining it so clearly. My computer has 16GB of RAM and plenty of free storage space on it's C drive so I was baffled by these continual memory errors. The issues do typically present when I am working on large files containing lots of audio and video, even though I was able to deal with these files regularly on my previous laptop. Gosh, this is quite disheartening (basically every program I create now has lots of audio voiceover and video files), but at least I understand what is probably happening now.

Processor speed does help, but extra RAM and a fast drive (SSD) would have even more of an impact on speed.

You're very welcome! It is indeed a real drag and we can but wait and see if the "powers that be" at Articulate hear our call ;-)

For sure. Continually disappointed with 32-bit storyline. Large projects and even small would really benefit from the speed and efficiency 64-bit version that could get a boost from ram and multi-core processors.

Matthew McCrorey
Agiliti | Sr. Learning and Development Specialist
Direct: 952-826-7831
www.agilitihealth.com

Same issue here - lots of audio and video and Storyline crashes or can't save large files.

Checking back in to see if the 64-bit version has made it onto the official 'Articulate' road map yet? 

All I can do is . . . 😂
I feel like Storyline has become industry standard . . . profit over product. No updates on this for years. Event though effects the productivity and thus profits of every customer!

Yup. I'm nearing the conclusion of a large project - even with constant saving, I estimate I spend at least 30 minutes every day recreating work after a crash. Getting seriously cheesed off.

I think windows 12 will drop before we get the support you'd expect from $1000+ Per user software. 

Captivate's running 64 bit - Might be time for that change..

I must say I've never considered Captivate before as I was so satisfied with Articulate, but I may have to scope it out now. As it is now I am currently paying more than 1000 euro a year for software which routinely crashes and which the developers aren't planning to fix