Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

After Effects CS6 (11.0.2) update available

Todd Kopriva

Well-known member
Joined
Sep 2, 2010
Messages
143
Reaction score
0
Points
0
The After Effects CS6 (11.0.2) update is available. This update includes many bug fixes and adds GPUs for the ray-traced 3D renderer.

Details are here: http://bit.ly/AE1102
 
The After Effects CS6 (11.0.2) update is available. This update includes many bug fixes and adds GPUs for the ray-traced 3D renderer.

Details are here: http://bit.ly/AE1102

11.0.2.12 is freezing after the patch. I'm on windows 7, 64 bit, a quadro card. The adobe update was a huge update for all my adobe products btw (around a 1 gig i think).

There might be a conflict with what microsoft is trying to patch today? I sent off debug information to microsoft all ready.
 
11.0.2.12 is freezing after the patch. I'm on windows 7, 64 bit, a quadro card.

I'll try to get someone to take a look at this thread and help you out. We'll need a lot more information. Start by answering all of the questions here.

The adobe update was a huge update for all my adobe products btw (around a 1 gig i think).

There have been a lot of updates over the past few months. It appears that you got them all at once.
 
I did a update of AE on a completely different production machine (basically only runs AE) and is the file server. R3D files don't work anymore on AE on that machine(it has wierd frezes with black renders of the composite), so there has to be something seriously wrong with this build(i have never had AE stop working on two different machines after a update).

[update ... ]

I was able to unfreeze both my computer when i clicked on the footage, then clicked interpret footage -> main -> more options -> preset (default)". It is probably some wierd problem with adobe not supporting redcolor 3, overwriting the redcolor 3 import utilities, then exploding when it try's to read redcolor3 metadata.

As a "hint" to adobe, nuke supports redcolor3 perfectly.
 
Last edited:
You need install the plugin again. This is a beta and each update overwrite him.
Your right Manuel ... the plugin has been beta since 6/03/2012, adobe needs to get this plugin part of the base product.

Also the re-install process is error prone and not intuitive, i have to do a internet search each time, then walk through it on each machine that is running adobe. Since i have multiple adobe products on 4 machines i need to do this for each of the product folders, this turns into a hour of wasted time ... which occurs after I freak out and think my production pipeline has blown up.
 
Back
Top