|
Indeed, the new version uses AVSVersion32.exe to check if avisynth 32-bit is installed. Previously, BD3D2MK3D did only a basic check to see if AviSynth.dll is present in the system32 or SysWOW64 directory. So, if the current check fails, it's probably due to a limitation or bug in AVSVersion32. It is used also by the About -> AviSynth Version menu to show the version number of the installed 32 and 64-bit AviSynth.
Can you open a Command Prompt window and launch AVSVersion32.exe, located in the BD3D2MK3D\toolset folder (you can simply drag and drop it from the BD3D2MK3D\toolset folder over the Command Prompt window and hit Enter). Then, copy and paste here the output of the command. Also, can you tell me if you have installed AviSynth classic with its installer, or manually ? In the second case, it is possible that it's the cause of the problem. Thanks!
In the meantime, I will uninstall AviSynth+ and re-install the classic version, to see if I can reproduce the problem.
|