Forum Discussion
64-Bit Storyline 360
Is there a way to access a 64-bit version of Storyline 360? I noticed what I have installed through the 360 suite is only 32-bit and I'm finding that I may be reaching a ceiling with performance whi...
Hi Everyone!
Great news! I'm happy to share that we just released Storyline 360 (version 3.82.31354.0), which includes a new 64-bit version of Storyline 360! Harness the processing power in modern computers with 64-bit Storyline 360. Large, media-rich courses benefit from increased stability and faster performance!
To use 64-bit Storyline 360, please update your Articulate 360 desktop app, then click the Install button next to the Storyline 360 app with the 64-bit and beta labels. The Install button will change to an Open button when the installation is complete.
This was highly requested, so we hope it serves you in your course creation! If you run into any snags, don't hesitate to contact our team in a support case.
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.comProcessor speed does help, but extra RAM and a fast drive (SSD) would have even more of an impact on speed.
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
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.
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 ;-)
Same issue here - lots of audio and video and Storyline crashes or can't save large files.
I wanted to share an update on this issue, which I had attributed to a new work laptop that was 64 bit. Articulate and the story file in question I was encountering issues with had worked fine on my previous work issued laptop
After working extensively with me through a support ticket, the Articulate Service Desk identified the culprit as a custom font that wasn't supported by my computer. I'm not even sure where the font came from - I imagine at some stage I downloaded a template from the community and it was in it. When I opened my story file a warning message would pop up indicating that the font wasn't supported, but I had gotten into the habit of just clicking "ok" and moving on with my work. On my old computer this never presented any issues, so I didn't suspect it as a cause on my new computer. However, on the recommendation of the Articulate service desk I rooted out and replaced all instances of the custom font (using instructions at end of this post) and immediately my performance issues improved.
Over the course of 2 weeks working extensively with this large project I had maybe 2 memory related crashes - not ideal, but a HUGE improvement to the dozens daily I was seeing before I removed the custom font packages.
I don't understand why the fonts caused such an issue, but suffice to say, I was delighted to get to the bottom of it. Many thanks to the Articulate service desk who I had a lot of correspondence with on my issues.
How to replace fonts:
Rob Puricelli
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.
It's really crazy that this is July 2023 and it is STILL having this issue. I wonder what it will take for Articulate to finally DO something.
