7 Replies Latest reply on Aug 21, 2016 6:24 AM by Roei Tzoref

    Getting back to CC 2015.2

    taylorm36109209 Level 1

      Is there a way to go back to CC 2015.2 without having to jump back all the way to CC 2015? Like, without having to use a 3rd party.

       

      Had to update and I have plug ins that don't work in 2015.3 and features that aren't in 2015.2.

       

      If I have to get it somewhere else other than Adobe, does anyone have any good suggestions?

        • 1. Re: Getting back to CC 2015.2
          Roei Tzoref Adobe Community Professional

          CC2015 is CC 2015.2 which is an update for 2015.1 which is an update for 2015 their all in the same version which is called CC 2015. it's also called 13.7.2 on Mac and 13.7.1 on PC.

           

          CC 2015.3 is a new version that's also called 13.8.1 which is an update for 13.8.0. you can have both 2015.2 and 2015.3. if you remove 2015.3 - you just removed a whole version that's not related to 2015 (2015.2). if you removed CC 2015 (which is also 2015.2) you just removed a whole version and if you re-install you will get CC 2015.0 but you should install all the way to 2015.2. a rule of thumb is - always use the latest of each version. if its 2015 - use 13.7.1 on Windows, 13.7.2 on Mac. if it's 2015.3 - use 13.8.1. -  - did all of that make sense to you ?

           

          What exactly wrong with the plugins? maybe we can help. for me just moving the plugins from the one folder to another did the trick. and eventually I reinstalled them because some required update for 2015.3

          • 2. Re: Getting back to CC 2015.2
            taylorm36109209 Level 1

            The CC 2015 version available on the "Previous Version" tag on the Creative Cloud is 13.5 and the Mac equivalent I was on was 13.7, which is between the two versions.

             

            I un-installed AE and then updated to 2015.3, but I have the BAO Mask Warper from aescripts and that wasn't working so I wanted to switch back at least until I finished working on some things. Lumetri isn't in CC 2015 (the 13.5 update) so that's another problem for me. The un-install wiped the files for 2015.2 so I don't have them anymore though I guess I could just pull Lumetri from the 2015.3 files I still have and see if it'll work in the CC 2015 space (?)

             

            I already have talked to the BAO Mask Warper guy to see about getting it squared in 2015.3, but he's not gonna look into it until Monday.

            • 3. Re: Getting back to CC 2015.2
              Roei Tzoref Adobe Community Professional
              The CC 2015 version available on the "Previous Version" tag on the Creative Cloud is 13.5 and the Mac equivalent I was on was 13.7, which is between the two versions.

              if you have 13.5 you need to update through the CC App to 13.7.1.  BAO Mask Warper and Lumetri will work fine in 13.7.1.

               

              again: 2015.3 is NOT an update for 2015, it's a whole new version.

              • 4. Re: Getting back to CC 2015.2
                taylorm36109209 Level 1

                Download the trial of BAO Mask Warper for 13.7.1 and see if it works for you. Some people seem to think that some unupdated plug ins using OpenGL may not be functioning properly on the new version, since apparently they updated it in someway.

                 

                Essentially, if I make the effect visible on a layer it goes invisible in the new version.

                 

                You shouldn't auto-update to the newest version mid project and have issues likes this. I know for a fact now.

                • 5. Re: Getting back to CC 2015.2
                  Roei Tzoref Adobe Community Professional

                  Download the trial of BAO Mask Warper for 13.7.1 and see if it works for you.

                  I used recently finished a very intense project with BAO Mask Warper (not a Trial) and Lumetri on 13.7.1. everything worked as expected.

                   

                   

                  Some people seem to think that some unupdated plug ins using OpenGL may not be functioning properly on the new version,

                  making sure again - we are talking about 2015.2 - it's not that new : After Effects CC new features | Faster importing options  13.7.1 is from march.

                  You shouldn't auto-update to the newest version mid project and have issues likes this. I know for a fact now.

                   

                  that is good practice, I agree.

                  • 6. Re: Getting back to CC 2015.2
                    taylorm36109209 Level 1

                    Where is your M3D Warper/Renderer in your CC 2015.3 files? I think the renderer is what's giving problems but AE is finding the plug ins fine.

                    • 7. Re: Getting back to CC 2015.2
                      Roei Tzoref Adobe Community Professional
                      Where is your M3D Warper/Renderer in your CC 2015.3 files? I think the renderer is what's giving problems but AE is finding the plug ins fine.

                       

                       

                      but why are we talking about 2015.3 when we already established that you want to use 13.7.1 ?

                       

                      let's get back to your original question

                      Is there a way to go back to CC 2015.2 without having to jump back all the way to CC 2015?

                      if you uninstall CC2015 (2015.2), and you want to reinstall it, you will get to install it as 13.5 (2015.0) . then you should update to 13.7.1 (2015.2)- you will have Lumetri and BAO Mask warper works fine for me.

                       

                      if you uninstall CC2015.3, and you want to reinstall it, you will get to install it as 2015.3 - 13.8 then you should update to 13.8.1. for me Lumetri works fine and BAO too.

                       

                      this whole mess would not be so confusing if Adobe simply called the latest version 2016. but for reason we will probably never know, some marketing scheme was implemented to call this 2015.3. this is true to all of CC. photoshop is 2015.5 too. oh well, at least it works!