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.

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

Manually removed each c++ item in control panel. Rebooted. xdmd error removed, kernalbase error remained, back to netvideoplayer error. Reinstalled c++ via Nov 2024 all in one.... netplayer error gone, xdmd error returns. Reboot. No luck. Turned to .net issues. Can't unistall. Went and removed a few .net optoins (mainly printing options). Rebooted. Errors. Installed 6.55, WORKING! This was a fresh install and stuff is messed up (looks like PBX lite) but I think we're on the right track. Going to put old version back and will update on results. Turns out the 'messed up' look was because I backed up my setting and then went vanilla. Transferred over my inis and we're back baby!!! So to wrap up, I (think) it was a .net issue... there's a chance that doing nothing but installing 6.55 would have fixed it. I think I was using 6.54 with no success. Either way, thank goodness the nightmare is over. " Thanks for all the help and advice guys! The c++ reinstall really put me on the right path. Case closed (officially this time)

DSIM and SFC have all bared no fruit. I see mentions of c++ runtimes and I will attempt that next as well as a newest pinballx install. Working on this issue now.

So the consensus amongst tech gurus. Kernelbase.dll is the 'base of all kernels', thus I can't simply overwrite it. It will update literally with every single windows update, hence why it looked like it updated as soon as I went online to download new vpx etc. If I'm the only one with the issue, that seems quite odd. It could be my exact blend of setup makes PBX not like the exact kernalbase I have. That, or once people start getting windows updates, all hell breaks loose. I can say I updated my personal pin with no issues, and I just spoke with a buddy who's kernalbase was updated today, no issues. I'm officially at a loss with no idea other than trying to do a Windows rollback and see if that fixes it. Otherwise, maybe Tom can spot a potential conflict from the evert viewer logs I posted above. Sincerely, up shit creek

Somehow the kernelbase.dll got updated as I was updating my Vpin. No idea how, but that's not really important. I'm trying to replace kernelbase dll as I'm certain that will resolve the issue. For some reason pinballx is just the sole casualty of this random update. I'll try the above methods though I'm fairly certain I've tried the SFC before, but not the DSIM. I'm away from the pin until at least Friday so it'll be a while until my next update. Seeing as its a Windows related issue, I will ask for help in Windows communities.

I'm 99% sure this is an issue with Kernelbase.dll which just happened to somehow magically get updated 2 minutes before PBX stopped working. Just looking on how to overwrite that file and I will report back. So at the end of it, likely not a PBX error at all.

Interesting the 2 errors I received are actual dll files in the PBX folder. netvideoplayer and xdmdnative.... not getting any closer but there's that. I have tried to copy over older versions to no avail. PBX lite does seem to load but still no go for PBX

This comment written in error, can't seem to delete. Issues persist.

Installed a fresh 6.54. Still the same Event Viewer issues. Kernalbase.dll and .net 6.0. Though the .net error now speaks of xdmdnative vs netvideoplayer. No log to provide as PBX never starts. Pinballx.ini is vanilla as it is a brand new install. It literally worked one minute on 5.47, then did not on 6.07

These are the 2 logs from Event Viewer if it helps anyone. Did a Windows 24H2 update and the issue persists. Application: PinballX.exe CoreCLR Version: 6.0.2824.12007 .NET Version: 6.0.28 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException: Could not load file or assembly 'NetVideoPlayer, Version=1.1.8008.37561, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified. File name: 'NetVideoPlayer, Version=1.1.8008.37561, Culture=neutral, PublicKeyToken=null' at PinballX.FrmMain..ctor() at PinballX.FrmMain.Main(String[] CmdArgs) Faulting application name: PinballX.exe, version: 1.0.0.0, time stamp: 0x65d50000 Faulting module name: KERNELBASE.dll, version: 10.0.26100.2454, time stamp: 0x398a1cce Exception code: 0xe0434352 Fault offset: 0x00000000000c837a Faulting process id: 0x3720 Faulting application start time: 0x1DB60979E9A9115 Faulting application path: C:\PinballX\PinballX.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: f983cbfa-5b49-4aad-a606-162eeb9f3756 Faulting package full name: bakPinballX.ini Faulting package-relative application ID: Attaching the log and ino as I know it will be asked. These did not update since the 6.07 install. Again, I did a full scratch install to c:\pinballx and the problem persists. No log files created as PBX never boots. log.txt