Jump to content

Recommended Posts

Posted

First time poster here so please treat me like the noob I am.

I have an Atgames Legends Pinball Micro with a VIBS board (so a two screen setup) that I've spent quite a bit of time setting up with PinUp Popper and Visual Pinball X and with some finagling I have managed to get everything to work with one exception; the B2S backglass.

From my admittedly limited understanding, as long as the B2S file is in the same folder as the table and are named the same as the table, it should automatically work when the table is launched, at least that's what I can see from the tutorials I've watched. However the backglass screen only shows the DMD, so I'm obviously missing something. 

I can start the B2S server manually and choose a backglass, but then it only shows the backglass file I've selected regardless of anything else.

Obviously I'm doing something wrong but I'm not able to figure out exactly what. Heck, for all I know I might be posting this in the wrong forum category!

Posted (edited)

@deadmanworkingThank you for taking the time to help me!

So yes, I did register the B2S server, though the name was B2SBackglassServerRegisterApp, I suppose it's the same one? Anyway, it came with the PinUp Popper installer and was already located in the Tables folder. 

Since then I figured that I might have an old or incorrect version so I downloaded and installed the latest version of B2S, however that really screwed with my install. With this latest version I always get an error message when loading a table saying 'No script associated with this object' or something very close to that and the table only seem to half load. I can see the table, and it makes some sounds and reacts to some button presses. For instance I can nudge the table but not use the flippers and the table can't be played.

Removing and reinstalling Pin Up Popper didn't help, instead I had to go into the windows registry and remove all mentions of B2S. I tried reinstalling the B2S that came with Pin Up Popper instead of the latest version but the same thing happens again. So I'm basically worse off compared to how I started.

Edited by Macross_VF1
Posted

Also, make sure after downloading the B2S server update zip file to right click on it and select Unblock. Then when installing double check that you are again installing into Tables directory and not B2S subdirectory. And after finishing the install re-register B2SBackglassServerRegisterApp.exe. 

Posted

I used PinUp Popper Baller installer 2501 to get VPX version 10.8.0 beta, PinMAME 3.5, and what I think is B2S 2.0.1. I've also managed remove the error message when launching a table by doing a full reinstall, ie removing everything related to B2S, VPX, MAME, the lot and then doing a completely fresh install.

 

After that I installed B2S 2.1.2 and registered it since 2.1.3 was the one that caused the error messages to begin with. No new error messages though the B2S backglasses still doesn't appear automatically. I'm back to square one which admittedly is an improvement.

 

Posted

OK so you are not on the latest VPX and Vpinmame versions. I would recommend you update them to the latest (January) versions (i.e. 10.8 final 2051 and VpinMame 3.6) by following this guide.

Always make sure to right-click each file after downloading, select properties and Unblock. And after installing do a check also on B2SBackglassServer.dll and B2SBackglassServerRegisterApp.exe to see that they are not blocked. 

Also did you use B2S_ScreenResIdentifier.exe to properly define the size and placement of the backglass? What does you Screenres.txt have in it?

Posted

I installed the latest versions of everything per your recommendation, unblocked the files like you instructed and ran ScreenResIdentifier. No Improvement. Then I figured I might as well unblock just about EVERY file connected to B2S and that finally solved the problem! Only unblocking B2SBackglassServer.dll and B2SBackglassServerRegisterApp.exe was not enough it would seem. 

Anyway, great success! My remaining problems are now that some tables doesn't launch, launch with missing graphics or launch rotated 90 degrees wrong, but that does seem to be more connected to the tables themselves than anything else. Thank you so much for the help!

Posted

And I've already run into a new problem, though this one I suspect might be easier to fix. The backglass for some tables completely obscures the DMD, like the backglass layer has been given priority over the DMD. I can briefly see the DMD when the table is loaded and when quitting the table. It also only seems to happen whenever the backglass file is described as a fullDMD.

Posted
46 minutes ago, Macross_VF1 said:

And I've already run into a new problem, though this one I suspect might be easier to fix. The backglass for some tables completely obscures the DMD, like the backglass layer has been given priority over the DMD. I can briefly see the DMD when the table is loaded and when quitting the table. It also only seems to happen whenever the backglass file is described as a fullDMD.

is b2s dmd set to visible in the settings window?

b2s-2.1.3-settings.jpg

Posted

@Cliffy It is indeed set to visible but no amount of finagling with the settings change the situation. And the Virtual DMD is there, if I press Alt Tab to see all my active windows I can find it. If I click on it, the window pops up in the correct position but if I leave it like that it seems to take priority over everything else and I can't control the table and if I dare to press the mouse pointer anywhere else but the Virtual DMD window, it goes back in the back ground again.

Posted
1 hour ago, Macross_VF1 said:

@Cliffy It is indeed set to visible but no amount of finagling with the settings change the situation. And the Virtual DMD is there, if I press Alt Tab to see all my active windows I can find it. If I click on it, the window pops up in the correct position but if I leave it like that it seems to take priority over everything else and I can't control the table and if I dare to press the mouse pointer anywhere else but the Virtual DMD window, it goes back in the back ground again.

Which vpx are you running? For a cabinet you should be running the DX version in exclusive full screen mode or the GL version. 

In vpinmame you should also have cabinet mode checked in the F1 menu.

You might try using external dmd by Freezy or Luck1 too.  External dmd allows use of color, higher resolution, more flexibility

Posted

@Cliffy I've spent far too much time trying to figure out this stuff and despite my best efforts it doesn't work consistently. And I'm mostly sure that I am the problem, that I just don't know quite enough about this to fix it. So for now I have figured out a workaround, anything associated with B2S have been disabled and I have instead set up the backglass screen to exclusively work as a DMD. I might come back and ask for more help in the future when I have a dedicated PC for my cabinet, as right now I have connected my everyday computer to the cabinet, and I wouldn't at all be surprised if it causes at least some conflicts. Anyway, thank you for the help!

Posted

@Macross_VF1 if you're having troubles with backglass obscuring the DMD I would suggest an easy fix, make your screenres so that the B2S only takes 4/5 of the backglass monitor and the DMD the bottom 1/5, so there is no overlap. 

On a 1280x1024 resolution that would mean assigning the B2S size 1280x800 in screenres.txt (3rd and 4th line) and place the DMD centered in the bottom area (size always in multiples of 128x32, so in this 768x192 would fit best). 

Then right click the B2S backglass and hide the grille. This looks good on all dmd based tables (and for older 70ies/80ies table you just use the full area of the backglass monitor) 

Also you could use Chatgpt or Gemini to guide you through these kind of steps, they are pretty solid if you describe your setup and problem in detail. 

  • 2 months later...
  • 1 month later...
Posted

yess same issue here!!!
everything working fine with b2s backglass, after install pin up sytem and everything is worng. Table is working with out b2s backglass.
Reinstall pinball x everything is working again:::!!!!!
pin up and b2s backglass is not working togeter ::))))

  • 2 weeks later...
Posted (edited)

Also having the same kind of issue, and also as much of a noob as the OP. 😆 I'm just starting my VPX journey and while it's early days, it's been fine until today. Here's my situation:

 

- Running a two-screen setup where my monitor is the playfield and the PC (a laptop) is the back glass/DMD. Eventually, that'll be arranged inside a small-ish cabinet, but walk before you can run!

- I installed PinUp Popper and followed the instructions. Got to the point where I had a bunch of tables running (playfield on the monitor and the DMD on laptop screen), but no backglass was showing because... well, I hadn't set it up.

- Today, I set up B2S. PUP had put all the files into the Tables folder, but the B2S wiki says to set it up in its own folder? I did that, but now I have two sets of files. I ran the server register, that worked (although it was asking about removing old files). Now, I get a backglass image.

- However! Lots of things wrong. The backglass appears on the wrong screen on boot and covers the playfield, taking priority. Forcing it temporarily to the other screen (shift+Win+right) covers up the DMD, and even though I can bring the DMD to the front, it reverts as soon as go back to the playfield. Even worse though, despite having multiple backglass files correctly named and placed, B2S server only shows one (Turtles 1991) regardless of which table I start up. Also, since setting up B2S, the 1 key no longer registers as Start so I can't play a table or save any settings when moving POV stuff around in VPX. It's weird.

 

I've run the setup software and put everything in the right place, and saved that as global settings (will do game-specific ones down the road). Problems persist. Same goes for the PUP screen setup, that's done too, still no change. I have no clue what I'm doing wrong, but that's certainly as much as me being new to all this as it is the software. I might try a wipe and reinstall, see if I can solve the problem, but surely it can't be that difficult or require that drastic an action... can it?

Edited by MartyBarty

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...