The 64bit Visual Pinball Revolution Is Upon Us - Convert Now!

I have a cabinet but no toys. I install DirectOutput for DOFLinx support which I think is still 32-bit based. I can still test that the driver is active via B2S Settings. The dialog title is not proof one way or the other. The Settings dialog shows x64 for me whether I am running VPinballX or VPinballX64.

However, there are a couple of differences in those images from what I have:

1. The x64 Plugins settings image shows PinUpPlayer Display Driver V:0.5.70...  If that is 0.5.7023.26826 with datestamp 2019.03.25 then that is suspicious as this is the x86 driver and not the x64 beta driver. You sent an image of your x86 Plugins settings that shows PinUpPlayer Display Driver as V:0.5.7023.26826 as of 2019... That looks to me like the correct x86 PinUpPlayer driver. The x64 PinUpPlayer Display Driver that I have is V:0.5.8351.33321. I'm not saying that this has something to do with DirectOutput but it is suspicious that something is off with the install.

2. I have a DirectOutputx64 folder and you have a DirectOutput-x64 folder. The difference in folder names don't matter as long as you have the Shortcut links/target paths in the B2SServer Plugins and Plugins64 folders setup correctly. In my DirectOutputx64 folder I only have the contents of the DOF-x64 archive. I can't tell from the images what you have on your C drive but if you copied all the contents of your original DirectOutput folder into DirectOutput-x64 then that would be a big problem. The only file I copied over from the original DirectOutput folder was directoutputconfig.ini from the Config folder to DirectOutput64/Config. Again, I don't have any toys so for me the contents of that file are minimal. In other words, I don't have any DOFLinx stuff in my DirectOutputx64 folder. 

The B2SServer wiki was what I followed when I manually updated to add x64 support. I don't recall at this point what I did to run RegisterDirectOutputComObject.exe. The wiki calls for running the one in the original DirectOutput folder or DirectOutput-x86 folder. That's probably what I did. 

From here it's the basic questions - Did you make sure executables and dll files are unblocked? Antivirus turned off and/or pinball folders excluded from scans? Re-check the target path in your B2SServer/PlugIns64 shortcut?

Like I said, I don't have any toys installed. I have DirectOutput installed merely to run DOFLinx. I have not even tried to run GlobalConfigEditor.exe. I do have the correct drivers installed and showing active when I look at either x86 or x64 platform and check my Plugins settings.

Do you have separate folders for DirectOutput-x86 and DirectOutput-x64? DirectOuput-x86 should only contain the drivers and associated files that come from the latest beta build for x86 DOF R3++ at mjrnet.org. The DirectOutput-x64 should only contain the drivers and associated files that come from the x64 DOF R3++ build linked in the upgrade wiki at the B2S Server github. The only file that needs to be shared at this point is Config/directoutputconfig.ini file.

You have to be positive that the 32bit DirectOutput system is fully working before you attempt to add x64 DirectOutput.

If you were going by the migration procedure with Baller Installer, they would have you update PinUpPlayer before DirectOutput. I think that was the order I did it when I updated manually.

I may not be much further help here because I don't have any toys installed and my only check is via B2S Server. And it worked for me the first time. I hope that you have a backup to go to so that you can test your setup fully on 32-bit before trying again to add 64-bit. 

The thing to remember is that aside from B2S Server, everything dealing with 64-bit is beta. Nothing wrong with waiting until the process is stable and the update path is nailed down and made much more user friendly. I don't consider myself in beta testing mode, and I haven't downloaded any tables that have to be run 64-bit. I'm still running 10.7.4 (although that itself is still beta too).