scutters

I'll send you a PM.. going a bit off topic for pinballx!

Can you post a log.txt after launching a table? Also, have you tried VPX running as admin or just pinballx ? Edit - and what is fix.exe, same issue with the launch after disabled?

No Cringe here.. not everyone has time, skills, space, tools etc to build a cab! Not sure what's loaded on VPcabs (just FX3 i assume) or how locked down they are. You might be best trying them first for support (again, not sure on warranties etc), hopefully they'll help you out and show you how to load up other software to get you going. Post back if not.

Few questions; Is this a new build issue or something that started happening recently? Is pinballx running as admin? How are buttons / keys mapped in visual pinball?, and is the Disable Esc Key checked or unchecked (visual pinball -> Preferences -> Keys). If unchecked try it checked Edit - sorry should have noticed before, in the ini file there's a few things mapped to the return button under [keycodes] - in Keyboard Input Settings change the Launch option to another button and see if that clears the issue

They look awesome! Finished item will be just mp4's (or other video format) then, rather than interactive B2S file as used in visual pinball?. If you use visual pinball Kiss here https://vpinball.com/VPBdownloads/kiss-stern-2105tribute/

Not had problem of VPX loading on backglass but i'd check playfield is set as main display in windows.

One thing you can try is in Game Manager unselect the 'hide backglass' option, this will mean that the backglass video will continue to run (so no black backglass screen during load) and then the B2S will load over the top. It will mean that the backglass video will continue to run in the background so i assume it carries some overhead - but i've been running like this for a while and not noticed an impact on my setup. If that works and doesn't affect gameplay then the easiest way to change the setting for all tables is to open the system .xml file in notepad and do a find and replace to update the entry for all (but make a backup copy first!)

Give v3.37 a go, not sure if the update included any multi gpu fix but it's worth a shot

Is playfield monitor set as 'main display' in windows?

Could we have an option (disabled by default) to remove/hide the wheel and table info box when scrolling through tables and table selection has not changed for x seconds? (so the playfield would show just the table video/image un-obscured). Default for x seconds would be around 5 or lower i guess. Table info & wheel could re-appear on any button press (except Select to play). Not sure if it'd be needed / wanted in Attract mode, but would be nice to see table info and then the unobscured table view when manually scrolling through tables. Thanks!

No errors in the logs so i guess the backglass is showing somewhere just not visible (in fullscreen). Maybe you need to try the backglass on screen numbers higher than 5 (you'd have to edit pinballx.ini directly, [Backglass] section monitor=x, or reset the monitor numbers https://support.displaylink.com/knowledgebase/articles/736116-windows-display-properties-identify-numbers-are

I refer you to my previous hacky method But, yeah that would be pretty cool handled natively in pinballx!

You're not running dual GPU's or anything are you? Error looks similar to that in https://www.gameex.info/forums/topic/22127-serious-display-issues-335/

@cherga I think your suspicion is right re the usb displaylink from settings log "Video Card: DisplayLink USB Device" @joebladyko Can't you run all the screens off the GTX980?, should have plenty of power for it. Anyway, seems like some multi GPU issue with 3.35 beyond my skills/knowledge.

I think you're referring to the wheel underlay. If so you want an underlay.png file in C:\Pinballx\Media\Images\ Examples here;

Last thing in the log is "Loading Game Statistics and Scores" Maybe you have a corrupt statistics.ini file or high score data?. Look in databases folder for the statistics.ini file and see if there's any rogue characters in there (or post it back here)

Hacky method.. Load on a media player of choice (that can launch minimized, autoplay on start and has configurable shortcut keys, and is pretty lightweight- i guess most can/are) set that to start with windows (or launch with pinballx start up), then either kill it or ideally pause with sendkeys or whatever with table launch before script and then restart / unpause the player with a launch after script on table exit Configure media player to point at your TNA playlist and it'll play that, pinballx would handle table audio on selection. Not tried it but i'm 99% it would work, i have GOM audio on my cab that i launch with some tables to play random music where i have removed removed the table's own music (but left callouts etc) and that setup works for me there with the two audio sources.

Try changing this value to 10 directly in your pinballx.ini file to try and reduce length of recordings (rather than going through settings.exe) [VideoCapture] KeysStartRecord=120 KeysEndRecord=120 Seconds=30

You could be pushing a GTX660 a bit hard with the video creation & playback, that might be cause of choppiness and slow recording. Other option is to try using PBXRecorder for the recordings (which will read screenres.txt directly and allow 5 or 10 sec recordings when running, or screenshots rather than videos)

In addition to Mike_da_spikes advice can you confirm if there's anything more in event viewer around time of last error (07:12:38.8), and does everything else appear to be functioning ok (other apps)? You could also try pinballxlite.exe, I suspect it'll have the same issue but if it doesn't that would be of interest.

My bet is UseB2S was set to True in the ini file But, whatever...

Sorry, my post is a bit misleading - yep it was fixed earlier, but as i was suggesting a new install i just mentioned the latest version.... which then changed so i updated the post. Not sure what was fixed in v3.34 but as no change log i assume it was only minor / cosmetic stuff

@phazer No single known event caused the issue then... Will have a look at the .ini when you post it but for now what i'd try is to rename/move your pinballx folder (as backup) and reinstall again (v3.34 now) and try that with no config / media files, if that works copy ini, database, media foldrs back one at a time trying again in between. (I'm assuming your uninstall previously was a windows uninstall without a delete of the pinballx folder after - if you fully removed pinballx before reinstall then ignore my suggestion)

@phazer When did the problem start?, after update of pinballx, windows updates, etc?

You need to attach your log.txt and pinballx.ini files, but it sounds like an issue reported by some users after upgrading to v3.30 which was fixed in later releases Make sure you're running the latest version v3.32 v3.34 (32bit)