derpda

Its funny that it seems to check some kind of hash of the `WoW.exe` file, even if that's not the file being executed... if we can circumvent that, as in...

Solved it I think! At `0045DF30` in WoW.exe it seems to do the checksum change. The line is Followed by some stuff about a ChecksumExecutables.cpp, so I think I'm right...

I still experience this problem on Arch Linux. The update to 1.66.4-2 did NOT fix this for me, but setting `tailscale set --stateful-filtering=false` did. Maybe this setting is not reliably...

Thank you for getting back to me =) I think this issue is fixed with PR #10! As mentioned in the PR, I have since made a host of other...

I believe ByteTrack ends up using the predicted bounding box for the next step instead of the current bounding box. See below https://github.com/Vertical-Beach/ByteTrack-cpp/blob/d43805d461a714f65da039981bd5f5d21cf5cf59/src/STrack.cpp#L110 I have changed that in my own...