After Effects Error - Zero Denominator comparing ratios (17 :: 16) error in Ae version 23.6

[saladdreesing]

Hey y'all, I'm really stuck.

This error keeps popping up for me and I have no idea how to solve it. It'll appear as I'm trying to play a sequence with an image in it. I made other sequences with images in them a few hours ago and rhey're all fine. But now when tryong to add anything new, it gives me this error and doesn't go away at all - no matter how many times I hit 'okay'. Any ideas?

Thanks!

Title edited by Mod.

[Jeffrey3113140136mh]

I've been fighting this error every day for a couple weeks now, there is no consistent cause or characteristic to any of the comps causing the error. My latest error occured in a 2D comp with one layer, a mov with alpha. No 3D layers at all. Very frustrating.

[jmg007]

Hi. Having the same problem. But the change to Classic 3D Rendere didn't fix the issue. I was working on a project and then After Effects was updated - continued working on the same project after the update and every time I hit the spacebar to begin playing a sequence the error will appear. Once the error message disappears - after hitting the enter button repeatedly - the sequence just plays normally. I'm assuming something is null or 0 somewhere but just can't quite find where. 

[jmg007]

Also, if I drag the timeline handle I get no error - it just happens when hitting the spacebar.

[Mark25159040zoyk]

Had the same issue. Had the Classic renderer and everything. But then I realised that it only happens when I hit the "spacebar" to playback, but didnt happen when pressing "play" button on the top right. I figure it has something to do with framerates. Because it gived this error box many times in a row, it could be the number of footage that has the strange FPS. And in this project I have every framerate possible; 24 , 25,  30,  59.94 etc. But somehow it is gone now. Purged the history and restarted... hopefully not coming back.

[Clubhouse]

Also experiencing this issue, not using any 3D elements. All footage is from a source that has never caused issues, getting issues on media that I know worked before the app was updated.

Yet another case of Adobe updating their software and breaking it, happens every single update. Absolutely useless.

[Jeffrey3113140136mh]

I've noticed that as well

[Nikitafu34]

I have been getting the same issue among many projects. Ive noticed it only happening if I tried to preview the comp while a keyframe was selected. But now it is just stuck. Classic Renderer didnt help me.

[Nikitafu34]

This new version of AE has also been maxing out my memory for some reason (64gb) which Ive never seen happen, and previewing has been a nightmare in general. I installed the last version 23.5 and now my project is running smooth so far and memory is not even half used up.

[Nikitafu34]

Scratch that. My memory is still being obliterated with the last version. Couldnt edit my last post

[Juniperf]

Unsure what's going on, but an error I've never seen before has been making frequent appearances over the last couple weeks. 

I understand the source of the error to be that somewhere in the project, some script is attempting to divide by zero. I'm not sure where this could be occuring, as this error even appears in new projects where I do not add any scripts. 

Is this a common experience? Every project seems of mine seems to be unsafe from this error. Could it be caused by an outdated plug-in?

[jenkmeister]

It's a bug in 23.6. 24.0 will have a fix for it. The 24.0 beta that drops later today should also have the fix for it.

A workaround some people have found is to switch away from the Cinema 4D renderer back to the Classic 3D renderer. 

[Juniperf]

Great, thanks! Glad to know I didn't break all my projects accidentally lol

[defaultbaf3r5rbpdv7]

This workaround worked for me... I could even delete that extra layer once I hit play once and keep using Cinema 4D renderer.

It seems like this error is an update bug... 

[Gabriel2274855065oc]

The good old Zero Denominator-error ... I know that switching to Classic 3D renderer solves the issue but I'm working on a project where I need to extrude and bevel a shape layer so using it is not an option.

What is the solution to this??

[jenkmeister]

A fix will be available in Beta builds next week, and when 24.0 releases closer to Adobe MAX. You could also go back to 23.5 if you aren't using specific features from 23.6 until those builds are available. 

[gtuxen]

Great to hear! Thanks 😃

[ozonetv]

If you're using an Environment Layer (in C4D renderer), try deleting it. Thats how I fixed the same issue. Of course, now I don't have an envirnment layer 😕

[upslon]

Hi. Having the same problem. But the change to Classic 3D Rendere didn't fix the issue. Tring to downgrade to 23.5... 🥴 Adobe being adobe...

[jenkmeister]

Yeah, I'll admit, this was a dumb bug to let slide in by us. It will be fixed in 24.0, and in the 24.1 beta we push out later this week. Sorry for the issues. 

[Gwen5ED0]

OS: Windows 10 Pro

Deleted cache files inside AE, played comp in quarter view

Error displayed when converting text layer to 3D using Cinema 4D renderer. It is crucial to convert it to that or else the desired 3D eefect won't be applied. Had seen the old forums dating 2017 and it says to click on Classical 3D or revert to the prev version of AE. But I can't as I bought the app 5 days ago. Is it possible to get it fixed any other way?

[Gwen5ED0]

But what if that feature is required? I am asking this because i have to turn each word of the text around in the comp and turning it to Classical 3D doesn't make it seem 3D. Classical 3D makes it look flat

[Melanie Stirner]

Hi 🙂

Thank you very much, was going crazy with that error message. It seems to disappear when I change the renderer from Cinema 4D to Classic 3D. So it helps for now to work fluent in AE again, but I need to switch back to C4D render for rendering, because it does not fit with the look with Classic 3D. My AE is up to date btw. 😕

[ozonetv]

Can you check to see if its related to Environment Layers in C4D Renderer...I delete that and the error goes away.

[Melanie Stirner]

I did not use any environment layers 😕

[jenkmeister]

If you need the Cinema 4D renderer, you can install the previous version of AE (and media encoder if you're using that - it needs to stay on the same version). The fix for the error is going into the Beta this week and will be in the next non-beta release in a few weeks from now.