This is update 9. This issue is so persistent that I am at a standstill with proceeding with a fairly large project with a looming deadline. Has anyone else experienced a copy/paste lockup issue like this? If you have how have you solved it? I'm downloading 10 even though it isn't listed as one of the bug fixes. I'll post back when I test it.
This is an editing job. Some lengthy references have to be swapped out. I did find a work-around. At least it's working for now. It's strange but it works.
Select text in SL and hit a letter key to remove the paragraph and change it to a letter.
In Word select and copy the text.
In SL Ctrl+A, Ctrl+V.
I can then do the rest of my edits and it hasn't locked up yet.
I went through the steps as you described here and I didn't have any difficulties with Storyline or Word crashing. You'll want to confirm you're working on local project files as well and if Storyline keeps crashing I'd advise pulling the error logs as detailed here so that you can upload to our Support Engineers to investigate further.
Thanks Ashley. I always work local. There was never any issue with Word crashing, just SL locking up. I allow SL to send reports when the program crashes but I'm not sure those were generated since I had to use the task manager to force close SL.
Good to know Michael - and the reports that you send from that set up do go to our QA team but they don't generate a new case for you so using the steps I shared above will connect you with our Engineers to be able to take a look at your system log.
Hi Michael! I would recommend utilizing the instructions that Ashley shared above to reach out to our support team. When you send the error report, this is not associated with user for us to follow up with, but is moreso for the overall status of the software and to be alerted to any bigger performance issues. By reaching out to our support team directly, you can get the assistance needed.
6 Replies
Okay. I downloaded update 10 and the problem continues. Here's a step-by-step:
This is an editing job. Some lengthy references have to be swapped out. I did find a work-around. At least it's working for now. It's strange but it works.
Hi Michael,
I went through the steps as you described here and I didn't have any difficulties with Storyline or Word crashing. You'll want to confirm you're working on local project files as well and if Storyline keeps crashing I'd advise pulling the error logs as detailed here so that you can upload to our Support Engineers to investigate further.
Thanks Ashley. I always work local. There was never any issue with Word crashing, just SL locking up. I allow SL to send reports when the program crashes but I'm not sure those were generated since I had to use the task manager to force close SL.
Good to know Michael - and the reports that you send from that set up do go to our QA team but they don't generate a new case for you so using the steps I shared above will connect you with our Engineers to be able to take a look at your system log.
Hi Michael! I would recommend utilizing the instructions that Ashley shared above to reach out to our support team. When you send the error report, this is not associated with user for us to follow up with, but is moreso for the overall status of the software and to be alerted to any bigger performance issues. By reaching out to our support team directly, you can get the assistance needed.
This discussion is closed. You can start a new discussion or contact Articulate Support.