I have Articulate 360 and not a big fan of Storyline's complexity. I have familiarity with Engage - however the fact that it must be used in your computer's hard drive, adds complexity to a nice, simple tool. I have saved an Engage interaction in my hard drive. However, in order to add any Content 360 files (which actually doesn't work for me. It has frozen the application and I've had to use Task Manager to close the app). I think any photos you wish to add, also have to come from a hard drive, which doesn't make sense if you're working for a company that uses OneDrive. Having to use hard drive, added extra steps and extra time. It's too bad.
Thanks for sharing your experience with Engage 360! I’m happy to work with you to figure out why the program is crashing while adding items from the content library! I have a few follow-up questions regarding your experience so I can understand what you are experiencing a little better.
Which version of Engage are you using? I am using Engage version 4.31.29403.0.
You mention that Engage is crashing when adding any Content 360 files. Is it happening with photos, illustrations, videos, and characters?
Is Engage crashing when creating any type of interaction or a specific one?
I’ve attached an interaction that I created in Engage 360. The video in the interaction was added from the content library. Do you mind importing it into Engage 360 on your end to see if it works properly?
Also, I understand that moving files from OneDrive to your hard drive is an inconvenience and adds time and steps to your project, but it really is a crucial step to avoid file corruption and other erratic behavior.
Thanks for reaching out and I look forward to your response!
Hello and thanks for the reply. I'm not sure what version I have (or where to locate the number) - but I just started in this role and got a new Articulate license, so I'd assume it's the latest version.
When I opened your Engage, I was able to play the video and see the images. I'm not sure why my Content Library it freezes. is it because the Content Library is NOT in a hard drive?
I then have to use task manager to close the program. I'd appreciate your help - if you have any ideas. It's probably that I'm not
Thanks for the additional information. I understand that your company uses OneDrive to manage your files, but working directly on a network drive has been known to cause file related issues due to the introduction of latency and file syncing.
To address the behavior, try saving your Engage 360 interaction somewhere on your C: drive that does not get synced to a network drive. If the issue persists, you can:
3 Replies
Hi Kathleen,
Thanks for sharing your experience with Engage 360! I’m happy to work with you to figure out why the program is crashing while adding items from the content library! I have a few follow-up questions regarding your experience so I can understand what you are experiencing a little better.
I’ve attached an interaction that I created in Engage 360. The video in the interaction was added from the content library. Do you mind importing it into Engage 360 on your end to see if it works properly?
Also, I understand that moving files from OneDrive to your hard drive is an inconvenience and adds time and steps to your project, but it really is a crucial step to avoid file corruption and other erratic behavior.
Thanks for reaching out and I look forward to your response!
Hello and thanks for the reply. I'm not sure what version I have (or where to locate the number) - but I just started in this role and got a new Articulate license, so I'd assume it's the latest version.
When I opened your Engage, I was able to play the video and see the images. I'm not sure why my Content Library it freezes. is it because the Content Library is NOT in a hard drive?
I then have to use task manager to close the program. I'd appreciate your help - if you have any ideas. It's probably that I'm not
Hi Kathleen,
Thanks for the additional information. I understand that your company uses OneDrive to manage your files, but working directly on a network drive has been known to cause file related issues due to the introduction of latency and file syncing.
To address the behavior, try saving your Engage 360 interaction somewhere on your C: drive that does not get synced to a network drive. If the issue persists, you can:
If the issue persists, open a case with our support team here so we can provide additional assistance.