Hi. I need a little tech support regarding ProAnimator for After Effects 8.6.1. I've written four emails to firstname.lastname@example.org and heard nothing back for days. You guys use to be Johnny on the Spot with that! In case you're checking here, the After Effects version itself is 17.02 (Build 26) (aka 2020) and the OSX on my mac is Mojave 10.14.6 and my video card is a Radeon RX 580 8 GB.
The error is "After Effects error: Couldn't find main entry point for ProAnimator AE - 64-Bit.plugin" Then the whole app crashes.
I've tried re-downloading and re-installing the plug in, but that was not a successful remedy.
I just downloaded the trial version for 2020 AE and I am getting the same message on my first attempt at using the plugin. Very disheartening. I have reached out to support to find out what limitations there are with the trial but have yet to hear from them. I also have asked what this error message means. I'm only writing you this so you know that you are not alone.
IINM, none of the plug-ins for Ae are qualified for any version beyond Ae CC2018. They stopped updating Warp to work with anything after CC 2014, I believe. I think they've given up supporting their products, although I see they are still selling them. I've given up myself. Getting Invigorator not to crash constantly has been a fool's errand. Element is far more stable. 3D Flag still works for me pretty well, even in Ae 2020. I wish they would update Invigorator, because it does Ray Tracing (refractions through glassy materials), which Element doesn't and probably never will.
I agree that they used to have incredible support. I surmise it's a pretty small company - two or three people.
MacPro7,1 24-core - 256 GB RAM - AMD Radeon Pro Vega II 32 GB - 10.15.3
Sorry we haven't figured out a fix sooner. There's a problem when running Mojave and AE 2020. For most people it doesn't appear if you had already been running the software before updating to AE 2020 which is why it took us down the wrong path for awhile but we are now making progress. We fixed the "no entry point" problem but then another one popped up that was a hidden by the first. Will let you know as soon as we know more.