-
-
Notifications
You must be signed in to change notification settings - Fork 222
Rework VRChat OSC address/port handling #1701
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
base: main
Are you sure you want to change the base?
Conversation
Eirenliel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean it's not really thread safe even with this fix, but like... so is life.
| /** | ||
| * Close/remove the OSCQuery sender | ||
| */ | ||
| fun closeOscQuerySender() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if your addOscQuerySender is synchronized, that should be too, probably.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to just use VRServer thread, all the rest are on it anyways so we should probably just keep that up
Cleaned up all the OSC port initialization methods to make them clearer and handle match detection better. OSCQuery detection has also been changed to prioritize an OSCQuery entry that matches the configured IP and/or port. Also prioritized OSCQuery detection over using the manually configured address so there won't be duplicate data sent.
Should fix #1309