Have anything divided by zero, default to zero value instead of undefined.

In expressions when you divide by zero, it causes the expression to break. it would be cool if AE was smart enough to ignore this and just pretend that anything divided by zero had the value of zero. so we don't have to put if/then statements into our code to avoid this.

an example is if you are using expressions to keep the stroke of a shape layer constant as it scales. the expression looks somewhat like this.

stroke/scale/100

if scale is zero, it breaks, but if the scale of the layer is zero, you can't see it anyways and so having it automatically have a value of zero would be just fine.

Change my mind.

After updating to 16.1 After effects is unable to allocate memory. I have a 64GB RAM system, but After effects is unable to load frames more than 10 frames HD at quarter resolution, suggests getting more RAM...
Also, the update doesn't migrate the panel layout settings or revert to them when opening a existing project which was saved with the panel layout (which is kinda weird, AE has a tendency to rearrange the panel layout when opening a project for an other user to their layout (very frustrating...), but when you actually want this to happen (because for some strange reason saved panel layout are always lost when updating) it's not happening (very frustrating...).
Also when going back to the previous version all preferences are lost and the migrate button in the preferences does nothing (very frustrating...).
Also panels change size at random, I can't figure out why (very frustrating...).
Also, third party panels open extremely big (when open for the first time, or after an update, since the panel layout is then lost) and the top bar is positioned well above the MacOS menubar, outside the desktop. I have to rearrange my Display arrangement in the System settings (placing my second screen above the main screen instead of next to it) to be able to get to the top bar of the panel to move them back inside the main screen (very frustrating...)

Maybe... ehmmm... Question:
Do you guys still develop After Effects to support multi monitor setups on the Mac?
I really like my dual monitor setup, but maybe this is just not something that is actually supported anymore...

This bug involves AfterEffects to Cinema 4D communication via Cineware. The bug may be in Cineware, or in After Effects itself. Observed in AE CC 15.1.2 (Build 69) with Cineware 3.1.22, but may be present in earlier builds as well, unknown.

Open test file CinewareTest.aep in After Effects. It references (six times) CinewareTest.c4d, also supplied.

The test file uses Cinema 4D to render the 3D comp Camera01_3D in six face renders (Cm1Front_3D/Cm1Left_3D/Cm1Right_3D/Cm1Up_3D/Cm1Down_3D/Cm1Back_3D) to build up a cube map comp CM1Cube, which is then converted to equirectangular for the final 2D comp Camera01_360VR. In normal use, that Camera01_360VR contains background 360VR imagery that the 3D elements are composited over top of.

Double-click the comp Camera01_360VR to view that comp. Go to frame 50 (to match the screen captures --- every frame other than zero will exhibit this problem).

Notice how the center region of the 360VR image exhibits discontinuities. This is the result of the bug. Screen capture: bad.png

For the correct appearance, see fixed.png In order to get that corrected image...

Double-click Cm1Front_3D.
Click the disclosure triangle for the Cm1Front camera layer.
Click the disclosure triangle for the camera's Transform.
On the Z Rotation channel, change 0x to 1x, ie create a Z rotation by 360 degrees.
Notice how the view immediately shifts to something completely different (correct!)
Double-click back to Camera01_360VR. Notice how the image now updates to be the corrected version fixed.png

That's the bug and the workaround (a nothing that does something). Now let's look closer.

Double-click back to Cm1Front_3D.
Set the Z Rotation back to 0x.
Rewind to the beginning of the shot.
Play
Note how the image remains unchanging. That is bad.
Stop
Set the Z Rotation to 1x.
Rewind
Play
Note how the image now changes steadily. These are the correct images.

At some frame other than 0 (say frame 50)
Set the Z rotation back to 0x. Bad image.
Change the Y rotation to 1x. Good image. Set it back to 0x.
Change the X rotation to 1x. Good image.
(Small changes to the transform do not have any effect)

Notice that the camera Cm1Front is parented to Cm1FrontNull. Cm1FrontNull is driven by expressions that pull the camera pose of the "real" camera from Camera01_3D. Each of the six face render comps does the same thing --- it has a ***** Null, and then its camera is hung from the null with a different constant Transform. This way the user can edit the real camera in Camera01_3D, and all six face cameras follow along with their own proper angular offset depending on the specific face involved.

The nature of the bug is apparently that the dependency analysis of the camera layers is seeing an exact identity rotation (X Rotation = Y Rotation = Z Rotation = 0) and deciding that the camera has not changed, and not sending that updated orientation to C4D. But of course the camera really is changing because of the parent layer --- the dependency analysis must look for a parent, not just that an identity rotation is present.

Hmmm, apparently this bug report tool doesn't allow .aep or .zip files. Kinda useless. You can get the file at this dropbox link:

https://www.dropbox.com/s/qnjpe51v7n3opg2/CinewareUpdateBug.zip?dl=0