scutters

@JimmyCoupe If you get chance please attach the pinballx.ini file as well after those changes. The settings in there (as text) will be easier to copy from for other users.

No problem. The one thing it won't do is show the reverse of the spinning logo if you use a background image where the non transparent area is smaller than the spinning logos diameter. That would be tricky to do and involve adding a new layer to the processing, or checking pixel argb values before drawing the spinning logo on top of them (or not for the logo 'reverse').. or something like that, and i'd guess the image processing would be a lot slower as a result too.

Yeah, it's a bit tricky to get the sizing right for the background.. but the 'Overlay apng in image' can just about do it! I resized and changed the centring of the logo image to; And then used these settings; (Note - the background / logo image would need resizing again if using the Tarcisio overlay - but you can try with different sizes [add more transparent border / shrink the logo down] and then use the frame images in the app Temp folder to dial in the exact size & location you want, it's maybe not ideal but it will work)

Can you give more info... you might be able to do something like that now, select an image to spin that has transparency, don't select a background colour, and then select 'Overlay apng in image' (set at pos 0,0 and use an image sized at 1000x1000) - is that what you mean, or did you want the background image sphere'ised as well but just not rotating?

https://store.steampowered.com/app/287900/Pro_Pinball_Ultra/ as well? (i don't own it)

Thanks. It is indeed a bug!, looks the format of dates from vpsd has changed at some point causing the issue (no idea when). Will be fixed in the next release.

Might be worth messaging @PcTeknic, he hasn't been on for a bit but he might see an email notification for a msg and reupload?

Also let us know what version of VPX you're using (DX or GL). GL is slow to exit for me but i think that's because i installed ReShade against the DX version of VPX and somehow that also affects the GL version (so i don't use GL version anymore).

The Indy close; 13:24:25.92 2/15/2025: Exit System Control Pressed 13:24:26.25 2/15/2025: Found Visual Pinball editor window 13:24:26.59 2/15/2025: Process Closed Note that it closed quickly. I think on your slower table exits PinballX is hitting an internal timeout after around 8 or 9 seconds after asking VPX to close and then kills it when it finds it's still running (again would need @Tom Speirs to confirm). So the cause of the issue is probably that VPX is now exiting slower than it was before and those couple of extra seconds delay now is enough to push it over that timeout limit. I'd be tempted to try the DX version to see if that exits quicker for you if you're not using GL specific functionality (or just use the taskkill workaround to kill pinup as a launch after)

From your log it looks like PinballX is resorting to killing VPX rather than a clean close (and that's probably why pinup doesn't exit); 20:04:16.12 2/5/2025: Visual Pinball Foreground Timeout: 32 20:06:03.74 2/5/2025: Exit System Control Pressed 20:06:04.56 2/5/2025: Found Visual Pinball editor window 20:06:12.75 2/5/2025: Killing process 20:06:12.75 2/5/2025: Process Closed Can you launch a few non pinup tables and attach a log file after that (just to see if they exit cleanly) as i expect the log to show something more like; 10:19:00.72 15/02/2025: Visual Pinball Player window foreground: 9 10:19:02.45 15/02/2025: Exit System Control Pressed 10:19:10.58 15/02/2025: Found Visual Pinball editor window 10:19:10.64 15/02/2025: Process Closed It seems that for pup tables (at least) on your setup for some reason PinballX isn't finding the Visual Pinball Player window. Why that would suddenly start happening i have no idea 😕, maybe @Tom Speirs does (or if i'm even on the right track here!)

It might happen with the DX version too now (i'm sure it never used to!). You could try turning fullscreen exclusive off in VPX, but then performance in game might suffer... so you may have to just live with it.

Is that before or after the loading media? Fullscreen exclusive with the VPX GL version can produce a momentary black screen as the game appears on screen, or if it's a delay before the loading media appears then it might be due to media in use (file size etc).

Are you seeing a black screen or the visual pinball editor instead of the loading image/video while the table is loading? Try adding the -minimized flag to the Visual Pinball launch parameters on one of your VP systems and see if that helps if it's the VP editor. E.g. Current launch parameters; /play -"[TABLEPATH]\[TABLEFILE]" Suggested launch parameters; -minimized -play "[TABLEPATH]\[TABLEFILE]"

Strange that it's only one table not exiting correctly. There's an old workaround to kill pinupplayer here https://forums.gameex.com/forums/topic/25060-resolved-pinuup-player-not-closing/ as a launch after script in PinballX (you'd only need the pinupplayer.exe line in that script) (the normal suspect for pinupplayer not closing on exit for one table is not having controller.stop in the table_exit routine of the tables script, but that's probably not the case with a VPW table!)

Not that i know of, i think you'll have to have the 'Hide Mouse Cursor' set to No and then just move the cursor to the side of screen when a system is launched where it's not used