mace

Sadly they have legions of phone users and only a few enthusiasts. Of course if they invited those of us who are engrossed in pinball and prepared to spend hours trying to recreate it to test the product it may get better.......but that would imply that someone cares enough to reach out to the community. It really is their loss as, even if they cannot support cabinet modes, coming clean and clearly explaining this would be an honest step forward. And there is no reason for them to build that terrible interface, even on a PC it's simply awful....

Cool, sorry that's what comes of reading things quickly in a train strike. Yes Farsight are all gits, they promised support, showed cabinet demonstrations and based on their empty promises we all bought a pile of tables that now only work on the one thing we all are trying to avoid, a desktop PC. I'd like it to work on principle but to be honest I'll probably just use VPinballX and dump the lot

Trying to help Dude, not trying to argue.......

Tom, my TPA FreeCamMod set up is working again with the new PinballX v2.23 build.

Happy to help Tom, I must admit I'm not in a good place with FS but having invested the dollar I'd like to think we can see it through. Thanks for making the offer too.

Thanks Draco, yet another hole in the menu opens up.........I still live in hope that Farsight will allow direct calling of tables at some stage.

Hi Tom, Couple of points, I'm seeing a long table exit to the TPA tables +24 seconds similar to the issue with VPinball that was fixed in build 2.12: I've tried slamming the door on TPA using a 'run after' TASKKILL command but it makes no difference, outside of PinballX the close and forced close are practically instantaneous. Secondly there seems to be an issue with focus as my loading had now stopped and the selection falls to 'last table played' each time - I don't think that's its a PinballX problem but as I mentioned above it started after I updated to the latest Nvidea drivers, it may be that my build is odd but I've uninstalled and reinstalled a couple of times and it seems that the only way to keep things going is a clean Nvidea install for new drivers not a straight update. Just mentioning it here in case it helps someone else, as usual with these short comments there's about a week of testing to make sure that it was a driver issue.

Perfect Tom, my tests line up with Carny_Priest i.e. I can consistently get the correct tables selected with WaitFor=9 and Table Select Delay - long, those appear to be the magic numbers, the loading is faster with this version too. Thank you!

Sadly I'm struggling with DOFFX2, my input controller only outputs joystick buttons and that program only seems to respond to keyboard presses. I tried mapping the keys using another program but it clashed with x360ce which I'm running to enable the plunger....

Behave :-)

Any chance once that its out we could carry on testing to reduce a couple of the longer loading delays Tom? I wondered if the unused waitfor setting (I'm assuming from your earlier comments that its unused) to adjust the delay before sending the first keystrokes, that would allow for the loading delays between SSD and HDD installations for example.

Right here the latest results videoed Tom: Short (fail on screen scroll as mentioned before): https://1drv.ms/v/s!Ao6k3CIlgOqjm9kfcejXbXbn4sBJug Medium (fail on screen scroll as mentioned before): https://1drv.ms/v/s!Ao6k3CIlgOqjm9kgUkW4buim4q2wTg Long works fine: https://1drv.ms/v/s!Ao6k3CIlgOqjm9kZGbYkY1hVWZTfdA Very Long works fine: https://1drv.ms/v/s!Ao6k3CIlgOqjm9keT0BnU4wg3IR30Q Just to reiterate I had to rebuild the entire hard drive from a back up to get this working as it was before, looks like a windows or NVidia update may be responsible, before the rebuild the game missed the initial key presses due to things not being in focus. Screen mode and aero made no difference the outcome was that the 'last table' option was picked and on the faster settings a PinballX crash and error. Would it help you if we shared our video driver builds?

Having just left Microsoft but remained on the Windows a Insider Program, could I just offer a small caution. Win 10 will attempt to install the latest approved NVidea drivers automatically, which is a good thing for some but may not be for cab builds. So it's worth going into your settings and set them so you can approve updates to avoid this and instead updates from the NVidea website. Obviously this only applies to NVidea users, I have two Win 10 machines in the house one running AMD Catalyst and the other NVidea and the AMD standard installation is not overruled in this way. My cab runs Win7 x64, I like stability...........

The new UI is awful, if they were trying to prevent cab owners running TPA they could not have done a better job of it. I've locked the build by blocking steam updates to TPA in the firewall rules just to stop the UI expansion of tables, every one they add makes for a painful .xml update to keep the cohesion of the interface. If only we could call the tables directly everything would be fine as the community have solved everything else, nut every update breaks TPAFreeCamMod too. I get that the legions of Android players are far more important to the programmers for income but the wider pinball community have also supported the game and kept it front of mind and they would do well to look at the example set by PinballFX2 and Zaccaria Pinball.... ......sorry rant over.

Just a thought but the other thing that may be worth trying is ticking the Disable desktop composition' box under the same tab Draco. That was the only way I could get Zaccaria Pinball to recognise the .ahk I made to automate the start up to menu for that game. If not it just sat there, I could hear the clicks but they made no impact on that program.

I'll rebuild things when I'm back Sunday evening and shoot a video for you Tom. Re my post above could you confirm that none of the config files are changed by swapping the .exe please. Draco, apologies in advance of you've already tried this but have you tried going into the TPA set up app and swapping the windowed/full screen windowed/ full screen setting? It makes quite a difference on my set up?

Hi Tom, I'm working away until Sunday but I gave it a quick spin before I left. Unfortunately it seemed to start sending the key presses too quickly after the first click on the opening screen so the last game panel gets clicked and then after a short while PinballX crashes with a error. I tried replacing the latest version with the previous .exe but the same thing carried on happening? Is there a PinballX entry other than the .ini, say in the appdata folder that could have been changed by the latest version? If not I need to restore back to one of the saves. :-(

Righto Tom, As I was stuck in due to the rain I've managed to give the new file a run out, the only hiccup was that steam updated Pinball Arcade so I had to revert to the earlier 1.52.8 version so we are not dealing with a moving target. Here are the results. Note: 'WaitFor' is set to '0' in the [Pinball Arcade] section of PinballX.ini SHORT DELAY (50) Random selection of Addams Family, I believe related to the error below: https://1drv.ms/v/s!Ao6k3CIlgOqjm819AF-wzNPhfU3HaA Correct selection of tables only providing they are on screen and scrolling is not required to reach them, otherwise the selection is incorrect by one step too far down, the extra step seems to happen as the cursor moves down onto the table selections: https://1drv.ms/v/s!Ao6k3CIlgOqjm81-QgpZoTIgAP-ZZA MEDIUM DELAY (100) Works!: https://1drv.ms/v/s!Ao6k3CIlgOqjm81__FZEB_sjB1tASw LONG DELAY (150) Not working, the selection is incorrect by one step too far down, the extra step seems to happen as the cursor moves down onto the table selections: https://1drv.ms/v/s!Ao6k3CIlgOqjm84AAcLbseeAZOpXMA VERY LONG DELAY (200) Not working, the selection is incorrect by two steps too far down, again the extra steps seem to happen as the cursor moves down onto the table selections: https://1drv.ms/v/s!Ao6k3CIlgOqjm84BfnzESlwHDfR6Ug

Hi Tom, Just ran it for about 50 selections, the results are encouraging: - Short does not work on my rig, I get the Addams Family selected an awful lot or random overshoots - Medium, long and very long work consistently, unfortunately they always make the selection below the target i.e. one row down - every time. So selecting the first four table is not possible - There are some fairly long waits in-between some sections - Tested direct and with TPAFreeCamMod using TPA v1.5.8 I thought that a video would probably explain the above so the following is with the wait set to very long for clarity and shows Diner being selected (this results in El Dorado playing): https://1drv.ms/v/s!Ao6k3CIlgOqjm8s8k1VH5v3pkzUnJw Hope this helps

Happy to help Tom, here's my spec's: My cab runs an i5 4570 at 3600Mhz, linked to a 40" main screen running via a GTX670 2G card and the 2nd 32" backglass screen and third 17" DMD screen running off the on board Intel video supplied by the CPU and the ASUS H81-M Plus motherboard. There's also twin SSD's, a good quality modular PSU, additional USB ports and 4G of1600MHz Viper Ram. There more in a post on my cab here: http://www.vpforums.org/index.php?showtopic=32481&hl Prior to the change I had the two TPA timings set to '1' in the ini and everything worked every time. After using V2 there seems to be little difference to the results on any of the timings.

I've lost count of the timing changes in my AHK's as TPA has expanded and evolved. I'm not too worried about cab support as the TPAFreeCamMod takes care of that but if we could just call the tables directly... Thanks for what you do Tom, it's appricated.

I'm calling TPA from an AHK .exe in order to run LedBlinky as well as TPAFreeCameraMod, but to test just using the DX11 version on its own I go into the TPA folder in the SteamApps folder and rename PinballArcade11.exe to PinballArcade.exe. Not the most elegant solution but it does work as long as you also rename PinballArcade.exe to something else first.

You could try changing the pinballarcade.exe entry in the .ini to pinballarcade11.exe as it makes a difference to the focus.

Does the DX11 version do the same thing Draco? Good to see Zaccaria Pinball in there as well, it's a great program can't wait for full cab support :-)

Hey Tom, like Draco I've tested this on all settings and with/without the TPAFreeCamMod, everything works but the table selection is still screwed. The most common fall down is the up/down selection going one step too far or the Addams table gets randomly picked . I'm no coder but I do have access to some tools and by my best guess PinballX is blameless, it seems to be the V2 interface in TPA is stupidly sensitive to key press length timing, for example even simple down presses on my keyboard can send the selection skipping. My best suggestions would be to either shorten the time of the PinballX key stroke rather than the time between keystrokes, or if that's not feasible just wait until Farsight decide to sort the whole thing out........ I do have a working solution which is to drop the direction keystrokes in favour of the mousemove/ mouseclick command, that does work but needs a screen scroll for the lower icons on my cab, at the moment the code is beyond me so I have knocked up a simple AHK which allows TPA to have it's own entry in PinballX to fire up LEDblinky, TPAFreeCamMod and TPA, it then auto clicks through to the menu and I use the cab buttons to chose and select the table. TPAFreCamMod then takes care of the DMD and backglass. It's not elegant but it works.....