Error Report Message from Storyline

Hi Donna

Can you please confirm that you're following some basic rules to prevent strange behavior:

• Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
• You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
• Avoid using special characters, accents or symbols in your file names.

Finally, if your Storyline software is not working properly, a simple repair may fix the problem. If not, please feel free to submit a ticket to our support team for additional help.

Thanks, Donna!

Hi Peter,

Thanks for getting back to me.  I can confirm all that you've asked:

• I'm working on my C:drive
• Directory path to project files and published output is less than 260 characters
• I'm not using any special characters (I removed all hyphens from file names a couple of days ago)

I haven't experienced this error today.  As a safeguard, I created a duplicate file and am working from that.  I'll submit a ticket if the error message returns.

With regard to the screen shot I provided, have you seen that before?

Thanks again.

Donna

Thanks for checking those items and for the screenshot, Donna. 

I honestly haven't seen that "red x of doom" since the early days of Storyline, and back then it had do with color depth. 

Can you confirm that you're running our latest update - Update 3? 

If you run into any more trouble, please don't hesitate to give our support team a shout. 

Thanks, Donna! Hope you have a great weekend

I am getting the "red X of doom" while moving around photos and creating blank shapes.  Every few minutes the big X hits.  The slide is a main menu, so there are a lot of triggers on the slide.  Also, it is a very large file 132,024KB.  Frequent saving is very time consuming because it takes so long for the saving process. 

I updated my storyline program within the past month, so the fixes identified in previous replies (more than a year ago) should be in the version I have.

Your thoughts and suggestions?

thanks,

Annette

Hi Annette!

This is not something that normally occurs. There was a thread here back in February.

Could you try importing your Storyline Project into a new file to see if this helps to clear up any persistent corruption?  If the problem persists, would you be able to share a copy of the problematic .story project file with us so that we can take a closer look?