MulletLife

RESOLVED FWIW I have it working, and now working better than my original DOF (No idea button lights were programmed in PBX). I had 2 setups. One was my from scratch build, all VPX DOF worked, nothing in PBX. Second setup was my setup from my old Vpin. Plugin worked, no lights in PBX or VPX. Started with my first setup, copied over some ini files, duplicated them and renamed them to what worked on old setup. Then I replaced the .COM DLL file and tlb file. Instant success. So now its just dialing something in to have PBX talk to undercab/speaker/playfield lights as I see some of these are in the dofconfig... not sure why some work now that never did. But for now this is resolved. TLDR: Replaced the file directoutputcomobject.dll and the plugin snaped to life.

I know this has been addressed many times. I've looked through the old threads and have not fixed my issue. I'm not sure if its related, but not only does my DOF not initialize in PBX, but when I run a table through PBX, DOF will sometimes hang on game exit. Likely because the PBX DOF code is not sending the exit/start codes. We'll fix PBX first and revisit. This issue popped up when I did a brand new vpin hard drive, from scratch, the only copy/pasting was tables. All files used were most current versions. 32/64 installed at the same time. PBX 7.13 if it matters. All DOF working in VPX. What I've done: Updated the plugin to latest dll Re-registered the x86 dof .com Checked that it shows the correct path in the plugin config I had 2 branches in the registry both pointing to x86. I now see there is 2 spots to look (local and classes), I only checked one. As a note, I have never had a cabinet.xml file on any of my builds, its never been an issue. We can see via logs that it fails to initiate plugin. Nothing I've seen anywhere on the PC refers to an x64 reference. All the wackiness in the DO.log has just started now that I've added a pinone board to the mix. So far that isn't breaking any of the games... so I'll contact Phil at CSD if that causes any issues other than reporting errors in the log. Thanks for the help. DirectOutput.log log.txt PinballX DirectOutput Plugin.log PinballX.ini

Not sure if this is resolved or not... note that there are 2 speeds. There is skip 1 game, and skip multiple games. Perhaps you have mapped both to your flipper button. You can test this by simply moving left or right with the keyboard. If your buttons are going faster than the keyboard, its a mapping issue. If its the same speed as a keyboard key press, then that is just the regular speed.

I'll have to grab those off the other PC, if its helpful. I have 2 screens set up in cabinet mode. So in PBX, there is a vertical monitor which is the playfield, and mounted on top is a landscape 2nd monitor. In PBX I want the monitor to show the blackglass, in VPX I want it to show the topper. I have the switching of screens all sorted. The only issue is that if I ask PBX to display the Topper and BG on the same screen at the same time, it defaults to the Topper in front, and I want the BG in front. As mentioned in my edit, I can 'solve' the problem by renaming my topper and backglass folders. I was just looking to see if there is a way to force the backglass on top of the topper window when both are displayed. Since I have a work around fix, its not a massive priority. Mainly checking if I missed an 'always on top' check box somewhere.

Yes, that is correct, and that is the intention. I want the topper to stay so I am left with a Playfield and Topper (what I use for the dmd) when in VPX.

FWIW, renaming the folders did fix the issue. Just looking to see if there was a more legit way to resolve the issue, but if it involves a lot of work, a work around fix on my end is better than hours of coding for an issue no one but me has.

I'm sure this is a very (me) focused issue. I have a 2 screen setup for PBX. What I'm looking to achieve is the Backglass to show on screen to while scrolling through tables. Once I chose a game, the Backglass disappears and the Topper is left in its place. This all seems good, except my Topper happens to always be the screen on top in the PBX second screen. Is there anyway to force Backglass to appear over top of the Topper? I'm sure a work around is to rename the backglass video folder to Topper and vice versa, but that seems excessive. Thanks everyone.

Not sure if you stated specifically, have you confirmed that the issue is NOT there when you load direct from VPX? In Game Manager, is it selecting the correct version of VPX. It will potentially hang if its pointing to something that doesn't exist (ie a typo). Have you tried to launch table direct from Game Manager? My 2 cents

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!

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.

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

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.

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.

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.

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.