scutters

For some reason after the launch of the Avatar table the log shows PinballX doesn't get as far as "Found Future Pinball window" which should be immediately after the launch (before table exit is pressed) It might be worth trying to set FPLoader to run in windows 8 compatibility mode and confirm other FP settings are also as suggested in Future Pinball and BAM Mega Guide by TerryRed - Future Pinball - Virtual Pinball Universe (vpuniverse.com) If they're all set then i'm not sure why you'd get the issue but only occasionally

It might be worth adding /arcaderender to your FP launch parameters, so they change to something like; /open "[TABLEPATH]\[TABLEFILE]" /play /exit /arcaderender /STAYINRAM If that doesn't help can you let us know how often the hang occurs?, every 3 table launches etc. Thanks.

Good point Mike, i'd forgotten that. Maybe without the -minimized flag VP not closing meant B2S didn't close either and that was why PinballX had an issue and hung with the 'use B2S in front end' option (trying to create another B2S instance). Definitely worth having that flag in the launch parameters anyway!

Interesting that that setting suddenly caused PinballX to hang. Did you update the B2S server app recently (and maybe moved it to a new location)?. Changing that setting will probably mean you now to need record or download backglass media for PinballX to use in the front end. Not sure what you mean. Is it the Visual Pinball editor you see on screen 2 during the table loading? If so then open Visual Pinball outside PinballX and drag the editor window from screen 2 to screen 1 then close it, it should open on screen 1 the next time then but may still be visible.. So something else you could do instead is just edit your Visual Pinball launch parameters from; /play -"[TABLEPATH]\[TABLEFILE]" to -minimized /play -"[TABLEPATH]\[TABLEFILE]" So that the editor window is minimised when launching a game from PinballX

@Mike Iacaruso On top of the other Mikes excellent suggestions please also try setting the 'Use Direct B2S in front end' to No in display settings. All of those settings will be easy to re-enable later if needed, so i'd suggest disabling them all and retesting.. if successful re-enable one at a time to see which is causing the issue, if unsuccessful then please re-attach new log and ini files after the test, and let us know if you did any software (or even hardware) changes when the problem first appeared. @marcusvpcardoso Please create a new thread for your issue attaching your pinballx.ini and log.txt files and also more info on your issue (is the hang on exit only with Future Pinball, but other emulators exit ok?)

Jack Sparrow (Original 2023) for @marty02's new table;

Thanks for the update with the fix. It makes sense as the plugin works from the relative position of the full desktop (all screens), so would be affected by the screens positions being changed in windows.

I do not own Retro Pinball but it looks like a request was made some time ago to add direct table launch - Cabinet support :: Retro Pinball General Discussions (steamcommunity.com). I'd suggest commenting in that thread and seeing if there is a response from the author (unless someone else who has the game comments here with some form of working ahk file).

My guess is that it's the power/battery saving laptop functions affecting that. Try going into windows 'graphics settings' and setting PinballX to run as high performance (set to use the rtx gpu) and see if that changes anything. If you still get black videos then maybe it's a lav config setting somewhere, but if that fixes it then it's probably an intel gpu driver issue. No idea about the flash engine error.

Updated to V1.4 New feature allows the placing of the animation on a larger background image (can be transparent) by x,y co-ordinates, useful for system underlays, overlays etc. E.g. (on top of non transparent image for clarity)

@gokwh as well as the files requested by Mike can you let us know if you updated anything else at the same time as Pinballx (VPX, Vpinmame, freezy etc?), and also the previously working version number of pinballx (if known)

I think all the main front ends recommend having the playfield screen as screen 1 and have it as the leftmost screen and primary screen in the display settings I've never tried, but the screen number is probably less important than it being the primary screen and also being the leftmost screen. I'd try dragging screen 2 the left of screen 1 in display settings. But your choice..

If you've run setdmd and set the vpiinmame default position value then you only need to run it once (unless you change your screen order). As it's a set and forget thing with setdmd why have PinballX position the DMD every time you start a SS table?

I wouldn't put this down a bug in PinballX, it just windows being windows and making a mess of screen numbers. I use 6 screens and nvidia and windows disagree about the screen numbers so what chance does pbx have?. You have a few options; Manually edit the pinballx.ini file to try screen ids > 5 Set the screen id the same as the backglass for the DMD and use the DMD x, y offset values as a relative position from the top left of the backglass Try and clean the windows registry entries for attached screens as described here - https://www.vpforums.org/index.php?showtopic=49405&p=501605 Personally, option 3 would be last resort and only after backing up those registry entries.

@Wimpie If you want to turn off the auto position of DMD in PinballX because it's not working for you and your pinmame registry positions all need updating then SetDMD is probably worth a look, https://www.pinballbulbs.com/files/setdmd.html. It's an old program but should do the trick for setting default position for new roms and also update any existing saved positions. Do make a backup of the vpm registry key first though as it suggests in the notes though (just in case).

Do you have any compatibility settings set for PinballX.exe (via right click->properties,->compatibility, e.g. compatibility mode, run as admin etc, )?

Attachment in first post updated to V2.2. Adds support for FlexDMD V1.9.

This is in the launch before options? When you click the 3 dots for the launch before executable and the dialogue opened did you click the drop down filter and change 'executable files (*.exe)' to 'batch files (*.bat)'? Best to attach your pinballx.ini and log.txt files in case it's something else and we have our wires crossed.

Mikes a busy guy so might not have time to have had a look yet. As you've had some success with Pinaffinity running then maybe you could play around there... As you don't want Pinaffinity running all the time you could launch and close pinaffinity with FX3 tables only via settings, or start PinballX and see what CPU cores are in use and try changing them there before launching FX3 to see if that changes anything (if it does then you could even create a shortcut for pinballx with cpu affinity set - https://answers.microsoft.com/en-us/windows/forum/all/how-to-permanently-set-priority-affinity-with/e7fe5a46-37c8-4277-9d27-60b537c4780a) Or you could just have PinAffinity running all the time . Sorry, i'm out of other ideas.

I don't have FP installed so might not be much help, but if you have a bat file that opens dmdext you could probably add that in the 'launch before' section for FP in settings.exe?

@MAYAman Search your PC drive for PinballX.exe. This will confirm if you have two instances installed and where (just in case you did install to a new location instead of upgrading the current install as Mike suggested). Let us know what you find, and please attach the \log\log.txt and \config\pinballx.ini files from any locations PinballX is installed. If you do have only one install and somehow the ini/config was corrupted during the upgrade then all the media files etc should still be in place (again as Mike said), so you may be able to just add & configure whatever systems you had before and then use the 'auto add' tables function to quickly recreate the system xml/database files if they were lost as well (which seems unlikely).

As far as i know based on log files etc; Sequential PinballX uses two pass (at least for ffmpeg capture). Pbx recorder can use real time or two pass in a later version (https://forums.gameex.com/forums/topic/28516-pbx-recorder-captures-playfield-backglass-and-dmd-videos-and-images/?do=findComment&comment=194355) Would need a change to PinballX to use ddagrab with ffmpeg for FP (and users to update their ffmpeg copies), probably a feature request. Think the shadowplay option is actually for all screens but probably only mentions playfield as that is (was) the problematic screen to capture for opengl apps with ffmpeg, never loaded geforce experience on the cab so don't know for sure ( @Mike_da_Spike can probably answer) So long as the default screenres.txt defines the full backglass area etc to match PinballX screens then i don't think the .res files will matter, if a B2S uses only part of a screen due to the .res file then pbxrecorder would still capture the full area - and that it was you'd want to avoid it getting stretched when displayed in PinballX. But the screenres.txt file could be located somewhere other then the Tables folder now. Probably needs @Tom Speirs to confirm most of what i've said above though!

In settings.exe make sure you have the launch before and after set to no for whatever systems you're using where the executable is Notepad.exe;

Interesting. Thanks for the videos. I'm still not sure if the CPU use is the cause of the focus issue, or the other way round. If on the first launch of PinballX you launch a second table does that then work correctly, or does it need a second launch of PinballX?

I think it is the [Internal] lastselected value in the ini file as you suspected, but if that entry isn't present then it's random. The lastselected value will be indicate the system (and table if applicable) you last selected before exiting PinballX.