RxLaboratory Forum

Please help.

I used Duik 2.0 on after effects 2019 no problem and loved it. Went to use it again after my AE has been updated and now no matter what I do i get the error message : Unable to execute script at line 37164. Null is not an object.
I've re downloaded duik, Ive uninstalled it, tried all the different ways to open it on AE and even removed AE and downloaded it again. Does anyone know/understand why this would be happening to my duik

Can you try this:
https://duik-docs.rainboxlab.org/instal ... stall-duik
to see if it helps?

In your Documents folder, you may also find a "Duik Bassel" folder, try to remove it, this may help too

Thank you, I had already have done the steps in the link several times and what seemed to be the culprit was the folder located in my documents. Thank you! I didn't even know it was there.

The procedure should deal with it too... I'll change that.
thanks for the feedback

Hi there,

I've also got the same issue, AE2020, Macbook Pro2019, Catalina (10.15.7).

The issue has a different script line though.

"Unable to execute script at line 39035. settingsFile is undefined"

I checked the document folder and there was no new files there that I could see. Deleted the files and re-downloaded and it still didn't work. Any help would be appreciated. Thanks so much.

Hello,

i have the same issue, AE 2018 (15), Windows 10.

Get the error "Unable to execute script at line 39035. settingsFile is undefined"

Tried to re-download Duik, followed the steps on the website on ways to fix bugs and also made sure to disable the option “Allow scripts to write files and access network” which is either in the General section.

Thank you in advance for any help!

It seems the update from yesterday introduced this new bug. I'll fix it today, sorry

It's fixed, and the fix will be available in a couple hours

sorry for that !

thanks for the quick fix! but now i have another issue:

"Unable to execute script at line 39035. Function container.add is undefined"

Thanks again for getting back to us so quickly.

Can you try with 16.2.21 which was just released and tell me if you still have an error? In which case, give me again the exact message and line.

Thanks for your feedback