Search the Community

I have downloaded and debugged 57 VPX tables. I have a 2 monitor and pinDMD V3 configuration. All tables run fine and each tables takes only a few seconds (<10) to load using Visual PinvallX. MY only problem is a few or the tables I have to mouseclick the playfield to get them to run. I have tried a couple of AHK programs but no success yet. MY BIG CONCERN - when launching from PINBALLX, it literally takes almost 60 SECONDS to load a table. I have tried both with and without a HOTKEY program with the same result. I am runnig Windows 7 64 bit in Admin Mode. Pertinent files attached. WHY DOES iT TAKE SO LONG TO LOAD A TABLE IN PINBALLX? Surely this is not the norm? Please help!! log.txt PinballX.ini Visual Pinball.xml VPXtofront.ahk

Tom and rablack97, I could no longer comment on my last topic since was closed because I was able to have a work around using rablack97's VPX.exe auto hot key program he so graciously provided. I do believe there is a focus problem within PINBALLX. I followed all of the installation guidelines and was only able run subsequent tables by entering ALT TAB or running his VPX .exe ahk file. PINBALLX certainly allowed for running the executables so kudos for that. I troubleshot this for days before finally implementing his ahk fix to get the focus correct without having to use a keyboard. First table loads great but seems to lose focus somewhere in the process of cleaning out the old table and loading the next selection. rablack97 - I would love to get a copy of your ahk script so I can better understand what you did within in. I certainly understand if youd rather keep it to yourself. Tom - please dont take this as me being negative about your product. I just think it this focus issue could be resolved, it would allow for a faster smoother install. I am surpirsed more people are not experiencing the lack of focus issue. Thank you both again for your assistance is helping me find a workaround

I have finally switched to VP's True Fullscreen and am loving the extra quality of the playfield image... but.... (there's always a but ) The Samsung has the annoying habit of placing a large banner OSD (on screen display) across the top of the TV (playfield) each time the resolution changes or when it detects a new signal. Now everything is set to 1920x1080 in VP and also PBX... and this problem never happened when using VP in Full Screen Windowed. So it's associated with True Full Screen... it's as if there is now a break in signal as PBX hands focus to VPX and visa versa, and this promps the stupid OSD. Is there anything in PBX that would allow a constant signal to be maintained during the focus shift? It's not a major problem, as it doesn't effect game play at all, but it is an annoying problem as it disturbs the "flow" of the cabinet by increasing wait times as new tables are selected. Sadly, there is no way to turn off this feature in the TV itself (even in the engineer's menu)

Hi guys, it's not a big issue bit it is an annoyance that I would like to resolve. I recently upgraded my video card and had a few issues with screen positioning. Re-ordering my video cables solved that issue and PBX runs perfectly across 3 screens with over 150 tables.... BUT (there is always a but lol), one table 'Cactus Canyon Continued (PROC)' starts with the play field on screen, but not in focus. A single mouse click on screen brings the PF back into focus and it then plays fine. Any suggestions will be greatly appreciated. Cheers, Rusty.

Hi, Has anyone come across this issue with Desmume. I loaded up the game the first time around no problems, I set it up that %{Enter} to make it full screen and wait before keys 2000 before the full screen happen... Perfect. I go out of the emulator and start up a new DS game and it loses focus. It opens the emulator with out any problems but it doesn't go full screen nor I can use the controls on my xbox 360 controller to move around except for the xbox button to exit. I tried the latest version and the version that you get when you download from the GameEx. Has anyone else have this problem... and did you fix it??????