jarr3 Posted February 13 Posted February 13 Fact is that everything before 2.1.6 relies on the Player Window of VPX will show the table name in the title. This has now been fixed in the latest builds of VPX 10.8.1 by adding two lines in Controller.vbs: Set B2SController = CreateObject("B2S.Server") If B2SController is Nothing Then Err.Clear Else B2SController.B2SName = B2ScGameName B2SController.TableName = ActiveTable.FileName <-------- This one ----------------CUT-------------------------------- On Error Resume Next Set Controller = CreateObject("B2S.Server") If Controller is Nothing Then Err.Clear If TableType = "VPM" Then LoadVPinMAME VPMver, VBSfile, VBSver End If Else Controller.B2SName = cGameName Controller.TableName = ActiveTable.FileName <-------- This one Without these lines, B2S Server has to walk through all opened windows to try to guess what is that flipper table you just opened. So this is now solved in B2S Server 2.1.6 which means B2S will not search the windows for the VPX player window when the TableName variable is filled. If it is not filled (an older version of the script is installed) it will still do the hacky search. You have not said which VPX version you use... you need the BGFX version, cause this is the one which will become the next VPX release. And the BGFX version does not have the player window with the table name in the title anymore... The B2S Server is not changed in anyway I know of, how it quits.
Tengri Posted February 13 Posted February 13 @jarr3 me? I wrote this in my first post on page 1 On 2/9/2026 at 9:27 PM, Tengri said: I'm a bit lost in the different explanations. I'm running 10.8.1 BGFX 64bit on Windows for quite some time now. .....
jarr3 Posted February 13 Posted February 13 @Tengri sorry, missed that. But as I beleive you state there, neither the new b2s plugin nor the B2S Server work? This is precisely the issue I am trying to address here. The 'old' B2S server now works with VPX 10.8.1 BGFX. I tried two handful of flipper tables with and without PUP, PROC and DOF. There were no problems with either. However, I have noticed that some tables are having problems with the plunger using a dudes cab.
Tikimaster Posted February 13 Author Posted February 13 (edited) Hi Friends! I just copied over my running server (B2SServer-2.1.5.1-d445bce-win) with B2SServer-2.1.6.387-3f3f231-win. Did not register something. I started a table with 10.8.1 4639 BGFX. Table, DMD and Backglass are showing. I can play it with my keyboard. I can close it with esc. Everything is closing. Backglass included. After that I tested the new server with my 10.8 Release and PinballY. Seems to have no problems as far as I tested. Does anyone know there the config of 8.1 is stored? I have to overwrite the keys with my gamepad buttons.. and I do not want to destroy anything... Edited February 13 by Tikimaster
Cliffy Posted February 13 Posted February 13 15 minutes ago, Tikimaster said: Does anyone know there the config of 8.1 is stored? In your windows user\appdata\roaming folder. Look for vpinballx.ini
Tikimaster Posted February 13 Author Posted February 13 6 minutes ago, Cliffy said: vpinballx.ini Yes. There is a Folder for 10.8 with an ini. I did not save anything in 10.8.1 - so I will have to check where the settings are written. No Clue how I can setup my pad as plunger.. I´ll check it next Week. Have to work this Weekend.
jarr3 Posted February 13 Posted February 13 (edited) Looking at the folder structure it seems to be a little confusion: If you go to %APPDATA%\VPinballX you will find: Directory C:\Users\<USERNAME>\AppData\Roaming\VPinballX 16.11.2025 19:31 <DIR> . 16.11.2025 19:38 <DIR> .. 04.02.2026 19:41 74 BAMViewSettings.xml 04.02.2026 19:41 <DIR> Cache 04.02.2026 19:41 <DIR> 10.8 04.02.2026 19:42 26.401 VPinballX.ini 10.8.0 stores it's configuration directly in the folder and 10.8.1 store in the folder "10.8". This sounds a little strange... but it means there will be a "10.9" when it is out and that not each "small" version jump will have it's own folder. Edited February 13 by jarr3
Cliffy Posted February 13 Posted February 13 Strange b2s server behaviour this morning with 2.1.6. Blood Machines. Testing as a friend said the music wasn't working for him. I loaded it in 10.8.0 and b2s server 2.1.6. Immediate popup screenres.txt not found. B2S not loading even after I make a screenres.txt as a copy of the tablename.res. However, pup pack mostly worked except for the scoring overlay, ie, just the main pupdmd window worked. Tested with 10.8.1 bgfx, b2s server 2.1.6 and boom the b2s loaded perfectly. Pup pack loaded completely. However, no music! So b2s server 2.1.6 is not yet fully compatible with 10.8.0 I'm afraid. Most tables seem to work ok with it but obviously not all
Cliffy Posted February 13 Posted February 13 11 minutes ago, jarr3 said: hmm B2S Server isn't doing anything with the music... 😕 yeah thats going to be a bgfx thing. Ok so I deleted the screenres.txt but left the tablename.res, ran blood machines again with 10.8.0 and now the b2s loads and all pup screens and music work perfectly. Strange! I guess running it in bgfx first somehow made the b2s server find the b2s which then allowed 10.8.0 to find it now as well.
jarr3 Posted February 13 Posted February 13 1 hour ago, Cliffy said: yeah thats going to be a bgfx thing. Ok so I deleted the screenres.txt but left the tablename.res, ran blood machines again with 10.8.0 and now the b2s loads and all pup screens and music work perfectly. Strange! I guess running it in bgfx first somehow made the b2s server find the b2s which then allowed 10.8.0 to find it now as well. Ok, if the problem with screenres files persist I will have to check what’s wrong… I added your right click back, maybe something went wrong?
Tengri Posted February 13 Posted February 13 (edited) 5 hours ago, jarr3 said: @Tengri sorry, missed that. But as I beleive you state there, neither the new b2s plugin nor the B2S Server work? Hi @jarr3 The feedback that I gave regarding the individual combinations of VPX + B2S Server, spread over multiple posts, might have become a bit confusing. To clarify: First of all, I’m super happy that the backglasses are now working with the current 10.8.1 BGFX builds. Thanks again for that! I reported the issue (whatever the root cause may be) regarding the backglass window/B2S Server not closing so that you (or whoever is responsible) are aware of it and have the chance to fix it for the community. I don’t expect a fix specifically for me. In case it helps, here is a summary of how the interaction between VPX and B2S Server has evolved over time: Setup: I’ve been using 10.8.1 BGFX 64-bit on Windows for months. I update to the latest Action Builds every few days and update B2S as required when new releases come out. Aside from a few occasional exceptions, backglasses were always displayed, and the B2S Server terminated correctly when exiting a table. The Change: A few days ago, I updated to the B2S Server version you linked in this thread (the one with B2S.Comserver.dll). During that process, I cleaned the registry (with the small included register application) and re-registered the DLLs (B2S.ComServer.dll + B2SBackglass.dll). Strangely, from that point on, no backglasses were displayed - not even when I reverted to the previous official release (v2.1.5.1) and an action build of VPX from a week before. I am quite meticulous and didn't change anything else in my configuration. We could investigate this further if you're interested. Current Status: With the latest release (2.1.6) and the current VPX action builds, backglasses are appearing again. However, in almost all cases, the B2S Server does not terminate when exiting VPX. I’ll gladly test if exiting with 'Q' instead of 'ESC' makes a difference. Since I haven't changed anything except for the B2S Server and the latest VPX builds, I assumed the termination issue might be a bug in the code. My configuration is completely unchanged and ran flawlessly for months in the setup described above. The phase where no backglasses were shown only was since two days ago, when testing your first linked build (the one with B2S.Comserver.dll). Edited February 13 by Tengri
jarr3 Posted February 13 Posted February 13 Hi @Tengri I will check once more what can have happened. I have decided to wait with the new B2S.ComServer.dll. The latest version of B2SBackglass.dll will have just one registration point (which has been wrong since years) And the registerapp should clean up the old wrong entries for the 2.1.6 release. I hope these measures will make it work for you again.
Cliffy Posted February 14 Posted February 14 (edited) 22 hours ago, jarr3 said: Ok, if the problem with screenres files persist I will have to check what’s wrong… I added your right click back, maybe something went wrong? still a problem with 2.1.6 I'm afraid. see pic. Now, just like yesterday I closed vpx 10.8.0 and then ran the same table with vpx 10.8.1 bgfx and the b2s loaded fine. Closed 10.8.1 bgfx, ran same table again with 10.8.0 and the b2s loaded without issue. This tells me that the 2.1.6 b2s server is setting a value somewhere when it's being started with vpx 10.8.1 bgfx that also then allows 10.8.0 to find the tablename.res. By the way, I tried 3 times with 10.8.0 fully closing each time and no b2s. It would only load in 10.8.0 after running once with bgfx. Edited February 14 by Cliffy
jarr3 Posted February 14 Posted February 14 (edited) Hi @Cliffy can you please activate debug log (B2SDebugLog) : https://github.com/vpinball/b2s-backglass/wiki/Settings#additional-registry-settings This is an example when I run : B2SScreen.New DONE FuzzyMatching FuzzyMatching END - Found matching filename B2SScreen.ReadB2SSettingsFromFile Start Search ScreenRes B2SScreen.ReadB2SSettingsFromFile Test Table (Original 1975).res B2SScreen.ReadB2SSettingsFromFile Test Table (Original 1975) (1).res B2SScreen.ReadB2SSettingsFromFile Test Table (Original 1975) (1)\ScreenRes.txt B2SScreen.ReadB2SSettingsFromFile Test ScreenRes.txt B2SScreen.ReadB2SSettingsFromFile Test D:\vPinball\B2SServer\ScreenRes.txt B2SScreen.ReadB2SSettingsFromFile Found ScreenRes D:\vPinball\B2SServer\ScreenRes.txt B2SScreen.ReadB2SSettingsFromFile Stop Search ScreenRes B2SScreen.ReadB2SSettingsFromFile A version #2 file DpiFactor =1,5 B2SScreen.ReadB2SSettingsFromFile Backglass Screen Size: 1,5,1,5->2560,2880 B2SScreen.ReadB2SSettingsFromFile BackglassSize: 100%,100%->2560,2880 Which means, you see each path it searches, I wonder which it tries on your side Edited February 14 by jarr3
Cliffy Posted February 14 Posted February 14 52 minutes ago, jarr3 said: Hi @Cliffy can you please activate debug log (B2SDebugLog) : https://github.com/vpinball/b2s-backglass/wiki/Settings#additional-registry-settings This is an example when I run : B2SScreen.New DONE FuzzyMatching FuzzyMatching END - Found matching filename B2SScreen.ReadB2SSettingsFromFile Start Search ScreenRes B2SScreen.ReadB2SSettingsFromFile Test Table (Original 1975).res B2SScreen.ReadB2SSettingsFromFile Test Table (Original 1975) (1).res B2SScreen.ReadB2SSettingsFromFile Test Table (Original 1975) (1)\ScreenRes.txt B2SScreen.ReadB2SSettingsFromFile Test ScreenRes.txt B2SScreen.ReadB2SSettingsFromFile Test D:\vPinball\B2SServer\ScreenRes.txt B2SScreen.ReadB2SSettingsFromFile Found ScreenRes D:\vPinball\B2SServer\ScreenRes.txt B2SScreen.ReadB2SSettingsFromFile Stop Search ScreenRes B2SScreen.ReadB2SSettingsFromFile A version #2 file DpiFactor =1,5 B2SScreen.ReadB2SSettingsFromFile Backglass Screen Size: 1,5,1,5->2560,2880 B2SScreen.ReadB2SSettingsFromFile BackglassSize: 100%,100%->2560,2880 Which means, you see each path it searches, I wonder which it tries on your side It is set to 1 in the registry, Richard, but I get no debug log.
jarr3 Posted February 14 Posted February 14 25 minutes ago, Cliffy said: It is set to 1 in the registry, Richard, but I get no debug log. What is your logpath set to in B2STableSettings.xml? <B2STableSettings> <HyperpinXMLFile>Unknown</HyperpinXMLFile> <ArePluginsOn>1</ArePluginsOn> <DefaultStartMode>2</DefaultStartMode> <LogPath>C:\vPinball\Log</LogPath> <---this one <IsLampsStateLogOn>0</IsLampsStateLogOn> That is where the logfile should be produced
Cliffy Posted February 14 Posted February 14 1 minute ago, jarr3 said: What is your logpath set to in B2STableSettings.xml? <B2STableSettings> <HyperpinXMLFile>Unknown</HyperpinXMLFile> <ArePluginsOn>1</ArePluginsOn> <DefaultStartMode>2</DefaultStartMode> <LogPath>C:\vPinball\Log</LogPath> <---this one <IsLampsStateLogOn>0</IsLampsStateLogOn> That is where the logfile should be produced ah. Mine shows no path; <LogPath> </LogPath>
jarr3 Posted February 14 Posted February 14 it needs a path (I beleive) you can create a folder use one which exists already
Cliffy Posted February 14 Posted February 14 2 minutes ago, jarr3 said: it needs a path (I beleive) you can create a folder use one which exists already ok fixed that so it logs in my b2s folder, E:\B2S. I get a log there now, thanks. Now I need to find a game that doesn't load the b2s and I'll post the log.
jarr3 Posted February 14 Posted February 14 Just now, Cliffy said: ok fixed that so it logs in my b2s folder, E:\B2S. I get a log there now, thanks. Now I need to find a game that doesn't load the b2s and I'll post the log. Great, I have posted a new release candidate where the reg app cleans the registry from unused COM registrations.
Cliffy Posted February 14 Posted February 14 Ok installed 2.1.6-391 and registered again. You're right, lots of old entries it wants to clean out! Will test the dickens out of it
Tengri Posted February 14 Posted February 14 Just a quick confirmation from my side: the backglass closes and the B2S Server terminates properly if I quit a table using 'Q' instead of 'ESC'. This suggests an unintentional change in the recent VPX build. I’ll file this as an issue on GitHub so the developers can determine if this behavior is intended. For context, I’ve had 'ESC' mapped to my cabinet's 'Exit' button since the beginning, and VPX has always closed the B2S Server correctly until now.
Cliffy Posted February 14 Posted February 14 13 minutes ago, Tengri said: Just a quick confirmation from my side: the backglass closes and the B2S Server terminates properly if I quit a table using 'Q' instead of 'ESC'. This suggests an unintentional change in the recent VPX build. I’ll file this as an issue on GitHub so the developers can determine if this behavior is intended. For context, I’ve had 'ESC' mapped to my cabinet's 'Exit' button since the beginning, and VPX has always closed the B2S Server correctly until now. By default Q is the quit game key (and all I've ever used) Escape brings up the resume/quit option menu. Of course any of these can be changed in the nudge/keys prefs
jarr3 Posted February 15 Posted February 15 11 hours ago, Tengri said: Just a quick confirmation from my side: the backglass closes and the B2S Server terminates properly if I quit a table using 'Q' instead of 'ESC'. This suggests an unintentional change in the recent VPX build. I’ll file this as an issue on GitHub so the developers can determine if this behavior is intended. For context, I’ve had 'ESC' mapped to my cabinet's 'Exit' button since the beginning, and VPX has always closed the B2S Server correctly until now. Great, thanks for the confirmation. I was a little nervous I had made a mistake... Well, yes VPX has a complete overhaul the last couple of months, so there is very likely something has happened there. VPX has to send a "STOP" command to B2S independent on which button you press. Now I only have to fix @Cliffy's problem with the screenres files and a final thing with the registry cleanup, and then we should be fine to release 2.1.6. Thanks to all testers!
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