64-Bit Storyline 360

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

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.

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 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.

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 generally have given up hope long time ago, as any serious matters ... doesn't matter here and things that were implemented in another softwares years ago aren't even considered here. I guess we will never see 64-bit app as it will require to rewrite the whole application - too much money to loose ;) only hope is if windows drop all the 32-bit apps support.

However, reading all your guys problem I think you all takes Storyline a little too seriously or doing something really wrong. I sometimes get RedCross on layers or images, but for the long time that doesn't crash the app at all. I just need to restart and everything works good again.

I've opened now one of my recent big project - 160 slides, with almost 200 voiceovers and 1000 of high-quality images on every screen, (no video tho). Storyline takes only 550MB of RAM for this. Plenty left to utilize.

And to be honest, if you are doing big, complicated projects, like over 200 screens or more, that's not the proper way on doing courses this days. Split that into separate modules and your problems will be gone. Put the videos in the last, compress them beforehand. Don't use 5000x5000 pixels graphics when you produce 720p training. Don't use many pngs on one screen, go for jpg whenever you can. Maintain your resources! If you are indeed in need to make huuuuuge courses, also work on separate files and in the end import all this separate files into one and then publish. You know the project beforehand, so plan ahead of doing it. All this boosts up Storyline performance. I once was also angry about the time storyline took to process things, but gave it 2 day proper research, pinned down what was the problem and now I work quite ok with it.

However, with every update comes some new issues destroying overall workflow which is often left to be. Still I guess no other authoring tool have so many... versability like Storyline, where I easly can do many, many additional things that were never meant to be by the devs I guess. Gonna stick with the guy, let's call it though love and hope for more performance updates. I suppose the GPU acceleration helped a little with overall performance, so there's a light in the tunnel.

As someone mentioned, HR reps will be pleased because they can do their interactive powerpoint, but let's be clear - they are the main target for this software. Not us, the artists :D

This is an issue we see regularly. The cause of the issue is a system issue.
Windows can only allocate a maximum of 2GB memory to 32bit applications. This is a combination of all of the 32bit applications you have open. We quite often see that clients are using Microsoft Office applications and their installed office programme is the 32bit version.

Ideally they would need their IT department to give them the 64bit version so that this free's up the memory to be used by Storyline 360.

To see what you are using you can open up your task manager (Ctrl+Shift+Esc) and any open 32bit applications will have (32bit) after the name of the application.

The interim option is to get the user to close down the other applications so that Storyline can have more use of the memory so that the crashes stop and they don't get the low memory error showing up.

The only other thing we can do as mentioned by Articulate staff is to put in a feature request to the Articulate Development team and the more it is mentioned the more hope we have of them looking in to a 64bit version of Storyline 360
http://www.articulate.com/support/contact/submit.php?form=feature

I hope this helps.

A >5 year thread, and really nothing from Articulate on solving this issue, that's sad and shows a huge lack of customer support. Sitting on laurels and expecting those who use it to put up with it will not last much longer. 

64 bit apps have been around for 15 years, long before Articulate even started working on the Storyline360 application. I find it rather odd and it shows a lack of vision that there is not a 64bit version out or even in the pipeline at this time (or a Macintosh version of this software.) It seems that actual development has stopped, and only little shiny buttons are being added to keep the masses using this, while breaking things that used to work. 

I am having to restart the app after it crashes several times a day at this point, and am using actions that are built into the program (no javascript or external coding). I do have a lot of variable/text entry fields that are used for assessment in real time, and other interactions on the same layers; this however should not be an issue. I have over 6GB of ram free during use of the app. And as stated above over 5 years ago, have to wait for several seconds when updating fields or images to continue working. I have submitted so many "what were you doing when the program crashed" messages, it's nauseating. 

instead of adding in more bells and whistles for the upcoming major release, maybe focus on a stable 64bit, non-memory capped application that takes full use of the CPU caching and can access the GPU for rendering as well. For the money this costs, and the huge user base you have, it should be expected. 

Here's a selection of some... interesting NEW error messages that I have encountered in the last 48 hours alone of working with Storyline.

I have never seen these before, so... progress?

Whenever I get the generic "Somethings gone wrong" modal, my workaround is to close it and keep working. It saves time. I only reboot when I get giant X's on the slide thumbnails.

This is also on top of the MANY little glitches that occur within a slide, such as the new shuffle states 'feature' just randomly throwing my states into sequence.

I love all this extra hassle and pressure and working with highly unstable software.

Love it.