Captivate 2017"not responding" (cursor changes to spinner) every few keystrokes

Forum|Forum|8 years ago
April 29, 2018
3 replies
677 views

I can't stand it, I REALLY don't have time for this, Every few keystrokes, I have to wait 3-10 seconds for Captivate to do the last requested action applied to an object. Often the screen greys out and tells me Captivate is "unresponsive". Occasionally it just dumps altogether instantly and there is no recovering the work - main and .bak files are corrupt. The action could be move, resize, change color - anything at all. This is the Captivate 2017 with the latest update applied, running in admin mode in Windows 10, all files on the C drive. This computer is a laptop with an i7 6700, GTX 1070 graphics, 512 Gb SSD (C:/), 2TB 5400 rpm (D:/), 64 Gb RAM - what more does this program need? How do I stop this? It's acting like it's accessing data, possibly from a URL, before it completes the action. Is it checking my license status? I've read and tried everything Rod Ward and Lillbiri have to say about this issue. I have Captivate 9 (latest patches) on another similar machine and it NEVER does this. Anyone have any ideas? Should we all just buy Storyline?

This topic has been closed for replies.

RevRichard

Participating Frequently

I too have been having this problem (Captivate 2017 not responding) but mainly when I either, 1) select a different slide to work with in my filmstrip, or, 2) when I do a "Save". In fact when I would do a Save, it would take almost 50 seconds for the save to complete. During the "Save" I would get the Not Responding message.

What I finally figured out was this: For some odd reason, Captivate was trying to access a thumb drive (E:/) I had plugged into one of my USB ports. I have no idea why. According to the Captivate Preferences I had set up, all of my Project and Publish files were being saved to my PC Drive (C;/), and not to my thumb drive.

After I unplugged the thumb drive, Captivate began behaving normally again. I have no idea why Captivate was trying to access that thumb drive, but for some reason that's what was happening. When I removed the thumb drive, Captivate was happy!

RodWard

Community Expert

Something is definitely NOT right here. This is not normal for Captivate 2017. Is there anything unusual about where you have this app installed on the system? Is it the 64bit version of Cp and is it installed in the normal Program Files location for 64bit apps?

If you look in Windows Task Manager, how much RAM or Chip percentage is the Captivate process using?

David Burnham HBA

Inspiring

I continue to have similar problems. Rod, you and Lieve and I discussed this same issue back in January of 2016 for Captivate 9 under the heading Captivate 9 is Frequently Not Responding.

Lilybiri

Legend

David, I vaguely remember that discussion. First release of 9 definitely had more problems like that. Up till now CP2017 is behaving better for me, even on my less powerful Surface Pro. Running as Admininstrator (Win10), regularly cleaning the Cache, seems to help. But the OP here definitely has big issues, that is why I begged the Staff to help here.

Lilybiri

Legend

You installed the recent patch to 10.0.1.285? Did you clear the preferences before installing that patch? Do you clear the cache regularly? Something must indeed be wrong, I'm running same version on systems that are much less performant than yours.

I will try to have someone of the staff contact you to help you out.

R

rcr60Author

Participant

Update - There is one spec of this laptop Captivate 2017 is running I didn't mention, and it might be relevant to the problem. It has a 17.3" 4K display, and while this is nice, having all the Captivate panels separated out just doesn't fit on the screen, so I was deactivating the laptop screen and working off of a 40" 4K monitor. It is in this configuration that the program had been the most erratic, and I say that because all of this week I've been working just on the laptop screen with the default Captivate workspace (not conducive to my workflow, but I wanted to see what would happen) - and so far this week I've not experienced any major incidents. That said, I'm still getting "not responding" quite often, but the program hasn't crashed working like this (yet). So, certain graphics configurations possibly complicit?

RodWard

Community Expert

Do you happen to have the Captivate Branching View open when you are working? If so, I recommend you turn that OFF unless you have a specific need for it. I found that this particular screen seemed to bog Captivate down quite a bit.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded