Copy link to clipboard
Copied
Hi. I have a few users who have specifically recieved this error when using my plugin when using windows remote desktop to render on a slave machine. Some have had success fixing the issue by installing Nvidia's windows remote desktop accelerator, but others haven't. Has anyone else had users experience this?
I have seen that this error code can be caused by other issues as well, such as a corrupted install or a firewall blocking permission. However in my case I believe the issue has something to do with openGL as the plugin is built on the GLator sample.
Copy link to clipboard
Copied
yo james! whats's up?
if i recall correctly, this error is due to some missing dlls that the plugin as a depenency on.
throw you plug-in into dependecy walker on one of the problem machines and see if that's indeed the case.
Copy link to clipboard
Copied
Hi Shachar! Mostly just trying to keep my ancient OGL plugins alive 😄
Thanks. It seems his machine is not loading opengl32.dll and glu32.dll, which I am assuming is the cause of the problem. He has a tesla GPU so not sure if that is contributing to the problem. I'll send him my dll's as a desperate fix and see how that goes.
Copy link to clipboard
Copied
i think it's unlikely that an nvidia GPU will be installed without opengl32.dll and glu32.dll being installed along with the rest of the software components...
i'm guessing he upgraded to the latest driver version. i would ask the user to look for these 2 dlls on his machine, and send you back the path on which they were found. if there's an oddity in the path that you can make sense of, perhaps you cound figure out a way to make the plug-in find it. (mereley hypothesizing here)
Copy link to clipboard
Copied
Here is the DW report. I see his dll's are in the correct location. However it appears he ran DW on the .aex inside his downloads folder. Am I correct in that DW needs to be run on the .aex inside AE's support files, with AE running and the effect being applied for the report to be of use?
Copy link to clipboard
Copied
i don't think it would matter, since the two dlls are in the system32 folder where the plug-in would find them regardless of it's own location.
now that the two dlls are there, is the plug-in working or not?
Copy link to clipboard
Copied
Find more inspiration, events, and resources on the new Adobe Community
Explore Now