scutters

If the screen locations are correct in PinballX, and the issue is only with the backglass after launching a table then that points to an issue with the screenres.txt file (changing monitors around messes with windows id's). From https://www.vpforums.org/index.php?app=tutorials&article=136, this is what the screenres files contents mean; 1920 <-- Playfield screen X resolution (width) 1080 <-- Playfield screen Y resolution (height) 1280 <-- Backglass screen X resolution (width) 1024 <-- Backglass screen Y resolution(height) 2 <-- Display number for the backglass monitor 0 <-- offset for the backglass on the selected display (normally left at 0) 0 <-- offset for the backglass on the selected display (normally left at 0) 600 <-- Width of the DMD area in pixls 200 <-- Height of the DMD area in pixels 1280 <-- X position of the DMD area relative to the upper left corner of the backglass screen 0 <-- Y position of the DMD area relative to the upper left corner of the backglass screen 0 <-- Y-flip, flips the LED display upside down The bottom few entries aren't relevant to you as you have a 2 screen setup without a dedicated DMD. The 3rd,4th and 5th entries are the ones you need to check / change (mainly the display number - try 1 first, but the backglass resolution set in PinballX is 1280x1024 but 1366x768 in your screenres file).

For anyone having problems using pbxrecorder after updating the B2S Backglass program to the newest version please see this comment about removing comments from screenres.txt - https://www.vpforums.org/index.php?showtopic=33552&p=512834 Sounds like the pbxrecorder ahk script will need updating to ignore the comment lines as a proper fix

You wouldn't be running a 'flipped' orientation in windows would you?. Think i had similar issues with my old screen before changing it and swapping the screens orientation round at the same time. Can you post your screenres.txt and pbxrecorder log file in the pbxrecorder thread?, might be something someone can fix in the ahk script.

Apparently the latest version of ffmpeg grabs the screen at a lower level, so should now be able to record future pinball media too. I don't have FP loaded anymore, but if someone wants to try it then please let us know / confirm if it works ok with pbxrecorder (you will need to amend the ahk script to pick up FP systems as well as VP)

@Schreibi34Do you run VPX in exclusive fullscreen, and if so if you turn that off do does GOT then launch without any focus issues (as it does for @grunger)? If i had the issue i'd be tempted to play around with the GOT table script too, maybe move the DMD_Init call to the top of the Table1_Init (to try force the flex dmd to initialise before the table). That might help.

Best bet would be vpforums I think i read somewhere (probably on vpforums ) that vpinmame has some issues still in 64bit, so best to stick to 32bit for now for Visual Pinball related stuff.

Flagged as resolved already so i guess the answer was found (in the documentation? ), and yes there are a lot of options to do what you want. I'd agree active filters are probably the easiest and most flexible (especially if using database manager to build the filters - see bottom of this post https://forums.gameex.com/forums/topic/23840-app-pinballx-database-manager-2211220-supports-touch-play-and-pbx-w7vista-version-as-well/?do=findComment&comment=201644)

Any chance you have a button stuck? that could cause that issue for key and joystick input screens if you have joystick to keyboard mapping software running.

V2.1 Released & attachment updated in 1st post with changes as shown in change log. Thanks @Mike_da_Spike for keeping me busy!

@Tom SpeirsThis would be for plugin code, something like Event_MenuShown and Event_MenuExit would be useful. The nearest i've found is using the Event_Input and checking the PinballXStatus flag but there's issues with that as the flag doesn't change while the menu is exiting (it has changed on the next input event), and the menu can also exit without user input on attract mode start.

I guess you killed PinballX in taskmanager then rather than exiting out?. As Mike says, the mouse is restored during PinballX exit.

@dielated the windows feature to turn off if you don't have a low disk space issue is 'storage sense'. That should resolve the wheel issue. For the exit game issue can you post a screenshot of your visual pinball key / button config screen and let us know what button (number) you use to exit a game. Also, is it only some games that you can't exit out of, but some exit ok?

You're still on a very old version of PinballX Try installing the latest version (even if just to new a different directory just to test)

I think you know what we're going to suggest - please update to the latest version of PinballX, a lot has happened between V1.72 and V5.55! Then attach your config.ini and log.txt files. The black screens you seen may be pinballx (pinballx screens change to black on a table launch) and the actual issue could be with the VPX setup or the launch parameters in PinballX but we need to see those files.

Freezys stuff can output to a real or virtual dmd (it can be enabled for 'rom' tables in vpinmame settings by to 'use external dmd', in which case you'd probably then also disable the default vpinmame dmd 'show dmd display window' option unless you want two dmd displays). Flex DMD actually uses freezys dmddevice to output to a display (real or virtual). Ultra DMD uses the the alternate XDMD libraries to display to a DMD (again real or virtual). P-ROC is then another entirely different thing again, not sure if that renders on real dmds or just on virtual dmds. It's a strange one alright.. i have both tables and can launch into VPX EFS from PinballX with no problems on a 3 screen setup (DMD is virtual). My guess is it's down to how the tables displays are initialised in the script and differences in cpu speed on different systems affecting the order of when each screen is actually rendered, but i have no way of testing that. I guess you tried the 'minimize' flag in the launch parameters without success before moving on to set up an alternate system for those two tables?

@bushav Can you try with File Matching disabled in PinballX (under General Settings). Just wondering if that could be a factor somehow after having issues with the IM virtual time table previously (e.g. corrupt historic file or entry and being incorrectly name matched to the new Legacy of the Beast table ). If that doesn't work can your attach your pinballx\databases\statistics.ini file as well (maybe there's an issue with that file for an IM table)

Hopefully it's that simple! Hah, yes that was me with same issue & fix. What were those VPW guys thinking?, the amateurs!!! . It is a great update though, i really didn't think the original needed any updates until i played the new one

Could be windows updates turned defender back on (if you disabled it rather than adding exceptions) or just updated some other dependency. Also, make sure you read https://vpuniverse.com/forums/topic/7384-4-gb-patch-for-future-pinball-and-bam-a-must-have/, especially the bit about recent windows updates needing FPLoader to run under windows 8 compatibility.

Please attach your pinballx.ini and log.txt files (log file after launching the GOT table). You shouldn't get the focus issue with VPX set to fullscreen exclusive so not sure why you are. Is it always the VPX editor window that has focus? - if so make sure you have the '-minimized' flag in the PinballX VP launch parameters, that should minimise the editor window when launching tables.

V1.0.7 posted - now includes all the above and one for GOT (and also available on the FTP!)

Make sure you tried changing the backglass width/height to tiny values with B2S set to bringtofront, that should work. If that's not the issue then please describe what you see on the DMD when the B2S is running but not shown there, is it the desktop or a black screen.

Ahh ok, the problem is there's three screens on the backglass, blank pinballx backgalss window, B2S and pup, and two on the DMD with blank pinballx dmd window and b2s dmd. Getting the ordering of those screens right is the issue. Bit of a strange table set up using B2S DMD for the scoring (rather than having that in the pup pack), but i think there may be a solution for you.. Are you familiar with '.res' files for individual tables (see ScreenRes Files section https://github.com/vpinball/b2s-backglass/)?, you could try a copy of your screenres.txt file in a .res file named for The Dude table, but then change the Backglass Screen resolution width/height to something really small so it doesn't obscure the puppack and leave the B2S setting at BringToFront or Standard.

I checked the release notes for B2S v1.4.0; What's New in Version 1.4.0 (See full changelog) - Add additional setting FormToBack complementing FormToFront. Now three states available: 1. "Standard" setting (both FormToBack and FormToFront turned off) is now as it was in 1.3.0.6. -> formDMD isn't controlled by the FormToFront/Back setting 2. FormToFront sets the flag Form.TopMost = True -> cannot get any other window on top 3. FormToBack, forces the forms to the back and ignores any try to get them come forward -> Windows stay in back. The B2S Server is not available in the taskbar anymore. (I should have done that before!) The bits of interest are; formDMD not controlled by front/back setting and the B2S server not available in taskbar anymore with formtoback set (so no alt+tab) From that it looks like you have FormToBack set (?), can you try with 'standard' & 'formtofront' in B2SServer and let us know what happens then when you restart the table from pbx (i guess formtofront will hide the pup pack, but standard might work) More info in Backglass Settings here - GitHub - vpinball/b2s-backglass: B2S Backglass Server and Designer for use with Visual Pinball

DBM can do a whole load of stuff! Make sure you check the pdf's in the install location folder, lots of info from Mike there (he just loves the documentation side of things )

Ok, so the cmd line works when launched from an admin cmd prompt, although you can't see the B2S running with ALT+TAB it is working. So the question now is, is the B2S running when you launch the table from PinballX but it's hidden (and you can't see it with ALT+TAB) or is it not launching at all - i think you'd have to check the processes in task manager to confirm that. If the B2S doesn't start with PinballX normally then does it start if you set PinballX to run as administrator (under compatibility settings)? - in which case the issue is likely to be UAC related somewhere in the PinballX->VPX->Pup->B2S call stack.