Carny_Priest

Yes, my little flash player project that cycled through instruction cards and score cards on the apron went by the wayside because the viewer no longer works at all when I upgraded to Windows 10. I don't know if it is a flash support thing or AutoHotkey. It's a shame because the single viewer could support vectors, bitmaps, and animation. Could have added some cool table features without having to actually mod any tables. But still it seems that retaining really good quality means larger flash files on the output which takes longer to load, and that's not good either. PDF would probably be better, I think.

I request pdf support for instruction cards and flyers. I went through a process of converting a lot of Stern and Inkochnito repro cards to vectors in order to retain source file quality and then converting to swf using some old Adobe tools. The output was viewable in browsers but wound up being corrupted and unusable in PinballX's flash viewer. To have the best quality, it would be great just to cut to the chase and use a pdf viewer then all we'd have to do is crop the sources and the images would look as good as possible at any resolution.

"May the 4th" be with you! Star Wars titles currently on sale for FX2. https://blog.zenstudios.com/?p=6271 I got caught up on The Force Awakens pack and I've converted the ShorYukenToTheChin table guides to Flash for use in PinballX. Uploaded to the FTP (Instruction Cards under #open6l) Star Wars - Episode VII The Force Awakens Star Wars - Might of the First Order Enjoy

Hi, the latest OBS studio added command line support for multiple profiles, so I ported gtxjoe's version 1.4 to support capturing Future Pinball tables. It has all the features of 1.4 except that it supports only Future Pinball and uses OBS Studio as the capture engline for playfield, backglass, DMD. Ffmpeg is still required to complete the transcode to generate the final output. Latest OBS Studio for Windows (portable zip): https://github.com/jp9000/obs-studio/releases/download/0.14.1/OBS-Studio-0.14.1.zip The installation contains both 32bit and 64bit executables. The script assumes 64bit and assumes that you will extract directly to your C: drive. Unzip the following file into the obs-studio folder, RETAIN THE FOLDER STRUCTURE WHEN YOU COPY https://dl.dropboxusercontent.com/u/45430846/config.zip Open a command prompt and navigate to obs-studio\bin\64bit execute obs64.exe --portable Agree to the license. There are pre-existing profiles, scene collections, and sources for playfield, bg, and dmd. Each source captures an entire screen. You may want to confirm that each profile is capturing the correct screen. Click the settings icon for display capture in each profile and see that the preview is displaying the correct screen. You can change the screen using the pulldown menu. The script assumes that full screens are used for playfield and bg. Ffmpeg will automatically crop the DMD video based on your FutureDMD settings. I think that's it. The 64bit compiled executable is here: https://dl.dropboxusercontent.com/u/45430846/PBXrecorder_x64_1.4FP.exe As always, run as admin. This can co-exist in the same folder as PBXRecorder for VP. The log will get overwritten but it creates an ini file with a different file name. Output will look best and work trouble free with the LAV filters that are linked on the PinballX home page. Because of the length of time it takes to load some of the more elaborate tables in my cab, I've increased the wait time from 15 seconds to 60 seconds. It's simply what it takes on my system to load SlamT1lt's Nightmare on Elm Street and Robocop. I'm running FP at 3K using NVidea DSR on a GTX 660. Using the same capturing engine, the videos are synced up better than when I was using a mix of OBS and ffmpeg. But my hardware is three years old now and running all of these capture simultaneously causes slowdown, so this may require some beefy hardware, or you might try capturing the different screens in separate sessions. I'm assuming if you are capturing three screens that you are using FutureDMD. I'm not aware of another solution. Capture settings are read from the registry and FutureDMD.ini. No sense trying to capture anything until you are sure the tables are playing correctly. Works with or without BAM. Why would you not use BAM, though? Source: Changes from 1.4 ; 1.4FP Future Pinball support with playfield capture via OBS Studio ; Add support for ™ and recognition of * (i.e, *) in Table and Description names ; Some minor clean up for unused ErrorLevel parameters Again thanks to gtxjoe for allowing mods to his source code.

Try it both ways on a favorite table and see which option you prefer. For me, I go with videos.

Probably have to map joystick buttons to a key (joy2key, xpadder, etc.)

Need some more information from you: Your pinballx.ini, specifically.

Congrats on Dr. Dude, by the way. Can't wait to give it a try later.

With: Without:

Two ways. Define different systems for each executable in pinballx.ini. OR Use only the main Visual Pinball system and the alternateexe tag in Visual Pinball.xml to override the choice of executable defined in pinballx.ini

The contents of your PinballX\Databases folder

Got a log file for this?

The fine Dozer version of Cirqus Voltaire shows that it is very doable to have VPX render a mirrored display with flashers. It would require modding the tables and scripts for this feature. Not a high priority for me at the moment. But very cool.

Ok. Just to clarify EVERYTHING works the way you like it outside of PinballX? The tables in your install all use directB2S or are other solutions included like the older B2S executables or UVP? You are setting up a separate system for each machine type. And you are doing this and setting up separate screenres.txt in each folder so that you can retain native aspect ratios for the backglass image? You are not willing to simply stretch the image to fit, right? I suppose if EVERYTHING is working correctly outside of PinballX that there is not any issues with screenres,txt. The right screen numbers are defined and you have the right offsets defined. As you have separate systems defined for each machine type then you will need a folder for each system. The name of a folder should match the name you have given the system. If you have a system with name=Tables_Alpha Numeric Compact_Physmod then the folder must be named Tables_Alpha Numeric Compact_Physmod. And within the folder there must be a file named "Tables_Alpha Numeric Compact_Physmod.xml" Let's say that we are not dealing with custom grouping. Then, the tables that you have in your C:\VISUAL PINBALL\Tables_Alpha Numeric Compact_Physmod folder would have entries in "Tables_Alpha Numeric Compact_Physmod.xml". If you are using different image offsets for each machine type then you will want the hidebackglass tag to be "True". PinballX will simply cover over whatever it typically shows on your backglass during preview mode. directB2S or what every SHOULD then display over PinballX during play. The setup is not one I've seen before. Very non-standard. Everything works from the editor, but because this is not a standard setup you will also need to test EVERYTHING again from a command prompt. This is most like how PinballX would be attempting to launch tables. Change dir to your Visual Pinball folder type in vpinball-Physmod5-plunger-mods.exe -play "C:\VISUAL PINBALL\Tables_Alpha Numeric Compact_Physmod\%Table%" where %Table% is some vpt table file in that folder. If the table has a directB2S file associated with it, the file name of the directB2S and the vpt MUST, MUST, MUST be identical! Keep testing. Baby steps. One thing at a time. If EVERYTHING works from the command line then it SHOULD work within PinballX. All said, I'm not sure that I would want to go the route you are going. You are in for a lot of housekeeping because all the media would need to be placed in separate folders (a set of media files for Tables_Alpha Numeric Compact_Physmod, and so on) OR you will have to setup a lot of symbolic links and kiss Game Manager goodbye.

Submit that suggestion here:

Probably should post your ini and log to get better support. Besure you are running PinballX and Visual Pinball as administrator. You should just make a habit of doing that with any pinball-related executables. IMO, if you are using built-in VPM support to display the DMD during preview I'd say disable that and use videos.

in your Keyboard Input Settings, set Exit Emulator to something besides Esc. Try E or Q. Be sure that your Visual Pinball executable is set to run as administrator. Be sure that your PinballX executable is set to run as administrator.

Hi, I managed to figure out how to flip the pyprocgame display for my cabinet so I installed the cool Cactus Canyon Continued project on my cab. http://soldmy.org/pin/ccc/index.php?title=Main_Page The code for the Visual Pinball port is here: http://vpuniverse.com/forums/topic/2286-cactus-canyon-continued-proc-in-vp/page-9#entry26310 Arngrim's DOF mod of the vpx table is here: http://vpuniverse.com/forums/topic/2286-cactus-canyon-continued-proc-in-vp/?p=27382 dB2S and wheel image here: http://vpuniverse.com/forums/topic/2286-cactus-canyon-continued-proc-in-vp/?p=27835 Requires the P-ROC to VP framework. Install files and instructions here: https://bitbucket.org/horseyhorsey/pyprocgame-evildead/wiki/Home or http://www.vpforums.org/index.php?showtopic=32197&page=3#entry320603 The table runs with official VP10. However, Cactus Canyon Continued requires an older set of VBS scripts, found here: http://vpuniverse.com/forums/topic/2286-cactus-canyon-continued-proc-in-vp/?p=26345 It's a truly complicated setup process, but well worth it as the project adds a lot to the original which was rushed to market in a relatively incomplete state to make way for the doomed Pinball 2000 platform: http://soldmy.org/pin/ccc/index.php?title=New_Things_in_..._Continued Plus more since that page was updated: more bandits, more callouts, a brand new built-in service menu, and full color virtual DMD: Because the table requires the old VBS scripts then there has to be a separate VPX installation. I also use a DMD display resolution that is different from any other tables I run to best accommodate the available options that come with Cactus Canyon Continued. So, I setup a totally separate system in PinballX.ini and use a dedicated script for launching the table (It works best for three screen cabinets): And here is my script for generating media. It is tailored to my particular hardware setup using NVidia DSR 4K and a non-native resolution for my DMD display. Modify the ffmpeg capture parameters to best fit your setup: If your setup is not that complicated and you make use of the alternateexe tags to run a different VPX installation. It's quite doable to just put this in the standard Visual Pinball.xml database and use PBXRecorder. You will need an alternate script to handle the Runtime error box that inevitably pops up with P-ROC controller based tables: https://github.com/horseyhorsey/proc-loader-pinballX Lots of ways to manage the install and get it working with PinballX. I tried to mod the code to include flipping the DMD as an option in the service menu, but I'm new to Python and couldn't get it figured just yet. I wound up "hardcoding" a solution for myself. I'm probably the only one running this in a P2K style cabinet, but if someone happens to need it then I can make the code mod available upon request.

I've installed over my existing installation dozens of times. I've never experienced an instance where my settings were overwritten.

Double-check that your WorkingPath and TablePath are correct. Double-check install directions for Visual Pinball, VisualPinMAME, B2S.Server or anything else you have running with VP. Updated run-time environments are not always installed when you install any of these programs. Check that any required by these programs as documented in the install instructions are up-to-date. If you are upgrading from XP, you will find that you will have to run all pinball executables as admin especially since you have things installed in the Program Files (x86) folder.

The settings used for obs-studio are comparable to those used in the original PBXRecorder: Open source H.264 lossless encoding 30 fps YUV444 color format Full color range Identical code for transcode and downscale for the output file In other words, it is the same quality results as the PBXRecorder for VP. Sent from my iPad using Tapatalk

Ffmpeg does not capture the FP playfield, rendered with OpenGL. At least not for me running in full screen. My mod only supports Future Pinball. For Visual Pinball continue using PBXRecorder. Sent from my iPad using Tapatalk

Hi, thanks to gtxjoe for generously making his source code available. This is a version of PBXRecorder that supports capture of Future Pinball tables. It has all the features of 1.3beta except that it supports only Future Pinball captures via swapping ffmpeg with OBS Studio for the playfield capture engine. Backglass and DMD captures still require ffmpeg Latest OBS Studio for Windows: https://obsproject.com/download#mp Install OBS Studio in the same folder where you will run the script or executable. The installation contains both 32bit and 64bit executables. The script assumes 64bit. Unzip the following file into the obs-studio folder, RETAIN THE FOLDER STRUCTURE WHEN YOU COPY https://dl.dropboxusercontent.com/u/45430846/config.zip Open a command prompt and navigate to obs-studio\bin\64bit execute obs64.exe --portable Agree to the license. You should see in the title bar that the profile and scene loaded are both named playfield. Right click on Sources: Display Capture and confirm that the screen that is being previewed is your playfield screen. Change the display in the pulldown if needed. I think that's it. The 64bit compiled executable is here: https://dl.dropboxusercontent.com/u/45430846/PBXrecorder_1.3betaFP_x64.exe As always, run as admin. This can co-exist in the same folder as PBXRecorder for VP. The log will get overwritten but it creates an ini file with a different file name. Output will look best and work trouble free with the LAV filters that are linked on the PinballX home page. Because of the length of time it takes to load some of the more elaborate tables in my cab, I've increased the wait time from 30 seconds to 60 seconds. I'm running FP at 3K using NVidea DSR. Some of the more elaborate tables (SLAMT1LT) has some slowdown while capturing on my system, so this may require some beefy hardware, or you might try capturing the different screens in separate sessions. I'm assuming if you are capturing three screens that you are using FutureDMD. I'm not aware of another solution. Capture settings are read from the registry and FutureDMD.ini. No sense trying to capture anything until you are sure the tables are playing correctly. Works with or without BAM. Why would you not use BAM, though? Source: https://dl.dropboxusercontent.com/u/45430846/PBXrecorder_1.3betaFP.ahk Changes from 1.3beta ; 1.3FP Future Pinball support with playfield capture via OBS Studio ; Add support for ™ and recognition of * (i.e, *) in Table and Description names ; Some minor clean up for unused ErrorLevel parameters Consider this beta as well. I've done some basic functionality tests in Win 7 x64 and some more thorough testing and catching up on my captures in Win 10. Again thanks to gtxjoe for providing such a great tool.

Ok, I thought you were keeping multiple db2s for some reason. Are you keeping multiple versions of the same table (day mod, toy mod, night mod, phys mod plus night mod, blah blah blah mod)? All the multiple VP executables can safely coexist in the same folder. Just use the alternateexe or exe tag in a single xml to call the correct version of VP. For me, I tend to select a single version of the table that best represents that table (usually the latest VPX) and I don't keep any others installed. I don't have much of an issue with having multiple copies of the same db2s. I have a few like AFM where I haven't decided among multiple wonderful versions! But the vast majority of tables I have installed just have one VP file and one db2s file. If you do maintain a lot of multiple versions of the same table where it is worth the bother of maintaining a central respository of db2s files to save disk space then you can script what you need following the basic structure of the script I coded for another project: PinballX launches the script and passes in the table name instead of directly launching VP. Read in the xml that makes use of alternateexe or exe tag. The values of the description tag can be matched to a file name in your central db2s repository. Perform the action and launch VP. Wait until VP closes and clean up. When the script completes control returns to PinballX. If you maintain multiple xml then the script for GTXJoe's PBXRecorder would be a better example of how to read in values from your various xml. I think what you want to do is perhaps well beyond the features that PinballX provides in-the-box, but it is flexible enough to do just anything anyone would want if you were willing to script it for yourself with autohotkey, batch files, Python or whatever.

Code an autohotkey script that reads the xml, copies over the db2s file and renames it to match the tablefile name then launchesVP. Use PinballX to launch the script and pass in [TABLEFILE] Sent from my iPad using Tapatalk