Leaderboard

I had the same issue, my system had the 32 bit Direct Output installed in a ‘DirectOutput’ folder and the 64 bit version in ‘Directoutput64’ the issue occurred when I registered the 64 bit version (which is not necessary). At that point the PinballX plug-in would only find the DirectOutput64 path which causes the plug-in to fail. I fixed this by: 1. Making a full copy of the DirectOutput64 folder and renaming it ‘DirectOutputPlugin’ 2. Going into the DirectOutputPlugin folder and running the DirectOutputCom registration tool 3. Deleting the entire contents of the DirectOutputPlugin folder 4. making a copy of the contents of the DirectOutput folder into the DirectOutputPlugin folder This fixes the issue as the registry now sends the PinballX Direct Output plugin to the DirectOutputPlugin folder which has the working 32 bit files. It retains the original Direct Output folder structure which, as they are called by VP from the VP 32 and 64 bit plugin folder shortcuts, is unaffected. A few notes: - You will only get this issue if you run the 64 bit Direct Output Com registration tool, If that has not been run you have a different issue. It’s easy to check by simply running the PinballX Direct Output plugin configuration and seeing which version of Direct Output the plugin is pointing to. - Make sure that you have a working VP installation first that’s calling the right 32/64 but version of Direct Output - Back everything up first, just in case, please. - When you have finished you can delete the majority of files and folders from the DirectOutputPlugin folder if you wish, you really only need the Dll, Com object, the five DirectOutput files downloaded from the online tool and the ‘Config’ folder. You don’t need to do this but I am OCD driven and like a tidy setup. - It’s a good idea to update the Plugin to Mike’s rather excellent tweaked version which is in the download section. Hope this helps out.