keithhov

RESOLVED!! 6.36 is back to quick exits to wheel menu, quick exit back to windows, tables even seem to load a few seconds faster. Definitely time for me to click donation link....20 bucks a year is a small price to pay the amount of time I spend with pinballx. Thanks to all.

Tried 6.33, no change in slow exit, backglass and vpm hung on screen when I got back to wheel menu.

ya i just tried 10.8.1 for the heck of it because I know its different......will try 6.31 soon

6.31 is actually slightly slower then 6.29, backglass and dmd hang on screen for about 3 seconds when exiting a table, then black screen for about 6 seconds, then back to wheel. I tried a fresh installation of pinballx, no luck, tried BGFX versions of vpx, tried 10.8.1, tried older versions of pinmame, all no luck. Thanks log.txt PinballX.ini

still slow exits with 6.31 unfortunately.

installed 2.29....no change in slow exits,,,tested with bfgx version of vpx,, no change. Stumped.. ....6.11 speedy exits. If I run vpx by itself tables exit quickly to file menu.

installed 6.23... still get the black screen for about 7 seconds when I exit a table before i get back to the wheel menu.....tried a new installation of vpx in a different folder....same results unfortunately. log.txt PinballX.ini

installed 6.21... still get the black screen for about 7 seconds when I exit a table before i get back to the wheel menu.....have tried different versions of VPX... no luck unfortunately

10.8 v2037 seems to work fine by itself....played fish tales for a few mins in 4k, steady 144 frames......2037 seems to work fine with pinballx version 6.11, exit takes me back to wheel menu instantly..........installed pinballx 6.20 and I am back to slow exits...not horrible but about 6 to 7 seconds of black screen then wheel menu..... tried both fullscreen hack options. I do get a error when installing 6.20 around C++, I don't get the error when installing 6.11. Might trying to manually reinstall C++ if one of you experts thinks it could be part of the problem.

Yeah I realize 1995 is a bit behind, I seem to be able to play all newer releases, especially VPW tables in full with no limitations that I am aware of. I will try 2037 tonight and see how it interacts with pinballx 6.11 and 6.20.... I kinda think windows builds/nvida drivers are causing most of the problems but that's purely a guess.

I too had exit problems with all the most recent versions of pbx and vpx/pinmame.. For now I am using 10.80 rev 1995 and pbx 6.11(something newer might work but I had 6.11 installer handy) and everything is working perfectly. Between new versions of windows builds, vpx betas and more there are just so many variables right now , very confident it will all be back to normal sooner than later.

Thanks scutters... I think i finally have it all figured out. When I tried Mikes registry steps above, windows still was making my primary playfield monitor number 3...and that was causing all types of problems,, windows,vpx and pinballx monitor numbers didn't match up consistenlty....I have kinda noticed that in the past but everything worked so I didn't really care. I could only get my playfield to be callled monitor 1 if I swapped display ports on the video card and then deleted configuration and connection in windows registry(thanks Mike) after reboot finally all 3 monitors were the correct number and windows monitor number matched up with VPX and PinballX. After rebooting a few times to make sure all the monitor numbers stuck, I installed 6.20 pinballx.... unfortunately, I still get the long exit of about 8-10 seconds of a black screen before I get back to the main menu. This is with the most recent public version of 24H2, latest pinballx and latest nvidia drivers. Fingers crossed all my monitor numbers stick as my cabinet turns off and on automatically each day. Maybe I will try a different installation of VPX on my cabinet to see if that exits quicky like it used to.

I did try to change VPinballX.ini file display 0 to 1, no luck unfortunately. I think I am just a weird spot with beta VPXs, nvidia drivers and windows being windows.... oddest thing is vpx,, I save it to play on monitor 1,,,,nope plays on monitor 2....sometimes....sometimes monitor 3, just all over the place. Also contributing was the B2S settings you mentioned as well, I am at least in a spot where I have some hope.... I imagine a few driver updates and windows updates it will be back to normal. I'll report back here if I find any big culprit.

ya i agree with Mike that the windows update really messed up my monitor configuration.... i did make some progress swapping cables but its still not right....VPX won't save playfield to the correct monitor no matter what I try....only way I can get it to work its to manual set display to =1 in individual table ini files... pain the ass to do for 200 tables,,, plus its very likely something will change and I have to do it all over again. I might try his registry hack above......I am usually down for a few hours of troubleshooting but just hopeful a windows update/nvidia driver update gets things a bit back to normal.

I did windows system recovery in hopes that it would take me back to windows version 23, I didn't think it would and it did not. It did put my windows back a few days to where I was using pinballx version 6.11, tables exited quickly again. I updated to 6.20, slow exits again. So sticking with 6.11 for now on cabinet. 6.20 works fine on pc with older nvida drivers....I updated newest nvidia drivers, tested 6.20, exits a little slower. Quick thoughts are Mike is correct above in that pinballx exits a little slower after updating windows to 23H2. I imagine it will all get fixed between newer nvidia drivers and some tweaks by Tom if needed down the road, I am fine closing this topic unless you feel otherwise. Thanks