autoload plugins not working

[theeht]

Is there some reason why my plugins aren't auto-loading? The registry is configured as described, with the plugin directory named accurately (this must have happened during installation--I don't recall doing it myself). But if I simply invoke a function without putting the "Loadplugin" line in the script, I get an error ("no such function" or something of the sort). Where might I be going wrong?

[digitalman]

Yes, certain plugins cause this problem with the latest beta of AviSynth. It may be a pain but just use the LoadPlugin line until AviSynth is fixed or the plugins are updated.

[Wilbert]

No. The plugins are not recognized, because they are not loaded.

I have no idea what the problem is. Probably a stupid question, you are sure AviSynth works (tried other scripts)? Could you reinstall it one more time?

[digitalman]

The one plugin that is giving me an issue is the new mpeg2dec3dg.dll, version 1.0.0, by Donald Graft. For some reason it will not auto load. You have to use the Loadplugin line. I am using the latest beta of AviSynth off of sh0dan's site.

[WarpEnterprises]

Cannot confirm.

mpeg2dec3dg.dll + AviSynth versions 2003-09-17, 2003-10-11 tested, works.

Please report:
- which OS
- did you test with VirtualDub? (ALWAYS use VD for testing, there is special "AviSynth-friendly" code in VD that helps finding errors)

Start REGEDIT and look into HKEY_LOCAL_MACHINE\Software\AviSynth.
There you really see what plugin directory is set. It occured once to me that it was not set correctly, even in a fresh install.

[theeht]

Originally posted by Wilbert
I have no idea what the problem is. Probably a stupid question, you are sure AviSynth works (tried other scripts)? Could you reinstall it one more time?

Thank you for the reply. Yes, AviSynth was working, but I took your advice and reinstalled. Now it works. The existing registry entry was:
"plugindir"="C:\\Program Files\\AviSynth2\\plugins"

But the reinstall added:
"plugindir2_5"="C:\\Program Files\\AviSynth2\\plugins"

With the same directory indicated for both. FYI I believe the first entry was created when I installed AviSynth as part of GordianKnot.

[WarpEnterprises]

Ok,this should only happen if you select "custom install" and use the same path as AviSynth2.0.

But it seems that the check of an existing regkey is too tight.