Skip to main content
Andy_K_nz
Andy_K_nz
Inspiring
August 24, 2015
Question

Got an issue opening CP8 projects in CP9? I have one :(

  • August 24, 2015
  • 2 replies
  • 799 views

Hi All,

I'm interesting to hear from anyone that has had problems opening Captivate 8 (or earlier) projects with Captivate 9. So far I like the general enhancements that Adobe have made but came across an little bummer with objects using the button states from CP8, they no longer work in CP9. Like I said it's a bummer, not a major issue but it would have been nice that Adobe was able to transpose the button state feature from CP8 to CP9. The new states feature is much better but this will cause an issue for me if I want to upgrade older projects to CP9 as I will need to reset any buttons built in CP8 with states. As always I would be happy if someone has a work around for this but if not... oh well

If you have encountered any similar problems loading old projects in to CP9 then it would be really good if you could post them here.

Thanks,

AndyK

    This topic has been closed for replies.

    2 replies

    R
    Randal Perry
    Participant
    September 18, 2015

    The two major flaws I have encountered saving a CP8 file in CP9 are loss of conditional advanced actions and damaging of timelines. if it isn't bad enough that I had to rewrite all these advanced action the bigger problems still remain.  The two attached graphics explain more problems caused by CP9. Let's be clear though. Adjusting the timeline won't correct the problems that exist with motion paths and motion effects that fail to reach 100% of their motion. This course is over 500 slides of the same problems.

    nsukumar
    Adobe Employee
    nsukumar
    Adobe Employee
    September 19, 2015

    Hi Randal,

    We are working on the conditional action issue. we will update you the status soon. Can you please share the project where you are facing the above timeline issue so that we can try the issue at our end. please upload it to a shared workspace and send us the link to nsukumar@adobe.com

    Thanks,

    Nimmy Sukumaran.

    R
    Randal Perry
    Participant
    September 21, 2015

    Hi Nimmy,

    I appreciate that you are working to get to the bottom of this issue. I am not sure what you expect Adobe will do ultimately to take responsibility for the problems this is causing developers. Anyway, I won't send you this project for a couple of reasons. One, there is nothing special about it, so the problems can easily be duplicated by Adobe or someone else simply by importing earlier projects into CP9. Two, I don't ultimately have the right to share the source files of projects that belong to my employer. You are welcome, however, to use the screen shots of the timelines that I posted above as an example. To elaborate a bit though, this project has only a dozen, or maybe fewer, timelines that are this complex, and complicating the issue. But, this project has close to 500 slides and everyone of them has potentially been altered by CP9. This is unacceptable.

    Thanks,

    Randal Perry

    Lilybiri
    Lilybiri
    Legend
    August 24, 2015

    The work flow for states has changed totally now. I didn't have time yet to double-check but have an idea for a workaround. Could you tell me if you saved the style for those shape buttons and do you see the style in the Object Style Manager and Properties? You can change the style for shape buttons in CP9 as well in the OSM, they have now the same presentation in the OSM as normal buttons (something I like a lot as new feature, but no one talks about it). If you can edit that specific style in CP9 and it is not overridden in the project you have to upgrade, maybe the style change will propagate to all shape buttons.

    Andy_K_nz
    Andy_K_nzAuthor
    Inspiring
    August 24, 2015

    ‌Hi Lieve,

    I had the same idea about the OSM too but also have not had the time to look into it much. I only had a couple of hours free today to look at what is involved in converting CP8 projects to CP9 and immediately hit a couple of problems that sucked up all my time. Thanks for your input and I'll check out if there is any work around using the OSM when I get another chance.

    AndyK

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices