Forum Discussion
Storyline 360 crashes when try to copy/paste
Every time I ctrl+d or copy and paste, Storyline 360 crashes. I've uninstalled/resinstalled to no effect.
Any ideas? Or does Storyline just not support this?
Thanks, Steve.
73 Replies
- RonazielLopezCommunity Member
Hi Steve,
Can you specify what are you trying to copy and paste to the Storyline?
If you are trying to copy a scene/slide from one SL project to another, it is recommended to use the import function instead. You can check this link on how you can do it.
Hi Steve,
Storyline allows for copying/pasting from other programs or applications - but the crashing is something we'd obviously want to fix!
I'd want to start by confirming that your .story files and any other items you're copying are saved locally. If Storyline continues to crash - could you go through the repair steps here?
If it's still causing you trouble - our Support engineers can help you pull error/crash logs and figure out what's happening!
- JanWatkinsCommunity Member
I see that it is 3 years later and it is still not possible to copy and paste notes from one slide to another without Storyline crashing. I've had to pull up Microsoft Word to copy and paste and it works fine. However, it would be nice to not have to do this. My template changes in areas where it isn't possible to just import the corrected slide. Has any progress been made in this area in the past three years.
- SteveJonesCommunity Member
It happens when I try to copy/paste an object on a slide with multiple states. Thought that would be easier than recreating objects and states multiple times.
It is saved locally. Did the uninstall/reinstall steps.
Hi Steve,
You should be able to do that - could you share a copy of your .story file (even just the one slide where you were trying to copy items)? In the meantime could you also try duplicating the object - CTRL +D will duplicate it and capture all the states too.
- SteveJonesCommunity Member
ctrl + d has the same result.
I'll upload the story file.
Interestingly, when I created a file with just the offending slide, I did not always get an error when copying/pasting or using ctrl+d
Hi Steve! I see your case, and it looks like Miker is doing some testing with your file. I'll follow along too.
Hi again, Steve. Checking in, it sounds like Miker found a couple of corrupted text boxes in your file, and you were able to recreate them.
If you have corrupted elements in your file, usually it won't preview properly. You might notice that you can preview some scenes or slides, and not others. I usually start at the top and drill my way down, previewing project, then scenes, then slides. And if I find a slide I can't preview, I remove elements until it does preview to isolate the culprit. It can feel tedious, but it typically works.
Here are some tips for reducing the risk of file corruption. Let us know if you need anything else!
- TiannaTagamiCommunity Member
This is happening to me. I tried uninstalling and reinstalling. I'm just trying to copy-past a shape on the same slide.
Hi Tianna,
Based on the conversation above, seems that the issue was due to corrupted items in the project. Are you having trouble copy/pasting anything else in the file or is this the only item? If this is the only one, you may consider re-building this particular item first.
If you need us to take a look at anything, you can share here.
- JoyceMaurin-e58Community Member
Hello,
I'm facing a similar issue.
I tried to follow your steps, but it didn't work. Working locally and everything.
First of all, my .story is quite heavy (48'000 ko) and using a lot of audio files, so I thought it may be a reason...
I have 3 kind of issues:
- Storyline 360 crashes when I try to copy-paste group objects on the same slide
- Storyline 360 crashes when I try to copy-paste slide from another .story (only the window where I try to paste)
- Some objects from content library does not appear when I copy-paste them from one slide to another or from a .story to another
Best regards,
Welcome, Joyce! Thanks for starting with the repair steps–so sorry you're still experiencing such wonky behavior.
I'm glad you reached out to us, as we're here to help! I've created a case on your behalf for our Support Engineers, so we can help get you up and running smoothly as quickly as possible. Someone from the team will be in touch, and I'll also follow along!