Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Fuzzy matching #131

Open
Heartman30044 opened this issue Feb 3, 2025 · 13 comments
Open

Improve Fuzzy matching #131

Heartman30044 opened this issue Feb 3, 2025 · 13 comments
Labels
bug Something isn't working

Comments

@Heartman30044
Copy link

What version of B2S Server are you using?

2.1.3

Can the bug depend on a certain VPX or VPM version?

latest vesions as of this date

Describe the bug 🐞

I had 2.1.2 installed and the following was working properly:

Cosmic Princess (Stern - 1979).vpx
Cosmic Princess (Stern 1979).directb2s

I then updated to 2.1.3 and the Directb2s is now longer found. If I change the name to exactly match, it works as expected.

Looking at the B2STableSettings. it doesn't seem to matter whether the global setting is set or not.

Hopefully this is enough information. If not, let me know. The table and backglass are in a separate folder with a unique B2STableSettings and Screenres files.

Thanks

Expected behavior and solution proposal ✅

I followed my update process that I have done before. 2.1.2 was installed. I copied the 2.1.3 files over and reran the register exefile.

Relevant log output

@Heartman30044 Heartman30044 added the bug Something isn't working label Feb 3, 2025
@JockeJarre
Copy link
Collaborator

Hi, the "fuzzy" matching was updated in 2.1.3 to only "fuzzy" match after the last ")"
so the names has to match fully like "Cosmic Princess (Stern - 1979)" and then be whatever you want...

The problem was that the old "fuzzy" match used the dos 8 char short names, which means it matched far to much.

@Heartman30044
Copy link
Author

Ok, Thanks for the reply - not sure I like that, but it is what it is. I will just have to go through all the tables and update the B2S filenames.... I understand what the fuzzy matching is now. Since I have all the tables in their own folder, the fuzzy matching (the old way) never gave me a problem.

Thanks.

@JockeJarre
Copy link
Collaborator

JockeJarre commented Feb 3, 2025

Thanks for understanding! We ALWAYS had problems with users where the old logic made it find the wrong backglass. (as long as it matched 4-5 chars it was happy)
I also understand why you never had a problem, but I hope to be able to keep the new way of working.
Reason for searching for the last ")" is to make sure the same table and brand but with different author or version number to match.

@JockeJarre
Copy link
Collaborator

before you change all, I might have an idea how it can be solved. Let me try it out...

@JockeJarre JockeJarre changed the title 2.1.3 Disable Fuzzy Matching seemingly not disabled. 2.1.2 works as expected. Improve Fuzzy matching Feb 4, 2025
JockeJarre added a commit that referenced this issue Feb 4, 2025
JockeJarre added a commit that referenced this issue Feb 4, 2025
Update to 2.1.4
@JockeJarre
Copy link
Collaborator

There is a new build available under actions (you need to login as a free user to reach them)
Can you please test?

@Heartman30044
Copy link
Author

I will, but it might not be until later today. This afternoon is pretty booked with other activities. Thanks.

@Heartman30044
Copy link
Author

Finally did some testing. I'm using PinupPopper Autorecord to do the backglass captures. I started by deleting all of the current ones and recaptured using the 2.1.3 version. Of the 50 or so that were captured, about 15-20 were not correct, so the names must not be compatible with the new method in 2.1.3.

I installed the test version that you provided and watched as it tried to do the ones that did not work before. All of the ones that I saw, loaded the backglass as I have named. However, the recording only seemed to capture every other one. I added some more delay the end game processing and that seems better.

Overall, I would say the new test version works better in my installation. However, I don't want the change if it still would cause issues with the others that wanted the change in the first place. I can change the names if needed.

Thanks.

@JockeJarre
Copy link
Collaborator

I would say, that now we have best of both worlds. I have removed the old wrong way and it would work for you even with all in one folder...
So we can close the issue now?

@Heartman30044
Copy link
Author

I would say yes - thanks for all the hard work.

@JockeJarre
Copy link
Collaborator

Thanks

@Heartman30044
Copy link
Author

If I can ask - and you see this, what is the new way of doing the matching. The reason is that in the following example it is using a version I wasn't expecting:

Table name:
Pabst Can Crusher, The (Stern 2016).vpx

Backglass I wanted to use:
Pabst Can Crusher (Stern 2016) full dmd.directb2s

Seems to always use this one (Doesn't seem to matter what prefix I put on it):
a-Pabst Can Crusher (Stern 2016).directb2s

Just wondering...
Thanks

@Heartman30044
Copy link
Author

Heartman30044 commented Feb 6, 2025 via email

@JockeJarre JockeJarre reopened this Feb 6, 2025
@JockeJarre
Copy link
Collaborator

I will check your new example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants