64bit and Multithread Workloads for Storyline
I just want to share something I have been sitting on for quite some time and that is my thoughts on the frankly old architexture that Storyline 360 is built on. From a back end point of view it only seams to be a marginal leap over Storyline 2 and none of the real performance issues that came in storyline 2 have been improved on in 360 / 3. Now in truth this may not be the case, it may have been re built from the ground up as some responses from Articulate have suggested but from a users perspective this seems to be simply untrue. There are a few outstanding questions asked by people on this forum dating back to 2016 regarding 64bit Support and with that Multithread workload support. Every response to these has been 'submit a feature request' of which those I have spoken too, all have submitted this request and it has fallen on deaf ears. Can we please have an actual answer on whether or not this support is coming on the development roadmap?
To give a bit of reasoning stoyline as a 32bit app is currently limited to single thread (1 cpu core) support and 4gb of RAM. If your system has a multi core cpu (which in almost every case it will have) that is system hoursepower that is untapped and similarly if you have over 4GB of ram, and the system average according to hardware surveys is 8GB for the average user these days. It is possible for a 32bit app to use multiple threads but that does not seam to be the case here monitoring the cpu loads when using storyline.
Storyline 360 is a new product, that is already old out of the box. As developers we are using products like Blender and the Adobe Creative suite along side this product to develop our courses, all of which have been native 64 bit only apps for almost a decade and take full advantage of a system, and for those who do video editting and 3D design to create content for their courses, they will have extremely powerful computers that are being completely underutilised by Storyline. A lot of the performance issues we see on a day to day basis are due to running out of memory or being bogged down by a single cpu core due to these limitations.
This is not a feature request this is an architecture request, this is a plea to just tell us is this on the roadmap, because I and many other developers are rapidly starting to loose patience in this products inability to keep up with the pace of the people who use it in this industry.