Carny_Priest

You should see the table's splash screen and a progress bar when loading. Every executable related to your pinball setup should be set to run as administrator including PinballX, FPLoader, Future Pinball, anything and everything else. If that doesn't work, try the official version of Future Pinball http://www.futurepinball.com/ Assign Exit Emulator to some other key aside from Esc. Then start getting used to always using that key to quit out of an emulator app. Q is good.

You lost me. I don't know what you are referring to.

Exit Emulator is the key that you set to close down the pinball simulator app that you have launched and return to the PinballX wheel. Quit - brings up the menu that allows you to close the PinballX application and return to Windows.

Yes. If you have Esc set to Exit Emulator in PinballX and Esc is set to exit out of the game in FX2 (bringing you to a game menu) then you have a conflict. It sounds like in your system it will be FX2 that recognizes the key press first. Resolve this conflict by setting one or the other settings to use a different key. Alternatively, you can always use Alt+F4 to close down FX2 immediately.

It is a shot in the dark, but in other contexts players have had trouble with Windows Defender. You might try creating exceptions for PinballX and VP. As always, set every executable associated with your setup to run as administrator.

Nothing leaps out at me with regard to the xml. And if something were wrong there then none of the media would be displayed. Make sure that the folder name was not inadvertently changed. It should be "Table Videos". Do you have other systems installed and they play table videos Ok? You could as a test swap out the video that is not working right now with PinballX with one you know is working. Eliminates the idea that you now have somehow corrupted videos. If the test video does work then re-download/regenerate your table videos. If all else fails reboot and/or reinstall PinballX/LAV Filters. If it was working fine before and not now and you did not change anything then maybe it is a flaky issue with a Windows or driver update? You could try a system restore to a point when you know the system was working for you.

The xml we would need to look at would be in your Databases/Pinball FX2 folder. The WorkingPath field in the ini looks funny. The executable is in this folder? C:\Program Files (x86)\Microsoft Studios\Pinball FX2 - Marvel's Women of Power The name of your video file in Media/Pinball FX2/Table Videos folder should identically match the value in either the game name tag or description tag in the Pinball FX2.xml file.

Here: https://github.com/freezy/dmd-extensions/releases

Sure, also if you have not already you should install LAV Filters. The link is on the PinballX homepage.

Install LAV filters? Linked on the PinballX home page. Update your video drivers?

Go ahead and update to the latest version, 2.28. Standard setup is to have playfield and backglass displays in landscape orientation. The backglass display is to the right of the playfield display. Top edges of the displays are aligned. How is yours set up?

Castlestorm, Zen Football, etc. show up in your wheel. You get a playfield image as expected but no backglass either? Or is it only Wild West Rampage that gives you a problem?

Backglass shows up for Visual Pinball tables but not FX2? Are there any files in Media/PinballFX2/Backglass Videos ? I believe PinballX will try to display a video first if there are both a video and a static image Try downloading a different image?

Well, apples and oranges. FX2 is not the same thing as VPX with P-ROC, with B2S, with DOF (I assume), etc. Do experiment with true FS. It's been around since the stable release of 10.1, I believe, so it is not like it is a brand new feature. It's solved ball stutter issues for a lot of users. Toggling Vsync on/off may help. I always keep it off. Some people prefer to have it on. Walk back on features that require more resources (AA, alternate ball images, playfield reflection, ambient occlusion, elements detail level slider, etc.) Wait for a built in processor affinity feature for VPX and/or B2S. It's so new that it has not even been released as beta yet, but I expect that it may be out soon. It may help as well. It's all I've got to suggest. I don't really have issues with CCC. There are long and currently active threads at VPF that are all about ball stutter. It's technically possible to pipe frames from p-roc directly to a real DMD. I don't know how to do it, but I don't have a personal need for this feature either so I won't be teaching myself how to do it. It doesn't appear that anyone else has shown an interest either. Whatever solution someone codes would only benefit that one game right now, so it's not very motivating. You might put in a request at freezy's dmdext repository. He might take a look at it. He might have a little more time now that vpdb is launched. Who knows?

Hmmm, I do use a custom system type for FX2. I forgot that I had trouble getting a clean exit with integrated support. Not an issue about key presses. I've attached my script in any case. Aside from killing the process harder, I use the script to launch helper apps to support functions specific to my own hardware configuration. You may not have to worry about launching antimicro (to map a gamepad button to an emulated X-box 360 exit button) OR launching dmdext to flip FX2's virtual DMD for projection on a Pinball 2000-style cabinet. The rest may still be useful to you. I use AutoHotkey scripts a lot with my cab. LaunchFX2T.ahk.txt

Myself, I don't use any scripts for FX2 and TPA at least not to navigate the app UI. As I mentioned above, for FX2 I use the command line launch feature and have PinballX launch through it's usual launch executable and parameters fields (i.e., PinballX.ini). I don't have any investment in TPA. Open source programs do the same simulation job with higher quality and a much richer feature set. I only keep TPA around to help test the integrated support. Currently, the integrated support is not working entirely correctly for me either. As Farsight keeps meddling with the UI function from release to release, I can see how that saps motivation to keep integrated support current and working in PinballX. It is what it is. Not all users agree that you can live without TPA though. Scripts here tend to use AutoHotkey as a super-sized extension of Windows bat instructions. A really good example is the defunct NukeLauncher app. It supported the older UI. Actually, it would probably be better to look at NukeFX on the site rather than NukePA because the current TPA UI got rid of its wheel UI and started using a grid UI that is similar to FX2. The source code is not published, but it is not like it can't be very easily viewed in any code editor. It will provide some good ideas how it is done. Looking at it you can decide if it is worth the effort to proceed with your own solution. http://www.nukelauncher.com/item.asp

Aesthetically, I would place the DMD on the backglass. Of course, I run using true FS. Before, you deal with that. You will need to deal with ball stutter. Troubleshooting: Does it eliminate ball stutter to run without DMDext? Sent from my iPhone using Tapatalk

Stexe, I'm not aware of a way to completely turn off key presses when you use integrated support for TPA. Using integrated support for TPA means that you do want PinballX to navigate the TPA app UI and launch a specific table as a single player game based on the value listed in the grid position tag in your xml. If you do not want this then your best bet is to disable integrated TPA support and use an "additional system" slot with a custom system type to simply launch TPA into the main menu. FX2 has some different options. Again, using integrated support means that you do want PinballX to navigate the FX2 UI and launch a specific table as a single player game. But, if you are using the Steam version of FX2, you can launch a specific FX2 table from the command line and bypass the UI entirely. As I recall, if you don't have any grid position tags in your xml then there are no other key presses happening in this scenario. At least, none that I recall impacting the game. Again, this is single player games only. The command line does not support launching hotseat multi-player games.

Launch dmdext with the -quit-when-done parameter https://github.com/freezy/dmd-extensions

I was using snippets of Atarian's code to handle focus issues on true FS. Those issues have been fixed in the more recent VPX betas. I fixed my table termination issues by removing Atarian's code entirely from my launch script. Yes, I change the FS registry values in my screen capture script. It's very easy and works everytime.

I'm not Tom, but I assume that you are using VPX and VPM betas. My POV at this point is you have a working solution for now. VPdev and PinMAMEdev are currently working on issues related to timing. Let the beta process play out before rushing fixes into PinballX that may not wind up being permanent or useful. I'm thinking that there will be a stable release in a few weeks. That said, I'm not putting you off. I have to run Visual Pinball as a custom system type myself. I have some really serious focus issues running the integrated Visual Pinball support with true full screen. I'm OK with running as custom as it works well for me. There's not much impact because I use something similar to the alternateexe tag. I just move all my media to another folder. I have my own capture scripts rather than PBX_Recorder. I don't think PBX_Recorder supports true full screen anyway.

Lol, yeah I see that 1 star rating in your activity list. I'd hate to see what you rate things you don't like. Glad you figured it out though.

You may just want to reboot and/or reinstall PinballX again prior to any formal troubleshooting. I would start troubleshooting by backing out all FX2 backglass videos. Do you get the default image when you scroll through? Does it still crash? Are you sure that your database file is error free? This is not easy to check sometimes, but an xml with errors will crash PinballX. If PinballX always crashes on the same title then it is likely an xml error. Introduce one change at a time to isolate on your problem media. What happens if you introduce just backglass images? Did you generate the videos yourself? Did you get them from the FTP or did you get them from some other source? Do they play correctly using a player outside of PinballX? Have you tried an alternate source? What's on the FTP is just shit people copy up. Not saying that it is bad quality but I don't think anything is checked so it is always a good idea to try until you find something that works for you. I never use Game Manager. I like to see what all is available and choose the alternative that I like best. I usually generate my own media. Also, you have to consider sources for your playfield videos. In other words, open6l did a bunch of videos initially and they are good quality but really huge in size. If you are using them in combination with your chosen backglass videos that may cause some issues especially if your system is not tuned too well, has a lot of other processes you don't really need running in the background that is eating up resources that could be used for PinballX. I don't have a real DMD installed so I don't know if that introduces trouble. I don't have a short answer. Just displaying Pinball FX2 videos on attract mode has not been an issue for me. I don't believe that PinballX itself is buggy in this regard. Seems like we would have heard a lot more about this if there were bugs. So, it will take a systematic process to figure out hat is happening on your end.