Carny_Priest

That thread is a little out of date. It has gotten easier for me to configure the controller with later versions of x360ce. Here are my settings: I don't even have deadzone set in the Advanced tab. If I have trouble with the plunger, I just unplug the USB and plug it back in to recalibrate.

Resetting by unplugging the controller and plugging back in is a very good idea. From there, it sounds sounds like you need to adjust axis dead zones in the Advanced tab. I don't recall what settings I have for mine. I'm not near my cab at the moment.

Don't know about xpadder. X360ce is pretty close to self starting. Copy it to the same folder as the fx2 executable. Run it. Allow it to download the Fx2 profile from the Internet. It should automatically detect the plunger kit. You may have to go to the Advanced tab and select 'Pass Through' to activate. You will be able to test the configuration. It's set and forget. It will run automatically when you start Fx2.

I'm running a VirtaPin v1 plunger kit which also emulates a joypad and not a keyboard. I don't use the xpadder plugin. I use antimicro. https://github.com/Ryochan7/antimicro Antimicro to map the exit button to Esc key and an ahk script to kill the FX2 process on Esc keypress For flippers, plunger, nudging - x360ce so that the plunger kit emulates an x360 controller. x360 already has an online config for FX2 although you may want to do some tweaking of deadzones. https://github.com/x360ce/x360ce It's all opensource/donateware

I use Display Changer II http://12noon.com/?page_id=641 the utility can manage multiple displays, cloning displays, changing resolutions, rotating displays, etc. through xml files that you generate. I then execute through ahk scripts as needed.

Can't say that I have put this to the test as I have my vpx tables in a separate xml until vp10 is out of beta. But if the user is using the alternateexe tag in the xml, I would think that could be leveraged for solving this. Otherwise, I do rename the game name to something that is more unique. The example from my setup is Fire! and Firepower. I wound up using aFirepower for the game name tag and renaming all my media to match that rather than use the description tag.

This is my personal capture script. This uses a custom xml, mostly to support my miniDMD project which is a VP launcher, but it may be possible to use a standard xml. If tag 'rom' is populated, the script will pull the correct capture dimensions from the VPM registry. Tag 'exe' stores the correct executable. This would be 'alternateexe' in a standard xml. The new one is the tag 'B2S'. If True, the script will pull the correct capture dimensions from screenres.txt. There are some extras here: custom hard codes for certain roms where I am intentionally overscanning. If I pulled the values from the registry, ffmpeg will crash because the capture area is beyond the defined area of the desktop. I also have a section for AMH, where if the table is selected then the capture parameters are pulled from the UltraDMD key in the registry. I don't have the B2S kill script in here but you would replace line 256 with something involving those rosveClose/CloseVP subroutines from FPLaunch. They have been used for years in HyperPin. They are tried and true; works every time for me in my VPLauncher.

Well, that is the deal with the script that I use personally for capturing. I wound up using a custom xml with an added B2S tag so that I could control whether or not I would record the DMD area depending on the table. Of course, that means I can't use Game Manager. And that may be a dealbreaker for many users. It was OK for me. I'm used to putting together my own media packs and editing the xml by hand in Notepad. I always record all three screens. These are captured simultaneously, and I like that as a result the video are synced together in PBX attract/preview mode. Best example of the effect would be Mystery Castle. That's why I don't use PBX built-in VPM or dB2S support. But it's cool if you do; it does save disk space for more tables.

The error in the log - the numbers following window area are the X and Y coordinates of your entire desktop with (0,0) the very upper left corner (usually your playfield). And (4646, 1080) means the width of the entire desktop is 4646 px and the height is 1080 px. Then the capture area defined by the capture instruction starts at position 3290 px and extends out to 4656 px. 4656 > 4646. Ffmpeg does not like it if it is told to capture an area not contained by the desktop, and it will crash. If the DMD width is really 1360 then you can hard code the instruction to use 1360, and it should run. Sent from my iPad using Tapatalk

This is taken from my miniDMD script which is my VP Launcher. Instead of killing the VP process you would run the subroutines

Uploaded to the FTP a version of this rotated for cabs

It would be easy enough to incorporate the rosveClose subroutine from fplaunch when killing the VP process in the script.

Just curious, what issues are you having with B2S? I haven't had any issues with corrupt output, but my resolutions are fairly standard. Also, the output uses a full color palette. Works perfectly well with LAV filters but may pose issues with other codecs. This can be fixed to output a color palette that will work with anything.

My script can be modified to do what you are thinking of and also mirrors the DMD or B2S - you would extend the desktop on your extra screens and position the output on those screens. The solution does require a custom xml. I have media as well on the FTP. http://www.gameex.info/forums/index.php?/topic/16462-%5BUPDATE%5D-Visual-Pinball-mini-DMD-B2S-screen-for-apron-now-with-Instruction-Card-splash-viewer

The capture script does work with ffmpeg daily static build from November 1. FP playfield capture works with the current stable build of Open Broadcaster Software (0.656).

Great stuff. I think a lot of people are looking for a solution that does not require a command line. I assume that a recent build of ffmpeg was used to test. The latest version I'm using is 9/11. I'll test the latest build in the next day or so. I obtain my builds here: http://ffmpeg.zeranoe.com/builds/ I use the static build, requires 7-zip to extract. Just extract to C:\ffmpeg and use the same path with the tool. A couple of situations that might come up for users: 1. VPM DMD uses different dimensions on the 3rd display than that defined by screenres.txt. Examples, might include configuring the DMD differently for super size SEGA displays like Frankenstein, Baywatch, or Maverick. Or configuring the DMD to display overlaying a B2S. An example, would be positioning the DMD to work with The Addams Family dB2S, the one with the THING lights positioned underneath the DMD on a third display. 2. Less common, user employs some form of overscanning to maximize the size of the DMD/B2S. If ffmpeg is asked to capture any part of an image outside of the defined edges of the desktop, it will crash. There are a number of roms that have secondary playfield displays such as The Simpson's Pinball Party, Ripley's Believe It or Not!, and World Poker Tour. I can't turn off ddraw for these, and I do employ overscanning to achieve an edge to edge display on my third screen. Right now, I just have custom code in my version of the script to handle the special cases. And I do run a custom xml to help manage some of this. It may be beyond the scope of the project to do anything beyond batch processing, but it might be good to allow for some level of customization. I'm not sure whether that would be in the form of a lookup table a user edits or adding some more interaction in the current user interface. Well, even without customization I can see this working for the vast majority of tables, so that will be a huge time saver in any case.

In my laptop-based test bed, I found that I had to have aero disabled when capturing from opengl from FP. This was with some earlier tests when I was testing other screen capture solutions. I actually don't know if it is absolutely necessary for OBS. I wound up just including those lines in case a user was running with aero. For me, I always have aero disabled on my cab (Win 7).

To resolve performance issues, I no longer run NVidia DSR supersampling on the backglass display. Changing the backglass display to a resolution different from my playfield display revealed a bug in the capture script when capturing B2S images on the DMD display: This line: DMD_X:=BG_width+XDMD_X ;Reference to Top Left of Playfield screen should be DMD_X:=PF_width+XDMD_X ;Reference to Top Left of Playfield screen

Ok, the machine is set for 32bit color? If you suspect that output contrast is off (clipped whites or blacks), you can look at the graphics adapter settings and see if you can tweak the dynamic range output (either full or limited or similar pair of terms). Or change the color palette. I use RGB but there may be other choices. Might take some experimentation. Sent from my iPad using Tapatalk

Users in this thread have used variations of Python or bat files to automate. Should work well with VP. Not sure about automating the FP part. Only plan I might have at this point for enhancing is adding capture for PFX2. Sent from my iPad using Tapatalk

Try LAV filters linked on the PBX home page. Sent from my iPad using Tapatalk

The beta is publicly available. Sent from my iPad using Tapatalk

Yes, AC/DC launches fine from within PBX.

There's a competing open source project as well which is causing some drama with the for-profit developers: http://vpuniverse.com/forums/topic/2219-pin2dmd-color-pindmd-compatible-interface-with-led-rgb-color-dmd/

Cool. I like this table. I have animated instruction cards for this. I think it's in my Other Uploads folder on the FTP.