7 replies to this topic

[jevansoh]

I can't get Pinup Popper to close/exit a Visual Pinball table.

 

I'm up to date on all software and I'm using a different key for Popper's exit than I'm using for Visual Pinball exit emulator.

 

The only way I can get a Visual Pinball table to close/exit from within Popper is by pressing the ESC key which closes the emulator but also closes popper, although it still runs in Explorer and I have to end that process manually.

 

No matter what key I assign to Popper's exit table, it just doesn't respond.

 

Any help would be much appreciated.

 

Thanks.

Edited by jevansoh, 11 February 2023 - 10:07 PM.

[jevansoh]

I've also tried setting PupCloser to run as administrator and tried the different options (1-5) but that doesn't help.

 

Future Pinball closes just fine and takes me back to Pinup Popper just fine.

 

But I just cannot close/exit any Visual Pinball tables with the exit emulator button.

 

The only thing I can do is close it with the "Q" button which closes Visual Pinball but also closes Pinup Popper, yet it leaves it running in explorer so I then have to end the task and reopen it.

 

Any suggestions would be much appreciated.

[jevansoh]

I've exhausted all options at this point.

 

If anyone has any ideas, I'd really appreciate it.

 

I've literally tried everything from every search result and am getting concerned this might not be possible to fix.

 

For some reason, no matter what I try, Pinup Popper simply won't exit a Visual Pinball table with the exit emulator key I've assigned.  I've tried multiple different keys, as well.

 

Thanks.

[PoppSickle]

I also have this Problem

[dicre]

same problem here, any help?

[fhjui]

you can activate the log for pinup-popper:

create a file named PINUPDebug.LOG and PopperDebug.LOG in the PinUpSystem-Directory.

Perhaps you can find a hint in the log when you close the table, what happens in PUP.

Edited by fhjui, 21 April 2023 - 12:48 PM.

[JimBeamer]

I've exhausted all options at this point.

 

If anyone has any ideas, I'd really appreciate it.

 

I've literally tried everything from every search result and am getting concerned this might not be possible to fix.

 

For some reason, no matter what I try, Pinup Popper simply won't exit a Visual Pinball table with the exit emulator key I've assigned.  I've tried multiple different keys, as well.

 

Thanks.

 

Hello, I set my settings in the Popper/Controller Setup like this and it works perfectly for me:

 

......................................Keyboard .......KeySt ......Joy Codes

Exit Emulators ...................81 .............Key-Q ............2

Menu / System Exit ...........27 .............Escape ..........2

 

Joy Code 2 is the exit button for me. In VPX I connected the Q key to my exit button to exit the emulator.

I use the program JoyToKey for the configuration of the buttons and here I linked the exit button with the letter Q.

It is important that you do not use the buttons more than once in the JoyToKey program. This also led to errors in the operation for me.

I hope it helps you with your problem.

Edited by JimBeamer, 02 July 2023 - 01:48 PM.

[txpenguin]

Rather than keep banging my head against this issue and/or changing my button mappings/behavior (I want the same button to exit tables and popper) - I wrote this AutoQA Janitor setup to do the following:

Public Repo here: https://github.com/s...-autoqa-monitor
 

PopperAutoQA cycles every table in the database, plays each for ~48s, and moves on. It does not:

• close VPX cleanly when a table modal-pops (missing ROM, VBScript error) — those processes leak and accumulate
• log which tables failed
• categorize why they failed

This repo adds three lightweight PowerShell daemons and a SQL analyzer that fix all three:

Script What it does scripts/autoqa-watcher.ps1 Polls likely output dirs every 30s; logs every new/modified file with timestamp + size — useful for forensic correlation. scripts/autoqa-janitor.ps1 Every 15 min, finds any VPinballX.exe older than 5 min, captures its window titles + modal dialog body text, then force-kills it. Writes one row per kill to a CSV. scripts/list-leaked-vpx.ps1 One-shot snapshot of currently leaked VPX processes (for ad-hoc inspection). scripts/get-vpx-crashes.ps1 Parses Windows Application Error events for VPinballX crashes; emits CSV with timestamp + faulting module + exception code. analysis/categorize-failures.sql Joins everything against PUPDatabase.db to produce a failure-type breakdown (pure crash vs hang+kill vs silent hang) per table.

The combined output lets you go from "1300 tables, ~5–20% break, no idea which" to "here are the 168 broken tables, sorted by failure type, with the modal dialog text for triage."