Wahreez McDermott

Thanks!

My Windows language is English and I live in Texas. DBManagerLog.txtPinballXDatabaseManager.ini Thanks!

I downloaded the newest version of Pinball X Database Manager. I hadn't touched the software in roughly two years, but after updating everything appears to work properly. The one issue I am having is that when I update a table with the newest version I am still continually getting "New Version available" when I restart the Pinball X Database Manager. I tried using the 'acknowledge' button, but that gives the following error... ERROR INFO : Datetimereformatstring2date String '2025-01-17 18:13:28 23:59:59' Was Not Recognized As A Valid Datetime. ERROR INFO : Backnowledge_Click Conversion From String "" To Type 'Date' Is Not Valid. I managed to work around the issue by opening the table and making a small meaningless change and then saving it so that I no longer get an update notification, but that's not a proper fix. Thanks for your help! I think it has something to do with the "Last Spreadsheet Date" which is listed as 2025-01-17 18:13:28 23:59:59 in the log file. I don't know how to fix it though. Edit: I have all my tables in \Visual Pinball\Tables\VPX

Both of those looks very sweet!

I don't think it's an issue with the script as the f11 stats show the script is only using 2% CPU. The author knows about the issue, but doesn't want to try and fix it because he has no idea what it might be. It's not a big deal, I just ignore it now. Thx for the reply!

Your understanding is correct. I have an i5-6600K with 16GB Ram and an RTX 2700. I'm able to run VPX tables at 120hz in 1080p with AO and Quality FXAA or SMAA. ScSP will work as well, but I do not bother to run it. I can also run with SSAA4x, but I choose not to right now because it's so hot outside here in the south. There are two VPX versions of Strike N' Spares, but they are the same copy despite occupying different data base entries. The issue with the VPX Strikes 'N Spares is that it'll run fine if you want to play one or two games, but over time it gets worse and worse. It has something to do with the physics as the VPX version starts around 20% (via F11 in VPX), but each time balls are returned after firing at the pins the physics value gets higher and higher until it's consuming all of the CPU. It's not an issue with the script as the % usage for script functions stays very low. I've become used to the single obsolete table entry and have learned to ignore it. I doubt they'll be another VP9 table in my database. Thanks for your time and response!

Hi, I'm running PinballX in a very basic configuration. Single Screen and using only Visual Pinball tables. I decided to add one VP9 table to my list because the VPX version of "Strike 'N Spares (Gotlieb 1995)" doesn't run properly and starts to slow down badly if you try to play more than 1 game. As a result of adding this VP9 table every time I launch the manager I get the warning about an obsolete table. The VP9 version of Strike N' Spares is "obsolete". Is there anyway I can edit the xml or do something else to ignore that table in regards to possible updates? Despite there being a VPX version it's not an update because it doesn't work properly. I know this is probably an edge case cause I googled this thread for "obsolete" and didn't find anything. I would just ignore it, but obviously I'm incapable of that, lol. Thanks for your time!