Preview is stuck in a loop and is unresponsive
RAM Preview becomes unresponsive to clicks, spacebar, Num0, ESC, etc. Playback continues on loop and the only way I've found to regain control is to minimize/maximize AE or close the application.
Build 17.0.4 Build 59

-
Gopesh Sahu commented
Hi Guys .. I purchased CC product recently. I am beginner. Ae preview never stops and hang the application even for 5 sec composition. It worked well for few weeks and now its giving trouble. I tried my best to resolve but its not working. I want go away from this cc. I have 16 GB ram machine. I don't want to change any settings/graphics just to work with Ae. As per Adobe system pre-requisite my machine is perfectly fine. Its a bug. My other animation software Autodesk Maya works perfectly fine.
-
Björn Ahlstedt commented
This is an NVIDIA driver issue - install an older Studio Driver or switch back to GeForce Game Ready (recommended) -- problem should resolve.. Good luck!
-
Sebastien Perier (AE Quality Engineer) commented
Hello Jesse,
We have identified a bug with the latest studio Nvidia Drivers, and it looks like this is the source of your preview issue. I would recommand updating to the latest "gamer ready" drivers.
Hope this helps,
Sebastien -
Jesse Petersen commented
The new update is full of bugs. Every time I preview a comp AE gets stuck in playback and I can't stop it. AE has been the most reliable and least faulty app Adobe has made. Please don't break it too.
-
Dinamo 3D commented
any news? I'm tired of keeping closing the program and then restart over and over again
-
Tjeerd de Jong commented
Still present on AE 17.1.1..
-
Dennis Sibeijn commented
Installed the 442.19 Studio Driver and the problem is gone. I'm only not too happy with installing older drivers to fix stuff though. Since Nvidia and Adobe are promoting each others products, I'm really disappointed (but totally not surprised either) that it's not fixed by now.
-
Lance Moody commented
Jesus! Can you guys seriously not fix this?
-
Marc Trzepla commented
Just echoing the sentiment of everyone else frustrated by this bug. What a drain on productivity.
v17.1.0
-
Tony Cooper commented
Cory's solution was it for me... I switched to NVIDIA's Studio driver and it has affected a lot of things in Ae and Pr... switched it back to Game Ready and all is well again. :\
-
anthony marzilli commented
I did the game ready driver like Cory Mentioned and I haven't had the issue happen in a few weeks. Fingers crossed.
-
Nicolas VANDECASTEELE commented
I encourage you to revert back to version 17.0.4 which does not have the problem. I will stay on this release until a fix is proposed.
-
Kenneth Bell commented
Yep same here. AWFUL bug, please fix ASAP!
-
SirCheeseKnight commented
Same problem here, really annoying
-
Seb James commented
I've just come on here to report the same problem and found your post. It's driving me up the wall!
Running the latest version of AE on Windows 10.I need to run the Studio Nvidia driver as it works with RTX with Vray...
-
Philéas commented
Hi ! I had this problem too using a Dell XPS 15 9570 (GTX 1050 Ti Max-Q), but reverting back to the Game Ready Driver instead of the Studio worked also for me. Thanks @Cory Anderson !
-
Cory Anderson commented
Hey everyone, I've found a solution on my end of hardware and maybe it will work for you too. I'm on windows 10, and I'm using two GTX 1080s in SLI.
I was using the "studio driver" under the GeForce experience firmware, and that's where I experienced this issue even when I reverted back a couple versions of AE. I decided to try switching to the "Game Ready driver" an viola! No more issues!
Hopefully this works for some other folks out there!
-
Brittany Alford commented
Very frustrating and makes after effects unusable
-
john miller commented
still an issue for me V17.0.6
-
Dennis Sibeijn commented
Same problem with 17.06, reverted back to AE16. Only way to get out of it was by minimizing/maximizing After Effects like crazy and pressing escape at the same time.
Specs:
Threadripper 3970X
256GB
4 x RTX2080ti
Windows 10 pro 10.0.18363Would have expected a fix by now