BamBam963

It tries to launch and then a blank window pops up on the desktop. When I check the Task Manager, it looks like the Steam Bootstrap is the offender. I can only end the process within Task Manager. I am able to launch the tables without issue directly through the Steam Client. I have my databases separate for each table classs e.g. Star Wars, Zen, Fox, etc. I do not have a master datbase for PinballFX2 as a whole.

Okay. I uninstalled PBX and then reinstalled it, and the problem with VP tables is fixed. Now all of my Pinball FX2 tables don't work. Sigh

Hi Folks, I have been plugging away at my cabinet build for some time. Everything was working harmoniously, but last night when I tried to play VPX, VP9 and VP9 PhysMod5 tables within PBX, I got an error message that stated: "B2S Backglass Server Could not find a part of the path 'C:\Visual_Pinball\Tables\VP9\VP9'." I surmised this was a global problem, so I went through the usual B2S troubleshooting techniques, but PBX would not launch a table. I then utilized VPX 10.4, VP9X and VP9 PhysMod5 editors, respectively, to launch the tables. To my surprise, all tables from each of the three table categories launched with B2S without an issue. It appears to be gremlins mucking about within PBX from what I see in the error message; which indicates that PBX is looking for an additional sub-directory when it shouldn't be. For example, I store my tables as follows: "C:\Visual_Pinball\Tables\VPX; C:\Visual_Pinball\Tables\VP9; and C:\Visual_Pinball\Tables\VP9PhysMod5". I checked my settings within PBX and utilized the navigate button to redirect PBX to look in the proper folders. I attempted to launch tables from each category (VPX, VP9 and VP9PhysMod5) and got the same error. What I do notice is that PBX is duplicating the subdirectory for all "Table" folders in each of the categories. For example, the error for each category indicates it is looking for the tables in folders as noted below: VPinballX.exe - C:\Visual_Pinball\Tables\VPX\VPX; VPinball993.exe - C:\Visual_Pinball\Tables\VP9\VP9; and VPinball99_PhysMod5.exe - C:\Visual_Pinball\Tables\VP9PhysMod5\VP9PhysMod5" I have attached a copy of my PinballX.ini file and Log.txt file in hopes that someone might be able to offer up some advice. Thank you in advance for your assistance. John log.txt PinballX.ini

That must be it as I re-installed PBX last night. I will give the unblock a try. Thank you.

Thank you. I will check it out when I get back to the ranch.

Thank you good Sir. I will compare them and see where I messed up. BTW-What is the FutureDMD_Relay.exe for?

Terry is my FP God. That is how I set it all up. FP works fine with all tables. It is just when launched via PBX that the wheels fall off the bus. I will compare my settings with the one below and see where I am at. Thanks for all of the replies.

I checked the task manager and PBX is definitely shut down. Can someone who has FP working under PBX be kind enough to screen capture the following for me? 1. Future Pinball Key Settings 2. Pinball X Keyboard settings (or PBX.ini) 3. FB launch settings within PBX (or PBX.ini) Thanks

Changing the key would remedy the exit routine, but why does PBX shut down when FP is launched?

I am currently using the following Future Pinball (BAM) launch parameters in my 3-screen cabinet. [FuturePinball] WorkingPath=C:\Games\Future Pinball\BAM TablePath=C:\Games\Future Pinball\Tables Executable=FPLoader.exe Parameters=/open "[TABLEPATH]\[TABLEFILE]" /play /exit /arcaderender /STAYINRAM FPRAMPath=C:\Games\Future Pinball\fpRAM LaunchBeforeEnabled=False LaunchBeforeWorkingPath= LaunchBeforeExecutable= LaunchBeforeParameters= LaunchBeforeWaitForExit=False LaunchBeforeHideWindow=False LaunchAfterExecutable= LaunchAfterHideWindow=False LaunchAfterWaitForExit=False I am successful in launching my FP table, but when I press the button assigned to exit the table and return to the PBX menu, nothing happens. When I press the Escape key, I am brought back to the Windows 10 desktop, but PBX is not longer running. I tested to see what happens to PBX after I launch Future Pinball by selecting the Task manager while Future Pinball is running. From here I can see that PBX is not running any more. It seems as though launching Future Pinball from within PBX totally kills PBX . I have read several other threads and do not see this issue reported else where. Is there something special that we need to do in Future Pinball to map exit buttons etc? System: Win10 64Bit All programs setup to run as Admin. PinballX.ini log.txt

I will disable it and try that. Thanks.

Here are the files. I moved the backglass monitor onto the R9 card with my playfield and kept the DMD dedicated to the R7 video card. That has remedied the B2S issue in PinballX. Pinball X however, still changes what it thinks Identity 2 and 3 are. It keeps reversing them. Each of the VPin.exe are holding steady with the DMD and b2S assignments so it looks to be a Pinball X issue of recognizing the monitor assignments. I surmize that as the backglass video and dmd for Pinball FX2 are on the wrong screens, but the b2s is correct, but the dmd is not for the VP games. On a side note, after launching Pinball FX2 from within PBX, I get kicked back to PBX, but Pinball FX2 is still running in the background. I can Alt Tab back to it, but it seems to initiate a new PBX event. I am going to kill the automatic updates once everything starts working as it should. The cabinet will no longer be tethered to the internet, once I figure out how to get Pinball FX2 to work in offline mode. Any ways enough of that. here are my two files. PinballX.ini pinDMD_log.txt

Which forum was this supposed to go under? I thought this was the PBX General forum. My bad Drako. Next beer is on me. ;-)

I am ready to cry. ;-) I had posted this problem before and thought it was resolved. I am running Windows 10, VPX, VP9X, VPPhysMod5 and Pinball FX2 I have my monitors assigned as follows: Monitor 1: Play-field (AMD R9 HDMI output) 1920x1080 Landscape Monitor 2: Backglass (AMD R7 HDMI output) 1366x768 Landscape Monitor 3: DMD (Shared with Backglass on AMD R7 VGA output) 1080x1920 Portrait Monitor placement within Windows is left to right with Monitor 1 on the left, Monitor 2 in the center and Monitor 3 is on the far right. Vanilla Win 10 drivers with no AMD Catalyst software is installed. B2S is configured correctly and Backglass is functioning properly in VPX, VP9X and VPPhysMod5. E.g. Display 2 @ 1366x768. DMD values all set to 0 SetDMD and UltraDMD configured and DMD is properly displayed in VPX, VP9X and VP Physmod5. Pinball FX2 is set to display the DMD only and Backglass is turned off so that the video Backglass keeps playing within PBX and while playing Pinball FX2. PBX is set to use B2S Backglass and DMD videos and the settings have monitor assignments set as above. PBX is set to play Pinball FX2 video Backglass in the front end and in game. Everything works fine , however, PBX infrequently changes monitor assignments for VPX, VP9X, VpPhysmod5 and Pinball FX2. To rectify this, I change a line in B2S Setup to change the XPosition of the Backglass to a value of -1366. This fixes the problem for VP tables temporarily, but gets buggered up again after a reboot of the PC or restart of PBX. I then have to reverse the process by changing the X Position of the Backglass to 0 . Sometimes, going into the PBX setup and switching the monitor assignment between monitor 2 and 3 fixes the issue for the Pinball FX2 Backglass videos. Sometimes I need to place a -1366 X Position value in the PBX setup program. It seems the issues are with PBX and B2Ssetup or Windows 10. I am considering a switch to a 2 screen cabinet, but it seems like a drastic step backwards to have a peace of mind to have this system run consistently. I am sure it must be something simple.

Would someone have already created a 2 screen version (with grill) of the following PBFX2 tables? Doom Fallout Marvel-A-Force (Women of Power) Marvel-Champions (Women of Power) Skyrim Star Wars - Rogue One

Thank you good sir.

Does anyone have Table Audio for the following VPX Tables? Card Whiz (Gottlieb 1976) Grand Prix (Williams 1976) Rapid Fire (Bally 1982) Spider-Man Vault Edition (Stern 2016) I would be willing to contribute some audio if someone can provide a brief explanation on how to capture the table audio. Thanks John

Does anyone have a DMD Video for this table yet? It is my last missing piece of media for my Pinball FX2 project. Thanks.

If you cannot get TBA to run DirectX11 games, it proably is an issue in the registry. If I recall correctly, you need to find the TPA entry in your registry and change the path to your user profiles for the game. Farsight goofed up and the path in the registry is for Stern Arcade and not TPA. You just need to rename it to your TPA path and you will be golden.

That did the trick. I uninstalled the AMD Suite and let Win10 install the vanilla drivers. Pinball life is good again. Now I can go back to growing the hair I pulled out all week. ;-)

Problem solved. I had a master pinball FX2.xml file created for Pinball FX2 and three seperate ones for filtering my Star Wars, Zen and Marvel specific tables, respectively. I had the "Enabled" statement set to "True" in my main Pinball FX2.xml file. By switching them all to "False" and leaving all of the tables in the filtered .xml files to "True"' It fixed the issue.

Hi folks, I have Pinball FX2 running in cabinet mode on my three-screen rig with no issues. I have it setup to launch from PBX as per instructions found here. The problem is that Pinball FX2 kicks me back to PinballX about 10 seconds into a game. The backglass image and DMD from the table I loaded is frozen in PBX. When I try to launch a different Pinball FX2 table, from within PinballX, it takes me right back to the previous table that kicked me out before. This table also boots me back to PBX. Any thought on how to resolve this issue? Thanks. John

I read that thread, but thought it was too old to be relevant. Should I totally ditch the catalyst suite and use vanilla drivers in Win 10 instead?

I have a three screen cabinet and everything runs great in VPX. I fire up PBX once and it works great. I exit PBX and go back in and my backglass is on my DMD screen. Frustrating as hell. I am running two AMD cards. R9 2GB card for the playfield and an R7 for the backglass. Playfield is on screen 1, backglass is on 2 and DMD is on 3. It never works consistently. It works consistently in VPX by itself. I have all of my monitors side by side in Windows. Monitors 1 and 2 are in landscape mode and Monitor 3 is in portrait mode so it takes up less realestate between the speakers. All monitors are numbered 1 to 3 from left to right. What I have notived is that the AMD catalyst suite has the monitors assigned to different Identity numbers than Windows does. B2S Setup sees the monitors the same way Windows does. PBX keeps switching monitor 2 and 3 around regardless of what is programmed into B2SSetup and SetDMD.

Same thing happens to me and I am about to lose my mind. I have a three screen cabinet and everything runs great in VPX. I fire up PBX once and it works great. I exit PBX and go back in and my backglass is on my DMD screen. Frustrating as hell. I am running two AMD cards. R9 2GB card for the playfield and an R7 for the backglass. Playfield is on screen 1, backglass is on 2 and DMD is on 3. It never works conisitently.