After Effects 13.7 update crashes Cinema 4D

[TP-Link_Italia]

I updated After Effects to version 13.7 and now when I try to open a new Cinema 4D file I am getting this error message: "Installation Error. CINEMA 4D version (16.038) does not match Resource folder version (16.028)! Please reinstalla CINEMA 4D correctly!" How can I deal with this since Cinema 4D Lite comes with After Effects? Any help would be greatly appreciated.

[kglad · Accepted solution]

reset your preferences - http://helpx.adobe.com/after-effects/using/preferences.html

[Joop Pillac]

I have same problem. The answer by kglad does not help me. What should I change or do in preferences html.

[kglad]

move the preference files to a sub-directory.

restart ae and check that new preference files are created.

[Joop Pillac]

Can you be more specific?

Where do I find the preferences files? And where should the sub-directory be located? In the preferences files?

Thanks for helping me but I think its a bug in the latest udate. Adobe shoudl come up very soon with a new update. What do you think?

[kglad]

click the link in message one:

• (Windows) \Users\\AppData\Roaming\Adobe\After Effects\13.7
• (Mac OS) /Users//Library/Preferences/Adobe/After Effects/13.7

[Joop Pillac]

Well sorry to say but this link cant be found at my PC. So my problem remains and will wait for official response from Adobe AE team. Hopefuly soon

[kglad]

(for anyone interested, un-hide hidden files as shown in the message 1 link.)

[Matthew Marlowe]

I had the exact same problem on my PC. I resolved my error by going into the installation directory of Creative Cloud, then into the After Effects CC 2015 folder, Support Files, Plug-ins, MAXON CINEWARE AE, (CINEWARE Support), lite, resource, then opening the version.h with Notepad(or any other plain text editor), and finally editing the only 2 digit into a 3.

I hope this helps!

[sanNOji]

I have same problem.

To start with do advice as Matthew . It was R16.

[Joop Pillac]

Thank Matthew. Will see if this is the solution in my case. But anyway I would like to have a feedback from the Adobe team about the problem and how they will solve it.

[madnessgraphicspoland]

it works for me, Thanks

[xiwers]

Thanks Matthew Marlowe. Sometimes Adobe isn´t aware of these details and you made it. You saved my day bro

[centaurincident]

Thanks--this worked for me!

[przemektrasnik]

it works for me

[josep88712381]

Hi how can I go to this folder ?

[adam s]

Look at Matthew Marlowe Jan 28, 2016 6:31 PM post up on this thread. Not sure the route on a Mac but assume its not terribly different, you can always to a file search.

[geomagnet]

Whoa...dude!   How in the world did you figure that out?  That's totally insane ~ but it worked like a champ.

[MOSTAFAHMY]

Matthew Marlowe

thank you, just follow his instruction, you are creepy awesome how did figure it??

[Charlie_Brendl]

@Matthew Marlowe

Thank you for help. Works for me.

[Brique]

I had the exact same problem.  Matthew Marlowe's suggestion above worked for me.  I found I had to create a copy and edit outside of the folder where this was located due to administrator restrictions on the folder (PC).  Then I just copied the edited file into the folder and gave administrator permission when the pop-up came up.

[TP-Link_Italia]

I tried deleting and reinstalling AE from zero and now C4D seems to work correctly. The preferences are not the problem, I saved them while uninstalling AE and it works alright.

[Joop Pillac]

‌i have deletef the updated version of Adobe AE from laptop and then reinstalled the latest version.mnow it works. But  i think this is not service I expect from Adobe when they pushed new versions. But i am happy to continue now with my work

[adam s]

I would not classify "resetting your preferences" as the correct answer but rather a "possible option". It was a waste of my time getting everything back up and running after the reset and not fixing the issue.

Matthew's response with editing the H file was correct, had to change the "2" to a "3". This appears to be just an issue with 13.7 as I didn't have the issue previously.