64-Bit Storyline 360

Hi Travis,

Thanks for reaching out and sharing your feedback.

A 64-bit version of Storyline 360 is still on our roadmap, but our team has been working on performance improvements to the memory and speed with the 32-bit version. We’ve also enhanced the UI since accessibility has been our key focus. 

Since you're running into issues doing basic actions, do you know if this is file specific, or is this happening across the board? You're welcome to connect with a support engineer anytime to share your file so we can take a more in-depth look and provide some help!

Thank you for that context, Travis.

We'll definitely take note of this and share it with the right team. As always, we welcome folks to start a conversation with our Support Engineers for a closer look!

Any word on the 64-bit version of Storyline 3?  This running out of memory issue is getting worse and worse by the day.

Hi Eric, and welcome to E-Learning Heroes. 😊

This feature has not made it on our roadmap yet. This conversation is attached so that we can share any updates with you here in the future.

Articulate 360 Feature Roadmap

In the meantime, I've opened a support case on your behalf so that you can work directly with one of our support engineers on optimizing your software.

I find it staggering that after this issue was raised over four years ago, a 64bit version of Storyline is still NOT on the roadmap, and yet new features, which are always welcome but will increase the demands on system resources are. 360 degree images? Very cool but almost certainly going to eat up RAM if done properly and if Storyline can't address above 2GB, this feature is going to be pointless.

I've gone back and forth with tech support, as have many others, and we are still no nearer to having a version of this software that is designed for the computers and operating systems of today (or even years ago). Colleagues in my team are reporting numerous issues with painfully slow performance and crashes, and the number of users reporting here is also concerning. Even when a user demonstrates clearly that a lack of ability to address the full system resource is causing an issue, we get told by Articulate that they can't replicate that issue and we should get in touch with a support rep with the general solution being to create a new project file and copy content into it.

I'm sorry, but I don't have the time to nanny an application that can't keep up with basic workflows. When the application stutters and wobbles at the simplest tasks, that then destroys any form of accuracy when moving, resizing or placing objects, it drives you to resort to dumbing down the experience you are looking to create for the end user, simply to ensure you can get projects finished on time for end users. It is stifling creativity rather than setting it free.

Speaking solely from my team's experience, we are increasingly disillusioned with the Storyline application to the point where we have begun investigating the painful solution of transitioning to other tools, simply because they perform as expected. This would involve huge costs and ramp up time, but we're not able to see any other alternative.

I've even reached out to Tom and Articulate's CTO, neither of whom have even had the decency to respond, even if it were to fob me off with another excuse.

I am sorry if the tone of my post here is overtly negative, but that mirrors my experience with Storyline over the last few years.

I implore your development team to reconsider the roadmap and deliver an ROI to us, the end users.

I tried the steps and they do not work.  The only thing that appears to work is if I save a different file name.  

I'm still getting the error "The project file could not be saved.  Your system appears to be low on memory.  Please close other programs and try again."  I've tried everything, usually saving as a new file name helps, but this time nothing is working.  I'm scared of losing all my work.  I don't know what to do.  All the mentioned troubleshooting steps are not working for me.

Has a 64-bit program made it onto the "road map" yet? 

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.