You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NelsonPJ — Today at 2:30 PM
I updated to 3.5.0 and started updating a few tables. I think I've seen this bug a couple times - when I drag a new VPX into the main window, VPStudio correctly identifies which table it belongs to, and I select the middle option to overwrite the existing table. But then after the table imports and the "Table Data Manager" box pops up, the selected "Virtual Pinball Spreadsheet Entry" is changed to a different version. You can see in the screenshot that I was updating JP's Deadpool (Team Tuga PUP version) to 5.1.2. It was previously 4.0 - and the version number in the main screen correctly updated to 5.1.2, but for some reason the Table Data Manager now shows a completely different spreadsheet version (some version with a VR room that's currently at v1.0).
Syd711 | [MAT] — Today at 2:38 PM
I think the "issue" here is that we apply the automatic VP-spreadsheet matching on table replace. The matching is and never will be a 100% reliable. So it may happen that the matching fails. I have to check if we try to keep it on table-replace which might be the better option - not sure about it.
...I just checked. Yes, we re-match tables on upload and replace. But thinking about it... if the table already has a VPS mapping, it makes sense to change the check so that we only take a closer look on the version and not make a full match again. I'll write a ticket for this.
The text was updated successfully, but these errors were encountered:
The text was updated successfully, but these errors were encountered: