keithhov

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

ya i did all that......trying system recovery to see if it will take me back to older versions of windows just for now....Im thinking windows update to 24H and latest nvidia drivers are liking each other.

I generally have versions that are about 3 months old,,..I dont have much time to troubleshoot right now.....one thing is clear though,, the recent windows update messed things up big time for me......I can't get vpx to push playfield to the correct monitor no matter what one I select in video settings....I have to manually move cables in back of video card.....once I get everything working.....if I reboot windows doesnt even turn on my main monitor....weirdest thing ever.....super confused....throwing in the towel until the weekend.

i unchecked some options setting up the B2s screen res file and saved new display locations.... not seeing the created directx lines in log file now but still getting the 10 second delay exiting.......i exit,,,goes to a dark black screen for about a second......then goes to a slightly lighter darkblack screen for about 8 or 9 seconds, then back to the main menu as it should....just weird.

new log attached....seeing "Created DirectX BackGlass Window" and " Created DirectX DMD Window" after hitting exit button..... not seeing those created directx lines on my PC set up? I did reinstall b2s server when troubleshooting a few days ago when I was have problems with windows renumbering my displays..... log.txt

Exiting tables takes about 10 seconds longer than it used to on my 3 screen cabinet setup. A few days ago a windows11 update messed up my monitor numbers, I had tables launching on my backglass monitor and dmds all over the place, normally I can just change some settings in nvidia but this time the only fix was to actually swap cables inputs on my video card, eventually I got everything back to normal, but now when I exit tables in pinballx it takes a much longer time to get back to the main menu.. I exit, and I stay on a black screen for about 10 seconds then back to the table select menu,,,,not a huge issue but just a bit annoying. I did reinstall latest version, I tested latest version on a different PC but I don't have the long exit issue. Files attached. log.txt PinballX.ini

I think I finaally figured it out.... NVIDA control panel.....adjust video settings.....even thought I had this disabled for my ASUS monitor, it was enabled with either the backglass monitor or DMD display monitor...... and windows often reports a different number monitor then what nvidia reports.... so just a lot of confusion on what monitor is what in windows opposed to vpx/NVIDIA and also in vpinballx.....I have generally been aware of this but am just used to it and after a few minutes or trial I get playfield, DMD, backglass on correct monitor. either way I just set color adjustments to be made by video player, instead of NVIDIA for all displays and after cycling through a bunch of tables, all videos seem to play correctly...... FINALLY!! Thanks for the help

I generally don't have any frame rate issues.....a few titles I have to turn down some reflections to maintain 144 frames.. I also use vertical sync and get steady 144 with no noticeable lag.... frame pacing on my cabinet causes microstuddering even with overdrive disabled, frame pacing on my traditional PC works great. I can't go to HDMI on playfield cabinet, if you use HDMI your maxed out at 120 frames,,,, the main reason I upgraded to the asus 43 inch is to get 144 frames. There just seems to be some type of dynamic brightness or contrast overide kicking in on videos on occasion... I am just trying to narrow it down if it's being causes by nvidia settings(I do have gamma correction disabled) or the asus monitor...... I haven't dug into to deep because its a minor annoyance. Thanks for the tips/suggestions.

Playfield monitor is Asus ROG XG43UQ Strix 43" 4K UHD Gaming LCD Monitor, 144Hz, FreeSync Premium Pro Asus ROGXG43UQ Backglass monitor is just a standard 4k 32 inch samsung monitor hdmi, the ASUS 43 is a really good playfield monitor after some tweaking,,,once i turned off or down all the fancy stuff. 1.4 display port....... Tested a bit more and can only reproduce the issue on the asus, so I am pretty certain its some type of brightness/contrast override,,, fortunately actual tables look great and consistent.

updated to latest version of pinballx, upated nvidia drivers,,, verified all HDR settings off in windows and on monitor,,,,ASCR disabled on monitor, dynamic dimming disabled on monitor... If I force my main display to backglass monitor, the video brigtness seems very consistent on the backglass monitor,, when I put it back to my main monitor playfield, it seems some type of monitor setting tries to kick in...looks like some kinda contrast adjustment makes the videos bright occasionally ..... Pretty sure it's just my monitor opposed to codec issue or pinballx... I don't want to mess with monitor settings too much as tables look great in VPX. I am good closing topic again.

I do have a complex monitor with all type of adaptive/dynamic settings.... I think I have most of it turned off....fearful of changing those settings as I have spent hours dialing it in for perfect table brightness....I will update to latest version of pinballx... and check windows HDR settings...ill post back on here if I notice any changes. Thanks,

Seems to only happen or happen much more often only when attract mode kicks in...... log.txt PinballX.ini

issue still persists even with correct codecs...

I uninstalled all codes, installed the suggested LAV codecs from the forums, seems ok for now.

My playfield videos look great when I play them in a media player, but about 20 percent of the time they play too bright and washed out when scrolling between tables in pinballx. I just reinstalled video codecs....K lite I think, but it doesn't help. If change change video playback settings in nvidia control panel but it doesn't seem to help in pinballX.... I have had this problem for a while now... files attached. It's a weird issue,, if i go to Metallica for example, its occasionally is too bright and washed out,,, I will go one table to the right, then back to Metallica and it will look perfect. log.txt PinballX (1).ini

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.

I tried Mike's guide and confirmed it does restore the mouse cursor!!!.....oddly I do have more fun restoring the cursor with the missing cursor just to test my hand eye coordination.

I had my yes's and no's reversed.... i get no mouse issues if in settings i set hide mouse to "no".... so it basically works as intended... Once my mouse cursor is gone....i can only get it to go back to normal through windows control panel(windows 11).... I think some users think it will be restored just by changing the setting in pinballx.....

I just forced pinballx to crash....no mouse cursor issues since in my settings I have mouse hide set to "yes"........ I set mouse hide to "no", I forced pinball to crash......my mouse cursor disappeared....as I mentioned for me it does show as one tiny pixel... photo attached. The tiny black speck above the o in mouse.....thats my mouse cursor.....only way to fix is to get to control panel and change pointer options back to what you want..... hard to do with no mouse cursor but I have done it 50+ time testing pinballx months ago when I had a problem. Makes it easier if you have your desktop set to a light color....... good luck

I used to have this problem occasionally when testing things , especially if pinballx would crash or I would do some type of force quit. The mouse arrow would actually change to 1 pixel making it hard to see and I would have to change the mouse curser back to default through windows control panel. Attach the the files requested above and someone will give you some suggestions, make sure you have the latest version of pinballx.

I started playing visual pinball occasionally around the year 2000 on low end pc and a monstrous crt 4:3 monitor.... then I really got into a few years later on a 16:9 LCD rotated for full screen portrait mode......constantly going to file...open....loading a table.........at some point I stumbled upon PinballX, initially I spent days and days downloading audio/video/wheel logos for tables....so thankful for what we have today. Chalk me up for at least 50+ of the 100,000 downloads! Tom, Mike, Draco and others.... thanks so much.