DJO Maverick Posted August 1 Share Posted August 1 1. 3 screen cab w/ DOF 2. DMDExt and PUP Player (but not a PUP table in question) 3. VPX 10.8 RC4, all versions 4. Seemingly all tables at random, though seems more frequent on latest G5K Addams Family and VPW Twilight Zone (which could be just more frequent play) 5. Yes 6. See 3 I've seen a lot of older threads about what seems to be the same issue, and maybe I've missed the solution somewhere. I've got an ongoing problem that strikes seemingly at random, where PBX refuses to acknowledge a quit emulator command. I've got VPX menu bound purely to escape (which isn't mapped to an accessible cab button), and PBX quit emulator bound to Q, an exit button on the front of the cab, to ensure they no longer conflict... and sometimes it works, and sometimes it just... doesn't. When it doesn't, plugging in a keyboard and alt-tabbing to PBX, Windows indicates it has stopped responding. It never recovers and has to be force-closed. As far as I can tell, there's absolutely nothing in the log either, other than launching the last table. I did notice that some threads suggesting ensuring that VPX was running full-screen exclusive, which mine is. Thanks, log.txt PinballX.ini Visual Pinball.xml Link to comment Share on other sites More sharing options...
Draco1962 Posted August 1 Share Posted August 1 Thanks for answering the questions found here: It is rarely referenced, yet it speeds up triage to have some concise data of the setup and the files attached do help. I am not an expert but get lucky sometimes. This one is a head scratcher. Have you tried disabling plugins, see if the issue resolves, then reenable each of the plugins until the issue returns? Link to comment Share on other sites More sharing options...
Mike_da_Spike Posted August 1 Share Posted August 1 Check this post as well: my assumption is that it has to tne exclusive full svreen mode with gl and the full screen hack of PBX Link to comment Share on other sites More sharing options...
DJO Maverick Posted August 1 Author Share Posted August 1 Killed full screen exclusive on the VPX side; so far, so good. Will keep you posted if something changes. Thanks- 3 Link to comment Share on other sites More sharing options...
Tom Speirs Posted August 1 Share Posted August 1 I have seen this behavior myself. Just saying. I agree that its some kind of exclusive display/driver issue. You can also disable full screen exclusive mode in PinballX itself by enabling full screen windowed. 1 Link to comment Share on other sites More sharing options...
DJO Maverick Posted August 3 Author Share Posted August 3 Update: Well, had a good run (inexplicably, apparently), but it cropped up again on Twilight Zone even in full screen windowed. So, that does not appear to be the solution. Whether it had some mitigating effect at least or I just had a run of good luck would take some more empirical testing... Link to comment Share on other sites More sharing options...
keithhov Posted August 3 Share Posted August 3 I had exit problems in the past and found that the GL version of vpx works better with pinballx then the non GL version.....I also have had issues with the newest version of TZ,,, some type of crash but the table keeps playing, but an error pops up in the background.... could cause problems exiting the table in pinballx. Maybe ALT TAB next time you can't exit to see if there is a error message to rule that out. 1 Link to comment Share on other sites More sharing options...
Draco1962 Posted August 3 Share Posted August 3 On 8/3/2024 at 1:45 PM, DJO Maverick said: Update: Well, had a good run (inexplicably, apparently), but it cropped up again on Twilight Zone even in full screen windowed. So, that does not appear to be the solution. Whether it had some mitigating effect at least or I just had a run of good luck would take some more empirical testing... Is it erroring again with all tables or just Twilight Zone? Can you attach new copies of your pinballx.ini and log.txt files after switching to fullscreen windowed and running Twilight Zone generating the error described? Link to comment Share on other sites More sharing options...
DJO Maverick Posted August 3 Author Share Posted August 3 I can create new ones next time it happens but I can tell you off the cuff when I glanced at it last time that the log ended in the same fashion. TZ is just the first one it's happened on since last post, though it always happened more frequently on newer VPW releases and the latest TAF (though it could happen on anything). Link to comment Share on other sites More sharing options...
DJO Maverick Posted August 23 Author Share Posted August 23 Been a minute (was out of town), but here's a fresh example from first day back, this time with Chrono Trigger. This is a slight variation on the theme though, that I've seen a few times with FS Windowed; here PBX crashed while loading the table in the first place, and without ever bringing the player window into focus (VPX and everything launched, B2S and Freezy were up, but black window and doom-loop cursor of frozen PBX remained over the player window until I tabbed to it). PBX had to be alt-F4'd. log.txt PinballX.ini Link to comment Share on other sites More sharing options...
scutters Posted October 10 Share Posted October 10 Sorry, looks like this got buried. Is it still an issue? Assuming it is can you check the event log to see if anything is logged there at the time of the hangs. This might seem a strange suggestion as it's really for VR users but could you also try with the VPXontop app running (https://vpuniverse.com/files/file/15657-vpxontop/) as a test just to see if it helps. Easy enough to remove or disable after. One other thing to try would be running VPX GL non fullscreen, but in windowed mode (under video prefs) with size 1 pixel less then screen width/height - actually, try this first.. i'm fairly hopeful that running VPX non fullscreen will get round issue Link to comment Share on other sites More sharing options...
DJO Maverick Posted October 28 Author Share Posted October 28 I have not seen it happen yet in RC5, knock on wood. 1 Link to comment Share on other sites More sharing options...
Draco1962 Posted November 5 Share Posted November 5 Has this issue been resolved? If not, please uprgrade to v6.20 and attach copies of your pinballx.ini and log.txt files. Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts