Skip to main content
Participant
Jan 20, 2025 1:34 AM UTC
Question

Preview error after Black screen

Sample video 

I'm experiencing issues with the preview in After Effects. When I move along the timeline, I notice flickering in what would be the render viewer. However, when I play the project and let it run for the assigned time on the timeline, it displays normally.

This problem started on Friday, 01/16/2025. Today, Sunday the 19th, I haven’t been able to resolve it.

Before opening After Effects on Friday, I updated the graphics driver (a single update). I’m using a notebook (Bangho Max L5) with an Intel i5 processor (Windows 10 Pro OS), Iris Xe graphics, 32 GB of RAM, and three drives: (C) 222 GB, (D) 931 GB, and (E) 1.81 TB.

Here’s what I’ve tried:

  • Uninstalling the graphics driver and reinstalling it... (No apparent result)
  • Trying to install a driver version prior to the update I performed (Couldn’t do it); I have the drivers updated as of 01/19/2025
  • Uninstalling After Effects and reinstalling it (No apparent solution)
  • Installing a previous version (25.1) from Creative Cloud (No apparent solution)
  • Modifying After Effects preferences (cache, memory, preview environment, etc.)... NOTHING...
  • Deleting temporary files from the operating system (Still the same)

What could it be?       

3 replies

Participant
Jan 20, 2025 1:35 AM UTC

Friday 17th, I correct myself

Translate
nishu_kush
Legend
Jan 24, 2025 7:50 PM UTC

Thanks for sharing the screen recording and the details. 

Can you test After Effects with in Safe Mode with third-party plug-ins disabled? If it works fine in the Safe Mode, launch After Effects normally and disable your third-party plug-ins (go to Effect menu > Manage Effects) one by one to see which one is causing the issue.

Moving this thread from Bugs to Discussions for troubleshooting.


Thanks,
Nishu

Translate
Participant
Jan 25, 2025 12:04 AM UTC

Hello! As of today, the preview problem has been solved, directly by itself or at least that's what I think (unless you have updated something internally in after), (Or ​​maybe my drivers started working correctly)... But if it eventually happens to me again, I will try your solution.

Translate