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.

Sign up for GitHub

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

Jump to bottom

[Bug] Error in serverlist: The game is not connected to the Launcher #55

Closed
O1LER opened this issue Dec 23, 2022 · 5 comments
Closed

[Bug] Error in serverlist: The game is not connected to the Launcher #55

O1LER opened this issue Dec 23, 2022 · 5 comments
Labels
bug Something isn't working in progress this is actively being worked on
Milestone
v2.1.0

Comments

@O1LER
Copy link
Contributor

O1LER commented Dec 23, 2022

Describe the bug
While in the serverlsit, the game shows an error, not connected to the launcher.
Despite the launcher being up and running, without errors and saying: Game connected!

To Reproduce
Unknown

To solve the issue, it is enough to log out and log back in, without needing to even restart the game

Expected behavior
While the launcher is running and showing connected, the game should also be connected to the launcher

Screenshots
image
image

beamng.log
@Anonymous-275 Anonymous-275 transferred this issue from BeamMP/BeamMP Dec 24, 2022
@Anonymous-275 Anonymous-275 added bug Something isn't working in progress this is actively being worked on labels Dec 24, 2022
@Anonymous-275 Anonymous-275 added this to the v3.0.0 milestone Dec 24, 2022
@Anonymous-275
Copy link
Member

Anonymous-275 commented Dec 24, 2022 •
edited
Loading

Transferred to launcher,
Fix in V3

@O1LER
Copy link
Contributor Author

O1LER commented Dec 24, 2022

So its a launcher issue despite the launcher being ok and without error?

@Anonymous-275
Copy link
Member

So its a launcher issue despite the launcher being ok and without error?

It is a shared issue that is only fixable by eliminating the local socket method used in V2

@Anonymous-275
Copy link
Member

So the only fix is to change that method

@O1LER O1LER mentioned this issue Jan 1, 2023
Closed
@Anonymous-275
Copy link
Member

Please reopen if this persits in 2.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working in progress this is actively being worked on
Projects
None yet
Milestone
v2.1.0
Development

No branches or pull requests
2 participants
@Anonymous-275 @O1LER