scutters

Looks like the main delay is before VPX is launched, after Set Plugin data; 22:04:19.50 03/09/2024: Launch System 22:04:19.50 03/09/2024: Hide Backglass 22:04:19.50 03/09/2024: Waiting for threads 22:04:19.60 03/09/2024: Disposing display 22:04:19.68 03/09/2024: Set Plugin data 22:05:20.36 03/09/2024: Writing ScreenRes.txt 22:05:20.37 03/09/2024: C:\Visual Pinball\VPinballX.exe /play -"C:\Visual Pinball\Tables\Spider_man.vpx" 22:05:20.42 03/09/2024: C:\PinballX\vpauto.exe 22:05:28.74 03/09/2024: Visual Pinball Player window foreground: 8 22:05:29.47 03/09/2024: Found PinMAME ROM: sman_261 As no plugins are enabled it could be loading media or playfield image creation related with some sort of timeout in PinballX(?) Make sure LAV codecs are installed as a first step - https://forums.gameex.com/forums/files/file/2451-lav-video-codecs/ Let us know if that helps.

Not sure, it might be that pinballx can see & use the controller but the settings app for whatever reason crashes out (in which case we might be able to set the joycodes manually in the ini file as a workaround while Tom investigates).. Just hope to see some clues in the log files when they arrive!

@fAthAwg13 as well as attaching the usual \log\pinballx log.txt and \config\pinballx.ini files please also attach the log\SetupWizard.log file after attempting to set to a button.

From the video (https://forums.gameex.com/forums/topic/30107-resolved-no-playfield/) the blue and yellow bars on each side are present on all table playfields in PinballX but not on the loading screen (using a still image of the playfield video). So i think it must be from an overlay or underlay being used in PinballX. @duv67 Check what underlays and overlays you have in \PinballX\Media\System Underlays and \PinballX\Media\System Overlays. Open them in paint and hopefully one of them has a blue and a yellow bar on the sides and is the cause.

Can you post a picture or video of the problem? Not sure i understand the issue from the description alone. Is it playfield videos are missing, or is it just a focus problem after launching VPX? Make sure you installed lav codecs on the new pc anyway - https://forums.gameex.com/forums/files/file/2451-lav-video-codecs/

Make sure you're set up as noted here - https://github.com/freezy/dmd-extensions?tab=readme-ov-file#pinball-fx And then check if this is the same issue as noted here - https://github.com/freezy/dmd-extensions/issues/485, if it is then keep an eye on that for updates / fix. Sorry, not something that can be fixed in PinballX if the issue lies with dmddevice & Pinball FX

I think you may be able to achieve what you want by using Active Filters (1) and Custom Groups (2) Are you using PinballX Database Manager?.. If you are then have a look at @Mike_da_Spike's excellent documentation that comes with it (the question mark icon in the top right of the main screen will open it), it goes into quite a lot of detail (and would be a very long post if i just copied and pasted it) See sections 5.3.1.1 for Filters and 4.1.5 for Groups. Let us know if you need more help, but i suspect you may need to be a little creative with your use of a Filter (maybe setting a custom Type on each table you want to appear)

You quoted it in your comment!!! 🤣

Agree. If hide mouse is set to true and PinballX crashes or the system is shut down before closing PinballX the easiest way to restore the pointer is to run PinballX again and exit out cleanly. Probably won't work for @rickh though as it appears the unhide mouse function on PinballX exit isn't restoring the mouse in his case.

You still have HidePinMAME=True set in your ini file. Did you ever try changing it to False as suggested in that thread? If you did and it didn't work then if you want to pursue that please open a new thread for it. Regarding the mouse issue if you're still interested in addressing that as well, the log did show that the mouse should have been restored on exit with no nothing logged to indicate a problem in doing so. Can you restore your mouse pointer via the control panel and then try PinballX again with the Hide Mouse setting set to False as suggested by Tom.. then attach new copies of your ini and log files if the cursor still disappears after running PinballX.

That probably is linked to Program Files install location and UAC

Your ini file shows quit and exit emulator mapped to keycode 70 (f key), not keycode 27 (ESC key) so i'm a bit confused. Are you using keyboard or buttons? Log also shows 'PinballX - Version 4.13 x64' which is quite old now and you should update.

This does kind of exist already (just not widely used) Place the video in your PinballX\Media\Tutorial Videos folder, then you should have a 'Tutorial' option in the menu when you launch a game (or pause it). The menu option won't appear for tables that don't have a matching tutorial video. There are also some existing videos on the FTP https://ftpbrowse.gameex.com/-PinballX-/Media/Tutorial Videos/

"PinballX - Version 4.77" Please update PinballX, the latest version is V6.07. If problem persists after that it may just be a focus issue(?). Press ALT+TAB after launch and make sure FX3 has focus.

Think it must have been the LAV codecs, that could have caused the issue as described.

It might be worth changing the visual pinball launch parameters in PinballX to; -DisableTrueFullScreen -minimized -play "[TABLEPATH]\[TABLEFILE]" .. so that it matches the default popper parameters. As you don't get the issue with the current launch parameters from a command line it shouldn't really change anything as the command line is doing exactly the same as PinballX is now (so i don't know what the issue/difference is). Alternative may just have be to save the table with 10.7 and then use the alternate exe flag in PinballX to launch with 10.7 for this table.

If the cmd prompt is now ok using the same launch parameters as Pinballx (and pretty much the same as popper from what i can tell from this post https://vpuniverse.com/forums/topic/9212-pinup-popper-will-no-longer-open-vpx-since-check-for-valid-command-line-parameters-1942-was-released-solved/?do=findComment&comment=74876) then it may also be worth checking you haven't at some time enabled some windows compatibility mode for the PinballX executable as they can have some strange side effects.

Agree. There must be difference in the launch parameters, possibly using a different VPX executable (the DX, or a 10.7 version)?

Might not be the issue but your log shows the table launch as; 13:44:56.45 7/7/2024: C:\Visual Pinball\C:\Visual Pinball\VPinballX_GL64.exe /play -"C:\Visual Pinball\Tables\Batman 66 (Stern 2016).vpx" Which has 'C:\Visual Pinball\' twice. This is because you have included the path to Visual Pinball in the executable entry. Can you change that to include the executable name only and try again (go to settings.exe, Visual Pinball system and set the executable entry to just 'VPinballX_GL64.exe') If the issue is still present please open a cmd prompt and paste this line in (which is the same as PinballX launching the table), does the issue exist then? "C:\Visual Pinball\VPinballX_GL64.exe" /play -"C:\Visual Pinball\Tables\Batman 66 (Stern 2016).vpx"

Flash is used to display old flash format flyers, so probably not a factor in your issue. @Mike_da_Spikedid make some notes a while back about to correct it though https://forums.gameex.com/forums/topic/27599-guidehow-to-remove-flashocx/ Looking at your logs there doesn't seem to be much of a pattern to the issue - Creature from the Black Lagoon has launched and exited ok in one log but failed in another; Ok 23:28:06.70 03/07/2024: C:\Visual Pinball\VPX 3D\VPinballX_GL64.exe /play -"C:\Visual Pinball\Tables\3D Tables\Creature From The Black Lagoon (Bally 1992).vpx" -minimized -ini "C:\Users\Pinball\AppData\Roaming\VPinballX\VPX3D.ini" 23:28:06.75 03/07/2024: C:\PinballX\vpauto.exe 23:28:15.09 03/07/2024: Visual Pinball Player window foreground: 8 23:28:30.45 03/07/2024: Exit System Control Pressed Fail 08:55:02.75 04/07/2024: C:\Visual Pinball\VPX 3D\VPinballX_GL64.exe /play -"C:\Visual Pinball\Tables\3D Tables\Creature From The Black Lagoon (Bally 1992).vpx" -minimized -ini "C:\Users\Pinball\AppData\Roaming\VPinballX\VPX3D.ini" 08:55:02.76 04/07/2024: C:\PinballX\vpauto.exe So for some reason PinballX isn't recognising that VPX has successfully launched when you see the issue (as there's no 'Visual Pinball Player window foreground' line in the log), and nor does that monitoring process timeout either (no 'Visual Pinball Foreground Timout' message in the log) - but only sometimes(?) Can you try something Mike suggested, for the VPX 3D system in settings change the system type from 'Visual Pinball' to 'Custom' just as a test (which should stop PinballX checking for the Visual Pinball windows becoming active), and let us know if that makes any difference (and attach a new log copy!). Also, please confirm that you have exceptions set in antivirus / defender for anything & everything Pinball related and let us know general system health status (plenty of free space on C drive, no other crashes or random error messages popping up, games always launch ok outside PinballX etc)

Looks like you're on PinballX V6.02 so you may as well update to the latest version. After the update can you post pinballx log files after the issue for the regular VP system for Big Bang Bar and for the 3D system so they can be compared (might be different issues). Ideally open a 'working' table in the VP system that exits normally before opening and attempting to exit Big Bang Bar so that is in the log too. When the hang occurs, is VPX still open or does it fully exit (with no left over visual pinball processes in task manager [details tab])?

Alternate Capcom logo added to pack and FTP (thanks for the real dmd capture @Mike_da_Spike)

@keefer99 The latest version of PinballX will still run on win7 using .net 4 (https://forums.gameex.com/forums/topic/28684-news-pinballx-590/)

In PinballX the Backglass and DMD are displayed on the same screen only after updating PinballX? Please attach your pinballx\config\pinballx.ini and pinballx\log\log.txt files

@robertms Thanks for that. Mike has experimented a bit and may have found the cause. Under accessibility settings have you changed the Text Size from the default 100%? Can you check with the setting at 100% to confirm on your setup... if that's it then we can fix it