Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Terrible UAT on current version of Captivate 9

Community Beginner ,
Feb 23, 2016 Feb 23, 2016

Hello,

I am using version 9.0.0.223.  I have run into several problems that I believe should never have been able to make it into your production release.

When I place a button on screen and then drag it to the location I desire it to be located, the states for the button remain in original insertion point.  I know that I have to delete the states and then add new states to correct the problem.  However, when I insert an image button such as (back_blue(90*27)) when I delete the rollover and down state and create a new state, the new state is created in the Text Button style, not the Image button that I have selected on screen.  So I have to go and set the [default image button style] to the same style in order to get it to work properly.  Not too difficult, just a pain in the rump.

This release of Captivate is not very pleasing to work with.  Who ever performed the UAT testing should be beaten senseless.  There are numerous issues that I have encountered with this improvement to Captivate 8.  I disliked Captivate 8 and my feelings toward Captivate 9 are not getting any better.  I have used and promoted Captivate as the best elearning development tool since it came out.  I have used it since it was RoboDemo and have generally found it to be a great tool.  It still is a good tool but the problems that exist seriously need to be corrected and fast, I am about to start building all of my modules in Storyline even though I dislike that product. I have been trying to convince my company that Captivate is the better product, sadly I currently do not have a leg to stand on in this argument.   It is currently less frustrating to work with Storyline than this version of Captivate. 

Another issue I found is that once I place the buttons on screen and make sure that the states are located in the proper location and the proper actions are assigned to the button, (i.e. Go to the previous slide; for the Back button).  If I reopen the file, I have to reassign the actions to the buttons because they have all reverted back to Go to the Next slide.  This is a serious pain in the arse.  I have created 5 modules and every individual file that I have opened, I have had to redo the buttons in it every time.

If I released a product like this, I would not stay employed for long.  I hope you fix this soon otherwise I will not stay a customer for long.

207
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 23, 2016 Feb 23, 2016
LATEST

I will not answer your ranting, I'm just a user like you and I don't like the UI change with CP8 neither. CP9 has a lot of improvements...and bugs. It appears you missed the hot fix released shortly after the discovery of one of the bugs you mention:

Hot fix | Adobe Captivate 9 issues

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Help resources