allheart Posted January 16 Posted January 16 Need some advice. If I use any table and a VPX x64 version, the B2S shows up just as expected. However, using the same table and the correspond VPX x86, the table loads but the B2S never does. Any thoughts. I've tried multiple tables and the same effect. If I rename the B2S to something "wrong", the x64 version throws the expected error. The x86 version doesn't through the error. Thanks for any suggestions.
bthlonewolf Posted January 16 Posted January 16 What version of B2S? Update to the latest version (within the last few days like this one: https://github.com/vpinball/b2s-backglass/actions/runs/20932172206), or roll back to 2.1.3, OR keep your current install as-is, but run and use only the B2SBackglassServerRegisterApp.exe from 2.1.3 (or slightly later). The issue is in register app not registering the libraries on x86 but has been fixed a few days ago.
allheart Posted January 16 Author Posted January 16 Thank you. Just tried the build you suggested and it does work everywhere that I tried. Thanks.. Maybe you know this, but when running the registerApp and allowing the context menus to be installed, it only seems to add them to the directb2s. The older version of the registerapp, added the context menu to the vpx table. Since the res file needs to match the VPX filename, it seems to make more sense to go with the VPX context menu. Any idea why it was changed? Thanks again.
allheart Posted January 16 Author Posted January 16 Okay, I found the comments on the context menu being moved to the B2S instead of the VPX. Not really liking that, but my solution is to use an older RegisterApp, and to not register the library, but only the VPX Context menu. On my system, it now appears on both. Thanks again
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now