8trek

Sorry but not sure i follow "when you press the exit button that is defined in px, it closes complete your emulator"... prior to disabling force exclusive fullscreen mode when i try to exit table in px i get the prompt mentioned earlier. Also don't follow your last sentence.

I tried both yesterday before just disabling force exclusive fullscreen mode and didn't work either.

ESC is not disabled... don't know what else to tell you but turning off exclusive fullscreen mode worked... not sure what it does if you don't mind indulging me. Yes, you have that correct regarding the BG.... yea, making sure everything is minimized or closed i guess is my only workaround.

Looks like i figured out the escape problem... disabling force exclusive fullscreen mode in vpx did the trick, no more prompt and game just ends inside px. Now unfortunately, still have the original problem when i exit a game the backglass video is behind other windows opened on the desktop. Again, also only happening with vpx tables.

Okay now things are getting more weird. When i hit escape in game play (while not using PX) i get this prompt but it quickly goes away and table ends. When i do same when running inside PX the prompt remains.

All pinball related programs including PX are outside of the protected areas. I've removed the run as admin but doesn't help. Still get the confirmation window and have to hit Q. After doing some searching i'm seeing other people having same issues.

not sure what you mean here

PX is running as admin, both in properties of the executable and logged in as an admin. I was NOT running VPX as admin inside the properties of the file but just changed it but has no affect on outcome. I have discovered the exit issue is only with X tables, not others that i have like 991, 995, and PM5. As of this moment I do have the ESC key set to end emulation in PX. Again works fine for all tables but X tables. Again what happens is the confirmation window appears and you have to hit Q. After this the X emulator does not die, I hit ESC again and the emulator dies and PX interface comes back however the BG is beneath other windows as is the title of the subject. So looks like something to do with VPX I guess?

Well that is a new problem that has surfaced. Discovered for whatever reason now on some tables when i hit the ESC key i started getting the confirm prompt (aka hit Q).... used to always be hitting ESC would just bypass that question. So if you see i hit Q twice in the logs it's because i just changed my pinscape controls to hit Q one on press and another on release... but guess this will cause problems on tables that don't require hitting Q twice.

Visual Pinball.xml

Going to attach another set of logs and config files. This time what happened was after exiting a game the playfield is black and the bg is like described above... going from bad to worse. Also worth noting this time went back to the 32 bit version thinking that might help.... but not. I then hit exit on keyboard then both display again. PinballX.ini log.txt

log.txt PinballX.ini

was happening once and awhile on older versions too. alt-tab does nothing.

either 1 of 2 things happens, either black screen or other windows opened like file explorer

As the title states... have tried latest and greatest px versions, both 32 and 64 bit. Not running any plugins or other software that would cause this. I know you'll want logs and all that but just though i'd pose the question first to see if anyone has heard of this before. Not using the .direct2bs option, just bg videos. Have the latest codecs. Win10 i7 cpu, fairly decent Video card... other than this tables run fine for the most part. Thanks.

He is correct although there is a bug with versions somewhere past 3.75 that this functionality stopped working.

FYI... problem solved with 3.75 and i now realize what the rom button is for.

It must be a version thing cause as Lizard did i installed 3.75 and problem solved.

Here ya go... i can't find a pindmd_log.txt or pindmd.ini file. Also, what is the rom button inside the game manager for? Some of my tables have it selected and many do not. Thanks! PinballX.ini log.txt XDMDlog.txt Visual Pinball.xml

Cool... thanks!

Hello Tom, see this thread for ref: Have you had time to look at this yet? Not sure if this is really a PX version issue or not. Thanks.

Great so where do i go to get older versions? Doesn't look like they are available anywhere.

Prior to recent updating of win10 and latest PX everything worked great. Now having an issue with my real dmd (PinDMD2 NOT PIN2DMD). Works fine when inside game it’s just when browsing inside PX either get nothing or if I grab the video files for real DMD inside game manager I get the video. I’d like to have the real thing like before when it reads from the rom (at least that’s my understanding of how it works). I read somewhere to copy the correct .dll’s for your dmd and paste in PX root folder and tried that… still no go. I also seem to recall years ago when I had this working it had something to do with selecting the ROM button for each game in game manager but that doesn’t seem to help now either. Actually I'm not really sure what the ROM button even does inside the manager. Any help would be appreciated much. Thank you.

This thread can be marked as solved. Here's what i did: Created a new root visual pinball folder called Visual Pinball Pre10 and copied everything over except made a junction link for the VPinMame folder as to avoid extra waisted space on drive. Then replaced the 4 B2sBackglass files with older versions. Now everything works from the command line and assume will work from PX now. My guess is problem had to do with the B2s server files as you mentioned in another post i looked at so think you for that and your help.

Something is getting lost in translation... There are 3 ways to run a table, either 1. inside PX, 2. from the VP gui, or 3. from the command line. If i run these tables using method 2 it works, 1 & 3 do not... so yes, it would appear this isn't a PX problem now that i realize method 3 doesn't work either. That said i guess the question now is why does method 2 work and the others do not? Guess i should post this question in vpforums. All of the BG files are named the same as the tables... it's a mystery as to why when using method 1 or 3 it's looking for the "rom".directb2s.