oscavmgr eventual osc disconnect, unspecified port closed

I'm unsure which port as the error doesn't specify but after some time eye and face tracking stops working, restarting oscavmgr and vrcadvert reveals that some port has closed. I don't even know where to begin with troubleshooting whatever may be causing this.

Feb 11 '25 10:02 blakeblair

What gives you the idea that the port was closed?

Try starting oscav with RUST_LOG=trace. this will log all outgoing messages. It will be noisy, but might help identify the issue. Do the messages stop showing once this issue occurs?

Feb 11 '25 10:02 galister

small update:

I've tried many combinations of troubleshooting steps and concluded that after the disconnect happens simply restarting VRChat will restore the eye and face tracking. This raises the question in my mind of why VRChat is closing the port after some hours of use. A friend suggested I look into whether or not other OSC apps do anything specific to inform VRChat to keep relevant ports open.

as for the rust log trace thing I'm not certain how to do that, should I edit my startft scripts that launches vrcadvert and oscavmgr?

also I'll be updating to the recent version tomorrow

Feb 13 '25 03:02 blakeblair

I've had a similar issue probably 2 years ish ago, when I was on Arch.

The workaround for me was to use an UDP relay such as https://github.com/danpodeanu/udp-redirect

I simply made the redirect tool open port 8999 and relay to 9000. Then i would launch oscavmgr with --vrc-port 8999. For some reason it prevented the OSC from breaking.

However because I haven't seen this for so long, I'm wondering if it's the proton version. Are you using the recommended Proton (RTSP)?

Feb 13 '25 08:02 galister