JoeViking245

Why not? If it's a matter of being 'locked', you can unlock it for editing (I believe near the bottom of the View menu?) Ya, that won't work. "The plugin no longer [...] extracts nor needs the tables script". That is to say, it doesn't look for or read a .vbs file. It reads the .vpx file directly. (The "script" is at the bottom of the file, past all the computer jibberish). Which leads us to, if you have an external script for a table and change the ROM in that script, the plugin will [still] read the 'old ROM' from inside the .vpx file. Only.

For Theatre of Magic, edit the script and look for the line Const cGameName = "tom_14hb". Remove the space in front of Const. So the "C" is the 1st character in that line. (I'll fix the search for that in the next update.) Twilight Zone has a table option to set which ROM version to use. "0" for Arcade-use credits (tz_94h) and "1" home-free (tz_94ch). Then plugin can't account for designer variables. The fix to have it work with the plugin would be to remove the option (including the "Select Case Romset" section and a few others) and then hard code the Const cGameName = "rom_of_your_choosing" (with no spaces in front of the first "C" ) I think that's the only table I've seen where the developer took the time to add in that option. That's exactly it. The plugin doesn't cross against VPMAlias. I could probably add that cross check in. Someday. I would need to a complete rewrite of this 3+ year old plugin to get it available in BB. Due to the popularity of this plugin, if I get bored enough I'll contemplate a rewrite. BTW, thanks for being the 1st to provide a thorough stress test and feedback since its release over 3 years ago. (Honestly, I had almost forgotten about this plugin. )

@Sbaby Disregard all of what I wrote above. Try this version. The games' ROM path file extension will need to be .vpx (or .vp9 or .vp8) The plugin no longer: looks for or even cares about VPinball.exe (or any name variant of the executable). extracts nor needs the tables script The attachment only has the plugin .dll file in it. Just replace your existing one with it. You will still need the existing "PINemHi" subfolder from your previous installation. VPXhiScores (v1.3-beta-1).7z

I dug deep into the archives and found the original code for this plugin and now see your issue. To have the plugin enabled (not grayed out), it looks for game's emulator path to contain "vpinballx". It also uses that path to execute extracting the tables script to get the games ROM. At the time (over 3 years ago), this seemed the most logical route to determine if the game was a Visual Pinball game. To make this work for your situation, I could change the logic to look at the games ROM path and check if its file extension is .vpx. Should probably check for .vp9 and .vp8 also if you still use those tables. Is it safe to assume that your VP games ROM path all point to one of those 3 file extensions? Next, I need to figure where your vpinball executable is located so the tables script can be extracted if it doesn't already exist. PINemHi only knows where the nvram folder is (via its .ini file). And there's no reasonable way to get the executable to vp using that path because there isn't consistency to how the .exe's are named. I'm thinking the easiest way is to have you add a text file in the plugins folder that contains [only] the full path to vpinball???.exe. (something like vpLocation.txt) Then if the script needs to be extracted from the table, it'll 1st look in the emulator's application path for "vpinballx" (so don't have that in the filename of your AHK script ). If it's not there, then it'll look for "vpLocation.txt" in the plugins folder. If that exists, it'll read the 1st line to get the full path. The plugin only extracts the table script if one doesn't exist for the table being launched. So, if your custom script is in the same folder as the table AND is named exactly the same as the table (minus the file extension), it won't get extracted. Does anything stand out to you that any of this may not work?

[temporarily] Set your emulator to the VPX executable run the plugin [once] for each table you want to see high scores for, "This is where it extracts the tables’ script." [when you are all done] change it [the emulator] back to your AHK script. aka, after doing the above steps [to extract the .vbs file] the emulator you use doesn't need to point to VPinballX.exe anymore. aka, you don't have "to go through all these steps every time I launch a game". Just the one time for each table to extract the .vbs file. I suppose you could create a batch file or AHK script that will loop through your tables, running VPinballX-x64.exe -ExtractVBS [filename], to get the .vbs files extracted. That way you won't need to change the emulator at all in LaunchBox. Again, as long as the .vbs file exists next to its corresponding table, there is no need for VPinballX-x64.exe to be 'the emulator'. Set your emulator back to your AHK script and see if the plugin [still] works for that table. It should. Unless you deleted the .vbs file.

Thanks! Glad to hear it still works in 2025. Yes. Extract the tables .vbs into the same folder as the table. (See How it works and What to Expect). Set your emulator to the VPX executable and run the plugin for each table you want to see high scores for, then change it back to your AHK script. Or, from the command prompt (or in a batch file or in an AHK script) run the VPX executable and use the parameters -ExtractVBS [filename]. Where [filename] is the tables filename.

I heard of at least one other plugin having issues with the 13.19-betas. I believe because of the switch to .NET 9 (from .NET 6). So far, I haven't had any reports for the few plugins that I have out there (knock on wood). Probably wait and see what @LostArc79 says about unblocking and the LB version being used.

(With LaunchBox closed) try right-click clicking the dll file and select Properties. See if there's something along the lines "UnBlock" and a checkbox. If so, check the box, click Apply and click OK to close. Start LaunchBox. If that doesn't work, are you running the latest beta of LaunchBox. Or the latest official build (13.18)? @B-B-Lee Are you testing on 13.19-beta-3? Or 13.18?

The next plugin update will add a new feature that will tell you if there's an update available for download. So [after that], no more excuses of "I missed the update". But I will still rely on you and the Community to let me know when occurs.

Are you running the latest release (v2.2.5)? Just tested and it's working here.

As per the plugin title, it'll actually show high scores in both LaunchBox AND BigBox. To clarify, the high scores shown are only your local high scores [saved by MAME]. And only the top 3. For more information about this plugin, please read through About This File at the top of this page.