3 replies to this topic

[Flipsync]

Pincab Toolbox is evolving!

The scanner just got richer: new checks (VPX version comparator, screen DPI, DMD COM port, system decimal separator, phantom VPinMAME config, default audio device...) and a new "Note" category for things worth flagging without tanking your score.

I am also building Repair — a tool to automatically fix what the scanner finds: unblocking a Windows-blocked file, restoring an archived ROM, cleaning up orphaned media, and more actions on the way.

I need your input: what checks would you want in the scanner, and what automatic fixes in Repair? Tell me what would actually save you time on your cab.
https://pincab-toolbox.vercel.app/

 

[Gemini Wings]

Fixing missing balls on start up, and adding music to table missing them. Like the vpx table o brother were are thou. Thank you

[Flipsync]

Fixing missing balls on start up, and adding music to table missing them. Like the vpx table o brother were are thou. Thank you

Thanks for the feedback, really appreciate it! Both are noted for Repair's roadmap.

On the missing ball(s) at startup , could you tell me a bit more? Does it happen on one specific table (like "O Brother, Where Art Thou?") or across several? And does it fix itself if you restart the table, or stays broken until you do something manual? That'll help me figure out if it's a table-specific config issue (which Repair could fix) versus a VPX engine/physics thing (which would need to be reported to the Visual Pinball X project itself, since I don't touch the core engine).

On adding music to tables that are missing it , just to be clear on what I can build: if you already have the audio file somewhere (just misplaced or misnamed) and Repair needs to find/relocate it, that's exactly the kind of thing I can add. If it's about sourcing music that isn't included with the table at all, that's not something I can build , has to stay something you add yourself. Which case is closer to what you're running into with "O Brother"?

Thanks again for taking the time to report this ,this kind of detail is exactly what helps me prioritize Repair correctly.

[Flipsync]

Hi everyone,

First off, I owe you all an apology: several of you ran into issues over the past few days, and that’s completely on me.

App failing to launch: On certain setups, the app crashed right at the splash screen. A GPU detection probe was failing before the window could even open. It had nothing to do with your setup and everything to do with my code. Fixed.

Broken update button: A backend change broke the link without me noticing. It took me a while to catch it. Fixed, and it no longer relies on any external components.

Antivirus alerts: Some of you flagged false positives during download. This is a common issue with unsigned software. Since code signing certificates are out of my budget right now, I’m tackling this by refactoring code patterns that trigger heuristic scanners.

Serum scanner false positive: Thanks to El'Baronrouge for pointing out that the scanner reports errors on perfectly working Serum installs. He’s right—it’s a false positive on my end. I haven't patched this yet because I need to inspect a working altcolor directory structure first. Guessing the rule fix risks breaking other setups. If you have a working Serum colorization, sharing your directory file list would be a huge help!

Fixed

App startup crash on specific GPUs.

"Check for updates" button non-responsiveness.

Right-click "Ignore result": counter and filters now update properly without guessing.

False-positive missing B2S backglass alerts on the three default VPX utility tables.

Missing B2S warning downgraded to a minor notice if a PUP-Pack is already active.

Demo files included with the tool are now excluded from disk scans.

Repair red cross icon display bug.

32/64-bit Serum verification check and actual port key parsing in dmddevice.ini.

What's New

Permanent ignore option: Ignore results permanently or set an expiration timer to review them later.

Installation snapshots: Compare two scans side-by-side to track changes.

Report export functionality.

Non-destructive script repairs: Neutralize hardcoded paths in table scripts without altering the original files.

DOF detector: Identifies unconfigured ROMs automatically.

Diagnostic tab: Inspect raw data read at startup (ideal for troubleshooting and bug reports).

In-app bug reporting button.

Play Optimizer tab: Sneak peek UI (engine currently in development).

Localization: Added German (alongside French, English, and Spanish).

Cancelled Features

I started building an automatic relocation tool for POPMedia and PUPVideos to a secondary drive using NTFS junction points. This feature has been scrapped and will not be released.

Creating junctions programmatically relies on system calls heavily exploited by ransomware. On unsigned software, including these commands triggers aggressive AV heuristics—even if the code never executes. Keeping the app clean and trusted by security software takes priority over adding this automation.

Note: The manual procedure (using Link Shell Extension or mklink /J) remains documented in the Diagnostic tab.

How to Update

Download the latest package from the standard release page and overwrite your existing directory. No uninstallation required—your settings, exclusions, and snapshots will remain intact.

Huge thanks to everyone who took the time to report bugs instead of just closing the app. That’s how this tool gets better.