[RESOLVED] PBX issues effecting VPX (6.07 and 6.87)

[MulletLife]

Hi Everyone

I'll try to be as specific as possible. 
I've been using 6.07 primarily as any other update I've tried has always had some issue I didn't like and reverting to 6.07 resolved the problem. I recently tried a newer version, and then reverted which may be the cause of my current issue. 

6.07 - I'll have games where the flippers will stick. Confirmed it only happens when the table is run via PBX*. Scared Stiff and Party Zone were 2 tables tested, along with roller games (as shown in the logs). 

**The issue only occurs when the tables are run through PBX. Direct launch from VPX yields no issues.  Something somewhere PBX controlled/related is causing the issues.  (edited)

Updated to 6.87 - I'm unable to start games now. Specifically, I can't insert coins or start the table. Sometimes the keyboard will allow coins but the cab buttons are totally dead. I've switched screens to ensure its on top, closed b2s, dmd, etc and still nothing. Dead buttons. 

Revert back to 6.07, flippers lock up. 


One pro/con I've noticed between versions... The loading videos will last 5-10secs into the table load (6.07), where as the load videos in 6.87 will disappear PRIOR to the table load.  It appears based on logs there is a counter/timeout in 6.07 but maybe not in newer ones? Is this an editable option so I can dial it in?

The major con,  when 6.87 boots up (and this exists in every version I've tried since 6.07 and why I haven't upgraded), PBX will load, after 1 second the exit menu will pop up and I must remove it before table selection. Reverting to 6.07 resolves the issue. 

I can perhaps try a different version of PBX if you have a fairly solid build number to suggest.  Again, all seemed well until I updated (6.5x range?) and then reverted. In terms of install/uninstall method, I'm simply installing to the c:\pinballx folder. I never do full uninstalls. So maybe some updated files/dlls are not being written back when I install 6.07 on top of 6.87

Thanks

log 2.txt log.txt PinballX.ini

[Tom Speirs]

Sounds like its an input related issue but I can't think of anything right now or anything that would be different between those versions. Is your cab keyboard encoder based or gamepad?

i would generally check usb/devices on the cab.

[scutters]

I'd also try with plugins and the launch on startup "PBXinitsecondary.bat" & on game launch "WinActivate.exe" all disabled just in case there's something going on somewhere else.

[MulletLife]

17 hours ago, Tom Speirs said:

Sounds like its an input related issue but I can't think of anything right now or anything that would be different between those versions. Is your cab keyboard encoder based or gamepad?

i would generally check usb/devices on the cab.

I've done hardware/software tests on the buttons/encoder themselves and they work as expected in systems like FX3 and VPX stand alone. Sounds like I'll have to keep digging. 

[MulletLife]

16 hours ago, scutters said:

I'd also try with plugins and the launch on startup "PBXinitsecondary.bat" & on game launch "WinActivate.exe" all disabled just in case there's something going on somewhere else.

I can't recall what the winactivate.exe was for so if its redundant I'll try to remove that.  The "PBXinitsecondary.bat" is a custom script to close out 1 version of joy2key and start up another. It never dawned on me that it could be throwing in an error. 

6.07 was running smoothly until something happened. Either a vpinmame update or possibly windows update. 

Also editing the original post as it should state the following. 

"The issue only occurs when the tables are run through PBX. Direct launch from VPX yields no issues".  Something somewhere PBX controlled/related is causing the issues. 

 

[MulletLife]

I"ve tried with a totally fresh version of 6.07. I've populated the settings enough to get Scared stiff (10.74) to launch. No joy to key, not winactivate.exe, no plugins. The issue still persists when PBX is run. Issue doesn't exist when direct from VPX. And without winactivate.exe VPX always loads as a background app. 

I may look to see if a .net or c++ update may fix it?? 

Somehow adding PBX to the mix is causing an issue. 

Going to update vpinmame and b2s although I'm certain that's not the issue. But I'll try anything at this point. Somewhere the math isn't mathing. 

[MulletLife]

20 hours ago, Tom Speirs said:

Sounds like its an input related issue but I can't think of anything right now or anything that would be different between those versions. Is your cab keyboard encoder based or gamepad?

i would generally check usb/devices on the cab.

I believe it is set up as a joystick. Its a zebsboards plunger. It always used to worked. Something has changed to now cause issues. Updated Vpinmame and C++, no change.  No plugins, no joy2key, scratch install, minimum setup enough to launch a table. Currently joystick inputs are blank in setup wizard.

Is there a possibility something is stored in the registry that would stick around when moving up a version and then moving back? 

My next step is to see if I can completely uninstall or install to a new directory so it forces a new registry entry. 

I feel I know PBX inside out, I'm baffled. 

Edit: Not a registry issue. New install to new folder resulted in the same issue. 
 

Edited May 31, 2025 by MulletLife
Additional info under "edit"

[Draco1962]

I advise testing against the latest build vs v6.07 as there have been considerable fixes and enhancements. You may also wish to update the thread with the latest copies of your pinballx.ini and log.txt files. Thanks!

[MulletLife]

To add to the weird factor. I've download a different version of Scared Stiff (this time used bigus, not sure what I had before). The issue no longer exists (it was on a table by table basis anyways).

So it always worked in vpx, didnt work through pbx. Some 10.74 tables were fine, others had the issue. If its table specific, then why does the table work fine in vpx but the issue only arises when through the front end....

At least for now there (seems) to be a work around so that's a plus

[MulletLife]

1 hour ago, Draco1962 said:

I advise testing against the latest build vs v6.07 as there have been considerable fixes and enhancements. You may also wish to update the thread with the latest copies of your pinballx.ini and log.txt files. Thanks!

Even though its not resolved, I've found a fix (basically download alt versions of the table). As weird as the issue is, I can't isolate if its a table issue or PBX issue. Either way, it can get marked as resolved or thread deleted. 

The main issue I have with newer versions is a bug that causes the exit menu to pop up as soon as PBX starts. If its a me issue, it happens on every tested version after 6.07 but not in 6.07. Hence why I haven't updated. That's an issue for another day. PBX is doing its job for the time being. 

Thanks all for the help. 

[Draco1962]

I will close this as unresolved then. Our triage efforts are best spent in the current version.

Should you decide to upgrade and deal with whatever issues you may encounter with a current version, please start a new thread and we'll be glad to try to assist.

[Tom Speirs]

Thank you Draco.

@MulletLife seems to be a lot of this lately. Old version testing does definitely help troubleshoot but people seem to lack understanding that i can't fix an old version without making a new version!

[MulletLife]

32 minutes ago, Tom Speirs said:

Thank you Draco.

@MulletLife seems to be a lot of this lately. Old version testing does definitely help troubleshoot but people seem to lack understanding that i can't fix an old version without making a new version!

FWIW, I'm stumped but this is now RESOLVED. 

Symptom: 10.74 games will run fine direct from VPX, but flippers will lock via PBX
Resolution: Re-installed 10.74 solved the issue. 

No idea how that would have an effect on PBX but here we are. 

Either way, RESOLVED!

[Draco1962]

Thanks for reporting back your solution to the errors you encountered! This may help someone else with the same or similar error.

[Mike_da_Spike]

Could the setting "AutoConfigure=True" be the issue, @Tom Speirs? Or does that still set the registry for pre-10.8 versions?

[Tom Speirs]

That feature has been updated for post 10.8. So it could be. i don't have issues though.