scutters

It looks like you have FX 3 set up as a custom system rather than using the built in FX3 system in PinballX? As FX2 is working i'd try enabling the built in FX3 system (and disabling the custom FX3 system) and seeing if you get better results with that.

Please attach your pinballx.ini file and the log.txt file (after a failed launch attempt). Thanks

Sorry, i didn't mean move the FPLoader.exe file, i meant changing the working path folder in PinballX settings for Future Pinball from C:\Games to C:\Games\Future Pinball\BAM. (no need to delete the pinballx folder!)

No problem. Did you check the working path in settings? FPloader.exe is normally installed into ...\Future Pinball\BAM i think, so C:\Games\ for FPLoader.exe looks wrong

Your launch parameters for FP are; Parameters=/open "[TABLEPATH]\[TABLEFILE]" /play /exit /arcaderender Try with the /STAYINRAM flag as well. i.e.; Parameters=/open "[TABLEPATH]\[TABLEFILE]" /play /exit /arcaderender /STAYINRAM Also confirm FPLoader.exe is located in your working path folder C:\Games (not in C:\Games\Future Pinball\BAM or similar) If you still have problems please also include you log.txt file (after attempting to launch an FP game)

As well as dracos suggestion you should also note some differences in your pinballx config; Non Working Parameters=lair vldp -fullscreen_window -ignore_aspect_ratio -x 1280 -y 1024 -framefile "C:\Daphne\dl\vldp_dl/ace/ace.txt WaitForProcess=DaphneLoader.exe Working (3 diffs highlighted in orange) Parameters=ace vldp -fullscreen_window -ignore_aspect_ratio -x 1024 -y 1920 -framefile "C:\Daphne\dl\vldp_dl\ace\ace.txt" WaitForProcess=Daphne.exe I'd start by changing those to match first off.

@thefuse001 Can you post your pinballx ini file etc from the working vpin daphne install?. Must be a difference in setup somewhere.

Not sure if it's a factor or not but you have system 3 (spaceace) set up as a VP system type in PinballX settings, might be worth trying it as 'custom' like system 2 (daphne). Worth ruling out anyway, if it's nothing i guess we wait to see if Mike can reproduce..

What happens if you ALT+TAB to Daphne after launching from PinballX. Does the input work then? (just to figure out if it's a windows focus issue or something else) Not sure if you have any plugins enabled in PinballX (please attach log & ini files). You could try disabling them if you do. Like Mike, i've no experience with Daphne.. does it have fullscreen / windowed modes that can be toggled?

Lol.. sorry, i misunderstood the issue entirely! We will investigate. Thanks for the portrait / landscape hint. The ini file may also help if you can attach it, thanks.

The instruction card /apron screen is always on, or at least it should be (and is for me - instruction card shows in PinballX and stays on after game launch).

My guess is either you have 2 pinballx installations (and the app is looking at the wrong install) or you have file matching enabled in PinballX (and your media file names don't match the exact game name or description fields - most likely to have happened if you copied media manually). But hard to say.. can you attach your pinballx.ini and log.txt files, along with the database manager log file (in the the log folder of the install location). A zip of your databases folder and some sample unfound file names may also be useful. Does any media show in PinballX database manager?

A couple of ideas for the wheel; For animated wheel users have an option to animate only the wheel image of the game that is in focus (so only one of the the five visible wheel images is animated). Might help with performance, but main reason would be to emphasise the wheel of the in focus game. Have an option to remove the intermediate (moving) wheel locations during wheel rotation. To be honest, i'm not sure 100% sure how this would be in use - i tried putting together some still frames without the transitioning locations shown and it looked good to me, but it may be different (or 'feel' different) when movement is in response to user input

For FullDMD users ( @DBrown67) if you have letterbox underlay videos set as DMD videos in PinballX the new DMD display options are ideal, as they can be sized/positioned to appear on top of the letterbox area (where the dmd would appear in game).

Please update PinballX to the latest version and re-attach log and ini files if there's still an issue (i have favourites working with v5.12) From your log you're on a fairly old version "PinballX - Version 4.01 x64"

V1.6 released, notes / zip updated in first post. This adds DMD style display options for virtual DMD users (don't select these options is you're using a real DMD - i have nothing to test on so can only believe bad things will happen if you do). Virtual DMD options will only display one line of data at time so will take longer to scroll through as can be seen in these examples; Classic Window style option (using Digital Readout font) XDMD FlexDMD (with freezy V1.9)

Make sure you don't have Basis Menu mode enabled. In Settings go to General Settings, Basic Menu Mode and set to No

Might be the Flash fix you need?. Not sure without seeing log/ini files. Update PinballX if not up to date and let us know if still an issue (attaching log and ini files).

Right click on pinballx.ini, then select properties. This box should be unchecked;

You can just attach the file itself rather than an image. Makes it easier to read. Also you didn't answer Mike's question about install location, don't install to Program Files just C:\PinballX or something. That might explain the problem, or is the pinballx.ini file marked as read only for some reason?

Well... that's just confusing!. This was with taking new screen grabs wasn't it?

I agree with Mike, a short video if possible could help. @mrgame Can you also confirm; What are your VPX settings (fullscreen exclusive set)? What happens if you run this from a command prompt? C:\Visual Pinball\VPinballX.exe /play -"C:\Visual Pinball\Tables\Robot (Zaccaria 1985).vpx" You definitely don't have any compatibility settings checked for PinballX? right click -> properties, this screen;

@Tom Speirs Sorry Tom, saw that post but thought (still think) we can find a workaround before a proper fix. Just had a few tangents along the way - but sometimes tangents are the best way to learn!! @DBrown67 Think you missed the bit in my post about dmddevice.ini. If you changed the reg values for vpinmame and freezy used that new size then you have useregistry set to true in the ini file. There should be section like this to control freezy size/pos and not use registry values, if you set these to your dmd 'letterbox' in the middle of the screen the capture may then work; ; use VPM's registry values when positioning the virtual dmd useregistry = false ; x-axis of the window position left = 5240 ; y-axis of the window position top = 105 ; width of the dmd in monitor pixels width = 1200 ; height of the dmd in monitor pixels height = 300

I suspect you may be onto something. As a test if you have the SetDMD utility handy you could try changing a rom registry entry to the full dmd screen dimensions (so pinballx may then record the fullscreen nd not stretch the screengrab when used). As you're not using vpinmame this should be safe, but please note that this could also affect how freezy is displayed - there's a setting in the dmddevice.ini file to use registry values or not, if you have that set to true then you'd need to set it false and then set a manual position / size (which is then saved in the ini file) for freezy. (You can of course manually edit the registry, but don't do that unless you're comfortable doing it and taking backups first etc.. do so at your own risk!)

Another idea for the system list.. Introduce another layer in pinballx navigation between the system wheel and the table wheel, a filtered list wheel. So, when you select a system if that system has filtered lists associated with it then display a filtered list wheel (media can be named similar to - system -, e.g. - filtered list name -), and then when a filtered list is selected the table wheel is then shown. The system would be shown again in the filtered list wheel as well as an 'all tables' or 'no filter ' type option. If there are no filtered lists then selecting a system will navigate straight to the table wheel as now. I think this could help with @PcTeknic's duplicate media across systems, as filtered lists could be used instead of different systems. It could also incorporate @lm_shaker's logic with the Exit button navigating back up through table to filtered list to the systems wheel. For users who do not enable system lists then i suppose the current navigation in PinballX could remain. ( i'm not sure where the legacy custom database xml would fit in with this proposal)