Skip to content
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

SocketManager unable to recieve messages from ConnectionManager if it's the same steamid connecting. #745

Open
AncientEntity opened this issue Dec 2, 2023 · 0 comments
Assignees

Comments

@AncientEntity
Copy link

Describe the bug
It's possible this is just how SteamNetworkingSockets and the relay network works but I wanted to submit a bug, if this is intended please close it and let me know. In my Unity project if I create a ConnectionManager and then a SocketManager that connects to the ConnectionManager (aka my same steamID) it successfully connects (I have SteamNetworkingUtils debug messages everything on) and the ConnectionManager can recieve messages, but the SocketManager is unable to. But if I grab a second computer with a different Steam account the ConnectionManager and SocketManager can both recieve messages.

To Reproduce

  1. Create a SocketManager on the relay network (not IP)
  2. Create a ConnectionManager and connect to the SocketManager (aka the same SteamID as the person connecting)
  3. ConnectionManager can recieve messages but the SocketManager cannot.

Expected behavior
Not 100% sure if this is the intended but I'd hope that if steam says a successful connection was made then hopefully it would let the connection manager recieve the messages.

Desktop (please complete the following information):

  • Just updated Facepunch.Steamworks today to newest
  • Unity 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants