[RESOLVED] After exiting a VPX table, PinballX is not working anymore

[pcraenme]

When I exit a table in VPX, I get a flickering screen and PinballX is not working anymore.
Upgrading to the latest PBX version did not solve the issue.
I am using NVDIA driver version 591.86.
I have attached the logfile and ini file.

log.txt PinballX.ini

[Tom Speirs]

change the backglass monitor from 0 to something else. thats your issue.

Looks like you only have one display attached.

[pcraenme]

I have only one monitor indeed, an 3440x1440 ultrawide.

In PBX settings the Back Glass Display is on 'Display 1' (see attached screenshot). In the ini file monitor=0.
When I change the value in the ini file to 1, the PBX settings shows it as Display 2. Is that normal?

When I run PBX with backglas on monitor=1, the backglass and also Mike's PBXFlexDMD plugin is not showing in PBX.
When I change it back to monitor=0 for the [BackGlass], but set Monitor=1 for [Display], it seems to work again.... for now...

PBX just does not want to run properly on my system it seems, since it can run fine and a few hours later, it does not anymore.

[Mike_da_Spike]

1 hour ago, pcraenme said:

In PBX settings the Back Glass Display is on 'Display 1' (see attached screenshot). In the ini file monitor=0.
When I change the value in the ini file to 1, the PBX settings shows it as Display 2. Is that normal?

The ini file contains a numeric display that begins its count from zero. The interface, however, utilizes numbers that commence from one, which is consistent with what is presented in the Windows display properties. This is to avoid confusion. Or is it more confusing now? 🤔

2 hours ago, pcraenme said:

When I run PBX with backglas on monitor=1, the backglass and also Mike's PBXFlexDMD plugin is not showing in PBX.
When I change it back to monitor=0 for the [BackGlass], but set Monitor=1 for [Display], it seems to work again.... for now...

Not sure what my plugin has to do with it. It is not using any backglass setting, but uses flexdmd with dmdext, where the flexdmd is searched in the registry and using that.

 

[pcraenme]

1 hour ago, Mike_da_Spike said:

The ini file contains a numeric display that begins its count from zero. The interface, however, utilizes numbers that commence from one, which is consistent with what is presented in the Windows display properties. This is to avoid confusion. Or is it more confusing now? 🤔

Not sure what my plugin has to do with it. It is not using any backglass setting, but uses flexdmd with dmdext, where the flexdmd is searched in the registry and using that.

 

When Tom said "change the backglass monitor from 0 to something else" I got a bit confused yes, since I had it already set to 1 in the settings.

Your plugin is not causing the issue, but is affected by it somehow. When I set the Back Glass display to anything else than 'Display 1', FlexDMD is not showing anymore in the foreground (and Backglasses also disappear). I see FlexDMD initializing and then when PBX frontend appears, FlexDMD is not visible anymore. With Back Glass display set to 'Display 1', FlexDMD remains visible.

I think my system is 'special'.... since I keep on having these strange issues. After playing around with it for a while, VPX is also getting very slow to startup. This morning is was very extreme, 15-20 seconds. Normally VPX starts within 1 second. A system reboot is needed to fix that issue.

[Tom Speirs]

im sorry your having these issues. The only problem i can see is your trying to run multiple displays on a single display. Although I allow it to work in the code, it is really not designed for this or tested like this.

PinballX does try to hide the desktop, so it may not be slow starting vpx, just that pinballx is hiding it. is it certain tables?

if things are slowing down it could be a memory leak, but hard to know if that is PinballX or it is caused by an external component or plugin such as flexdmd.

[Mike_da_Spike]

1 hour ago, Tom Speirs said:

or it is caused by an external component or plugin such as flexdmd.

Don't blame the foreign guy 🤠! Just kidding. Plugins can screw up a load of thing. Especially of they use external dll's and touches rendering api's..I think it's (somewhere) in the manual, and @Tom Speirsmention it also a lot of time, disable all the plugins and try to reproduce the issue. If the issue is still left, blame the English guy 😎. 

[Tom Speirs]

no problem. i can take it easily buddy. lol

PS: We are all foreigners to the Americans!

[pcraenme]

I already tried disabling all the plugins (I only use 2, the Pinemhi plugin and FlexDMD plugin), but… that did not help.

I have a high spec system (AMD Ryzen 7 7800X3D, 32GB DDR5, NVIDIA RTX4080), so when startup of VPX is taking more than 15 seconds, something serious must be going on. I checked Windows event logging as well, but there is nothing noteworthy in there that could explain it. It is not affecting anything else on my system, and I play very high demanding sim racing games (in VR), which use all my CPU and GPU power. I also never had these kind of issues with VPX on my current system (almost 2.5 years old now). Just recently, when using VPX from PBX, these issues started. VPX was installed via BallerInstaller and is up-to-date.

I really like PBX, so it is really unfortunate I am having these issues. Thanks for all the support I already got on my issues. Let’s hope we can tackle them.😋

 

 

[Draco1962]

Is it possible that installing VPX via Ballerinstaller is creating the issue where it may not with straight a vanilla install of VPX? 

[Tom Speirs]

i need log please. Again, vpx might just be hidden. hard to say without the log.

[pcraenme]

Last few days things seem to have stabilized. Let’s hope it stays like that for now. When issues return, I will make sure to capture the logfile and post it here.

Thanks.

[Tom Speirs]

Good to hear but please let us know if we can help.