-
Notifications
You must be signed in to change notification settings - Fork 28
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
Doesn't work with VRChat #38
Comments
Upon investigating the log files it seems RPC isn't(?) disabled by default, as the logs mention that it failed to connect to Discord. But this could also be caused by purposefully failing as well.
Moreover, attempting to force enable discord RPC via the config.json file: https://docs.vrchat.com/docs/configuration-file {
"disableRichPresence": false
} does not work. Giving the exact same output. |
Hmm, I managed to get logs from the bridge and it seems like VRChat at least connects to the socket, but then it doesn't do anything from there.
Actually I saw something similar in LoL when I looked into #37, which makes me wonder if something else is supposed to happen outside of the socket. At least comparing to osu, there's nothing out of the ordinary in these first two messages. |
I've had some similar issues with No Man's Sky's rich presence not working, no clue if that's related. I know Discord has two versions of their rich presence, one of which is deprecated and the other is their GameSDK. I would hope most games have since switched but it's a possibility there's an issue due to the two different versions. |
They didn't and never will, as discord-rpc is simpler and better, while GameSDK is abandoned bloat that only causes problems |
I'm not sure if this is a VRChat issue or an issue with this IPC bridge but I've mentioned it both under the Proton/VRChat discussion on GitHub (ValveSoftware/Proton#1199 (comment)) and here. It's a good possibility that VRChat will disable its Discord rich presence when loading in Proton, similar to how they disabled AVPro players
The text was updated successfully, but these errors were encountered: