Carny_Priest

Well, it may just be the solution that works for me as I run a custom launch script. I documented the issue and a solution here: It may be that you can try to have PinballX launch Task Manager programmatically.

The stop-gap solution is to run with Task Manager. Options -> Always On Top can be unchecked

Click the DMD on the playfield. F1 Uncheck Use DMD You may have to restart the table.

There should be a space between /STAYINRAM and /open

If you are really talking about pinDMD, that is a separate piece of hardware for attaching a real dot matrix display from a real pinball machine. If you don't have this hardware, then you don't have to worry about pinDMD settings. Again, I haven't been through the process of installing Visual Pinball via PinballX. Maybe there is a tutorial? In any case, if you at least get the playfield and backglass displaying on the correct screens then configuring the rest should fall into place.

Yes. Easy for us since we know how all of these separate applications, VP, B2S, VPM, etc., work together. Very confusing for someone new to the platform. These easy install solutions are supposed to bypass all of this tinkering. Probably will be easier for the OP to simply start over. Not much lost.

Generally speaking, if the game is not set up correctly then nothing you do in PinballX will fix it. PinballX is just the front-end. But it sounds like you are using the newer installation routines that attempt to set up Visual Pinball for you? I don't know much about that feature. It sounds like xactionbobx is giving you the right advice. You will need to have whatever screen you intend to use for your playfield configured in Windows as your primary display (i.e., not the one that is your laptop screen). At this point, you might try uninstalling everything. Set up your playfield display as your primary display, and then try to install again.

Are you saying that within PinballX the playfield is correctly displaying on the playfield display and the backglass on the backglass display. But that then they are reversed in game?

VPX 10.2 is still in beta. Go back to the VPX 10.1. If you are having trouble related to PinballX then come back and start a new thread. I don't think this is the same issue as the OP's.

Great. I had the mine issue. Solved it by not downsampling and just using native 1920x1080 resolution. Might try playing with AA or details settings. Multiball is the real issue. It should be at least 3 balls. Something to do with the trough code. It doesn't look like anyone is going to try to fix it. Sent from my iPhone using Tapatalk

Hi, this video shows typical behavior for My Tables selection. Selecting for Dr. Dude... https://dl.dropboxusercontent.com/u/45430846/Desktop 10.14.2016 - 16.26.50.03.mp4

I don't see anything wrong. Changing hardware can have unintended consequences. Some suggestions: Try setting the SystemType to Visual Pinball Try the newest VP beta http://www.vpforums.org/index.php?showtopic=35311&page=1 Try it both windowed and true full screen Maybe the timings for one of these options will work without having to force focus on the VP Player by coding it.

The usual drill. You should give us your log, xml, ini. I also need to know if you are running true full screen. By the way, does multiball work for you on CCC? I typically get only two balls. Last Call is a multiball mode as well, but I only get one ball.

I've attached my launch script. There are some instructions customized to my machine that you can comment out. I run the table in true full screen, but for P-Roc I find I don't have to do anything special to bring focus back to the player. LaunchCCC.ahk

Yes, I'm using the Version 3 option. I'll see if I can get Shadowplay or something working on this later today.

Ok, well, it's pretty clear what that code is doing. But given that users may have their cabs configured in different ways, some may require screen rotation, others keymapping, or even helper apps to mirror the score display you'd probably have to complete the script yourself. Compiling is easy. Install AutoHotkey from ahkscript.org. It will provide you a easy method of compiling by simply right clicking on an ahk file and selecting compile it. Even better if they do provide a command line driven method for directly launching into a table. I've been slow to work with the Zaccaria app because no multi-monitor support. I've gotten spoiled.

Can you share a link to the script?

FCM got updated, so I can test A-Z selection: Selection on tables A-F seems good. It goes awry with R-Z. Cursor seems to want to go back to the G-Q section. I had the correct table selected in the R-Z section once out of about six times. Tested medium, long, and very long delay My Tables selection: grid position 1x1 does not get selected. I have three other Owned tables that make up the first row. The other tables get selected correctly. I typically enable the free table of the month (Dr. Dude this month). It is in the Unowned section. I can hear the cursor selection happening but the selection does not move down rows consistently. Tested short, medium, long, and very long Very long selects the correct column but two rows up. All other delays selects the correct column but remains on the first row (Owned tables). Perhaps for those who own all of the tables, the "My Tables" support will work well.

Number 7!

Yes. I do this as well. Sent from my iPad using Tapatalk

Not much information here. Do have FX2 enabled for cabinet support? When you say that it runs outside of PinballX, are you trying to start a specific table from the command prompt. Or are you simply starting FX2 through Steam or double-clicking the FX2 icon and selecting a specific table through FX2's main menu? You've installed Steam in your Program Files (x86) folder. Do have UAC turned off or Steam set to run as Administrator? If nothing else in your parameters, try putting [TABLEFILE] in quotes such as "[TABLEFILE]"

I would not say that there is anything that you can do for me. I'm satisfied with what I have at this point. After all, this version of VPX is still in beta. Who knows what else will change? I've made it work for me by moving over to a custom system. I feel like the dB2S server crashing or not loading for very large files is a different issue, related to timing or order of focus. It's just weird to me that I can solve it by running in parallel with Task Manager. Again, this may be because I'm running a script instead of VP directly. I've linked to it if you want to look, and I mention it because I recall that someone else was having a similar issue at some point. Maybe it was TerryRed.

I can't say that I'm loving this feature either. I wound up having to move Visual Pinball to a custom system slot. Probably because I am having PinballX run a custom launcher that itself launches a bunch of helper apps. I recall there was mention of some dB2S backglasses not getting displayed in PinballX although everything runs fine outside of PinballX. In updating my launcher to run VPX in True Full Screen, I was running into the same issue. Weird bit, I mentioned in this post: Weird thing - If a dB2S is really large and/or takes a long time to load, such as the one released with Fire! or the big fantasy one for Monster Bash, there winds up being some sort of a conflict with PinballX where B2SBackglassServerEXE.exe is shutdown or crashes. I don't know if it is a timing issue or resource conflict. But if Task Manager is running at the same time, then dB2S backglasses always load successfully. It's hacky, but without knowing what else to do at this point, I programmatically start Task Manager before launching Visual Pinball and then close it down when quitting the table. This helped me with start up reliability not only with VPX but with VP9 tables that take a relatively long time to load such as Stern AC/DC PhysMod5.

Update: Modified to work and look better for Win10 (using a basic or non-Aero theme) Because of changes made to automate Visual Pinball, I can no longer use this launcher with PinballX's integrated Visual Pinball support. I run this launcher as a custom system with a custom system type. Start up and exit code is more reliable Tested with a recent static build release of ffmpeg (2016-09-29) and Nvidia driver (372.90) running on Windows 10 Anniversary Edition Can be modified for VPX windowed full screen support Display of Instruction cards and Score cards are better synchronized via cheap process cross-communication using a temporary ini file written to disc. Launches VPX True Full Screen and automatically brings focus to Visual Pinball Player (no support for mirrored DMD or splash viewer with true full screen, however) I've fixed all cards for use with the splash viewer. On the FTP, Other Uploads/Carny/Z20160604/MiniDMDFlash Edit: Update LaunchVP attachment PinballX.ini - don't need to monitor for any other executables LaunchVP1mirror.ahk - fix bugs Notes: I still run an Intel i5 3570k, 8Gb RAM, with an NVidia GTX 660, 2GB VRAM. With my configuration, the overhead of running all of the extra processes to display everything on both sides of the apron is a little much for VP9 and too much for VPX. Based on the executable, the script runs the mirrors and splash viewer for VP9. And for the performance benefit, the script runs VPX with its Video Options set to use True Full Screen mode. I've included a version of the script where the DMD mirror and splash viewer on the right hand side of the apron are disabled. That should be less of a performance hit if running on both sides of the apron causes slowdown or "sticky flippers" while in-game. Because True Full Screen locks out all other processes that try to use the screen there is no way this solution will work (not on the playfield screen anyway). Weird thing - If a dB2S is really large and/or takes a long time to load, such as the one released with Fire! or the big fantasy one for Monster Bash, there winds up being some sort of a conflict with PinballX where B2SBackglassServerEXE.exe is shutdown or crashes. I don't know if it is a timing issue or resource conflict. But if Task Manager is running at the same time, then dB2S backglasses always load successfully. It's hacky, but without knowing what else to do at this point, I programmatically start Task Manager before launching Visual Pinball and then close it down when quitting the table. No assumptions are made about the dimensions required to capture the DMD. If the table is VPM, the dimensions are pulled from the registry folder for VPinMAME for the specific rom the table uses. If the table is UltraDMD, the dimensions are pulled from the registry folder for UltraDMD. If the table uses a third screen dB2S or older B2S, the dimensions are pulled from screenres.txt. Capture dimensions can otherwise be customized in the script. Information that tells the script if the table is VPM or B2S is stored in a custom xml that uses the standard rom and exe tags and adds a B2S tag. I've included my xml as an example. For me, latency on the DMD mirror was better with Win 7 than with Win 10. This is probably the last update for this project. These days, I only install VPX tables. With my hardware, VPX runs great but not so good with DMD mirror and the splash viewer. As I replace the VP9 and Phymod5 versions of my favorites with shiny, new VPX versions I can see phasing this project out. I'd expect that a cab with powerful hardware could still use a variation of this script to run a mirror and/or splash viewer using a fourth screen. Somebody had asked about routing something like this to fourth and fifth mini screens mounted on a false apron. Possible, I guess, if the hardware is state of the art. LaunchVP.zip

Was going to test that attached executable, but FS updated again today so FCM is behind. Such a PITA FS is!