exiting tables takes longer then normal

[keithhov]

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

[Mike_da_Spike]

Hey, can you post a log after you select a game and exit it again? So we can see more from your logfile?

[keithhov]

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

[keithhov]

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.

[Mike_da_Spike]

I've also observed that my cabinet has been experiencing longer table exiting times this week, which started after the installation of Windows 23H2. 

Could you also supply the new log that includes the extended black screen duration? Perhaps Tom could work some magic to accelerate the process a bit.

[scutters]

@keithhov this might well be unrelated but what versions of VPX, freezy & VPM are you running- similar(?) problems here, https://vpuniverse.com/forums/topic/11015-updated-now-i-seem-to-have-table-exit-delay-and-puppacs-stay-open/.

Maybe see if there's any difference in delay on exit with an EM table.

 

[keithhov]

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.

[Draco1962]

One thing to make sure of is that you are running the latest manufacturers driver update for your GPU in addition to the latest versions of the software following major Windows updates.

[keithhov]

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. 

[keithhov]

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

[Draco1962]

If there's an issue with a current version it is always best to try to triage it for a fix.

The further away you get relying upon an older version the less likely you may be likely to get support, and the more likely other functionality will breakdown as future OS updates are installed.

[Mike_da_Spike]

As I mentioned before, I also encountered issues when upgrading to 24H2 with my display settings (so I hope Scutter won't have many problems with his setup of more than six monitors). However, swapping cables is irrelevant, as Windows stores everything in the registry.

Normally, I open the registry editor, navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers, and rename 'Configuration' to 'Configuration.old' and 'Connectivity' to 'Connectivity.old', then reboot.
This cleans up the monitor configuration in Windows. After rebooting, I set the monitors correctly in Windows. Then, I open VPX and set the playfield monitor correctly as well.

Also, open B2S_ScreenResIdentifier.exe and set your monitors correctly again.
Finally, open PinballX settings.exe and configure the display numbers according to Windows numbering.

if you got FP or any other emulator running, check and fix those as well

and a big thanks to MS that screws up the monitor with 24h2

Edited Thursday at 11:49 AM by Mike_da_Spike
Typo 24h2. Thanks Draco

[Draco1962]

But wait! You have no idea what Windows Hell awaits with 24H2!

[keithhov]

23 hours ago, Draco1962 said:

If there's an issue with a current version it is always best to try to triage it for a fix.

The further away you get relying upon an older version the less likely you may be likely to get support, and the more likely other functionality will breakdown as future OS updates are installed.

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.

[Mike_da_Spike]

2 hours ago, keithhov said:

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

got to your %appdata%\VpinballX fodler and edit VPinballX.ini
find section '; Video options' and change your Display = 0 to Display = 1
but that would be the same as  changing the settings as I mentioned and click Save changes 

I feel your pain @keithhov. I had it a couple of weeks ago myself, but al sorted out.
Not sure if @scuttersalready upgraded his cabinet to 24h2, but he will not be happy as well 

 

[Draco1962]

18 hours ago, Mike_da_Spike said:

Not sure if @scuttersalready upgraded his cabinet to 24h2, but he will not be happy as well 

Like 23H2, 24H2 will mean dfifferent things to different people. I have 3 different Win 11 Pro devices and 1 had an issue and the others were fine, and then a patch was issued to address 24h2 issues and a different device had issues that were subsequently fixed with another update... 🤬

[keithhov]

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.