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

Double counting of Bases / Streaks #1

Open
IamToyflish opened this issue Sep 22, 2019 · 3 comments
Open

Double counting of Bases / Streaks #1

IamToyflish opened this issue Sep 22, 2019 · 3 comments

Comments

@IamToyflish
Copy link

i ran the scoreboard at german lasertag league today and noticed that streaks and base-shots (or takes? not sure) are doubled.

I can provide the json game logs, if that's helpful.

@tsilen
Copy link
Owner

tsilen commented Feb 26, 2020

We've seen something like before, too. The exact reason is not known, but I'm thinking that the UDP packets are actually coming twice, possibly due to the UDP broadcast leaking to multiple network interfaces or similar. On one of the local halls we saw similar issue (all events shown double) on one of the actual P&C scoreboards, while the other scoreboard didn't have this issue.

It could be that if the game server is both in the wired and WiFi network and also the scoreboard backend, it might record the events through both interfaces as they're just broadcasted to the entire network(s) and the UDP receiver also listens to the events on all interfaces.

Needs some further investigation and figuring out if the condition could somehow be detected..

@DorwardTech
Copy link

It's definitely the multi network issues. I've done it before on several scoreboard. Just needs to make sure that the pc running it, is only in 1 ip range.

@907github
Copy link

Q> What laser Tag system are you using this with and is there an example of what it looks like.? Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants