Raphiiko
It seems that when changing the listening port for OSC through VRChat's
--osc
launch parameter, the default port 9000 is still advertised over OSCQuery: Both through the
?HOST_INFO
response (see picture), as well as VRChat's own
._osc._udp.local
zeroconf advertisement.
Steps to reproduce:
  1. Change VRChat's launch parameters to change the OSC listening port (e.g.
    --osc=9050:127.0.0.1:9051
    )
  2. Launch VRChat
  3. Note how VRChat still advertises port 9000 in the zeroconf advertisement (
    ._osc._udp.local.
    )
  4. Note how VRChat still advertises port 9000 in its
    ?HOST_INFO
    response.
Expected behaviour:
For VRChat to advertise the actual OSC port it listens on, as it currently seems to be hardcoded. Automatic discovery goes both ways, and right now this means VRChat's OSC port is not actually discoverable over OSCQuery.
January 15, 2024