-
Notifications
You must be signed in to change notification settings - Fork 64
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
Winsock error - Crashing on startup with 1.0 update #47
Comments
I have same errors, however it is actually working, I am able to connect via TZ: Europe/Vilnius
SERVERNAME: origin
#VR_NAME: origin
VR_PASSWORD: somepass
VR_DESCRIPTION: "some desc"
VR_MAX_USERS: "8"
VR_MAX_ADMINS: "2"
VR_FPS: "120"
VR_SECURE: "true"
VR_LIST_ON_STEAM: "true" |
Same issue for me : Direct connect is working, but the server cannot be find through Steam or in game.
|
glad to see I'm not the only one with this issue, I can echo @coute's issue exactly |
Inspired by #33 (comment) TZ: Europe/Vilnius
SERVERNAME: origin
VR_LIST_ON_STEAM: "true"
VR_LIST_ON_EOS: "true" and now it is visible on steam server list, gonna add one by one and check when it disappears. |
So after adding the password it is still visible in server list, note that I had to change "Merciless Setting" to show in server filters even though all of my game settings should be default. With that said, I am still unable to join a game with password via server list, I get |
The same is being reported on Reddit and Steam forums. Most are reporting success after changing ListOnEOS to false, but leaving ListOnSteam true. See: https://steamcommunity.com/app/1604030/discussions/0/3272440173687560495/?ctp=4#c4358998752032497713 |
I have the same issue, changing the ListOnEOS / removing the password didn't help, it is still crashing. Running this in a Ubuntu 22.04, 4-core, 16 gb vm |
I wasn't able to get mine to appear in the list yesterday, so everyone I shared with just connected directly. Big update this morning that appears to have created a lot of client crashes. I updated my client and restarted the Server, but now I can't connect. The logs show the same as above, which seemed to work fine yesterday. Does the Server update on restart? I didn't see anything for that in the logs. Edit: Update, I was clicking the continue button which would eventually time out trying to reach the server. I can still connect if I go to play online and use the direct connect option there. I'll try re-enabling ListOnEOS to see if that fixes the Continue button. |
I had the same issue, restarted the server and I see the exact same logs. However, by using the direct connect with the IP address and port number I am able to connect and play. |
The game is working perfectly with a new run of the container (from scratch). I'm on it with several buddies (on unraid-dockercompose) PS: do NOT join via Steam. That doesn't seem to work, using a password. |
Another report of this issue #56 |
I need someone with this issue to test trueosiris/vrising:latest. |
@TrueOsiris for example, me. I have tons of "fixme:winsock:WS_setsockopt SO_SNDBUF ignoring request to disable send buffering" in logs.
|
The text was updated successfully, but these errors were encountered: