This object is in archive! 

Crash to desktop upon server join since Crossplay update

Jack Bartlett shared this bug 3 years ago
Won't Fix

Elastic http response error BadRequest: {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"failed to parse"}],"type":"mapper_parsing_exception","reason":"failed to parse","caused_by":{"type":"json_parse_exception","reason":"Non-standard token 'NaN': enable JsonParser.Feature.ALLOW_NON_NUMERIC_NUMBERS to allow\n at [Source: (org.elasticsearch.common.bytes.AbstractBytesReference$MarkSupportingStreamInputWrapper); line: 1, column: 1659]"}},"status":400}

Worked fine until crossplay

A second file is included, maybe the error is more relevant.

Replies (5)

photo
1

Second error, same as above

photo
1

I've looked through the forum and tried all possible fixes so far. Deleted appdata/SpaceEngineers, verified game files, reinstalled, playing with no mods, ran a virus scan, and have all up to date drivers.

Notably, I uninstalled the game for extra memory for a brief time after the crossplay update and did not reinstall until after the hotfix. I am not sure that is useful but may be relevant.

I routinely get the first error included above.

Does space engineers leave behind any files during the uninstall that I should manually delete before reinstalling besides the appdata folder?

photo
1

Rolling back to the 1.196 beta causes the game to run fine, but then updating back to the current version breaks it again. Confirmed to be a game issue with the current version. Plz send help

photo
1

Hello Jack!

Sorry to hear you're having this issue. Is this happening with every server you try to join or only specific ones? Is it happening every time you try to join or are you able to get in at all?

Kind Regards

Laura, QA Department

photo
1

Every server, singleplayer included. Happens every time. We narrowed it down to the second error file I've included. Using a VPN causes the game to work fine. I don't consider that a solution though.

The error looks like it's related to epic games' servers and that would make sense considering this issue only started with the crossplay update.


2021-02-23 02:02:57.069 - Thread: 1 -> MyAudio.LoadData - START

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: invalid HTTP response code received. URL: https://api.epicgames.dev/telemetry/data/datarouter/api/v1/public/data?SessionID=%7BE28B50CA-4156-4F13-9883-188039C67D70%7D&AppID=EOSSDK.PhaseRelease.ReleaseBuild&AppVersion=1.9.0-14547226%20-%20%2B%2BEOSSDK%2BRelease-1.9-CL-14547226&UserID=&AppEnvironment=Production&UploadType=sdkevents, HTTP code: 0, content length: 0, actual payload size: 0

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: request failed, libcurl error: 0 (No error)

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 0 (Found bundle for host api.epicgames.dev: 0x148a6d358f0 [can pipeline])

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 1 (Re-using existing connection! (#0) with host api.epicgames.dev)

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 2 (Connected to api.epicgames.dev (34.200.61.131) port 443 (#0))

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 3 (We are completely uploaded and fine)

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 4 (TLSv1.2 (IN), TLS alert, Client hello (1):)

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 5 (Connection died, retrying a fresh connect)

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 6 (necessary data rewind wasn't possible)

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 7 (Closing connection 0)

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 8 (TLSv1.2 (OUT), TLS alert, Client hello (1):)

2021-02-23 02:07:38.425 - Thread: 27 -> EOS|LogHttp: Retry exhausted on https://api.epicgames.dev/telemetry/data/datarouter/api/v1/public/data?SessionID=%7BE28B50CA-4156-4F13-9883-188039C67D70%7D&AppID=EOSSDK.PhaseRelease.ReleaseBuild&AppVersion=1.9.0-14547226%20-%20%2B%2BEOSSDK%2BRelease-1.9-CL-14547226&UserID=&AppEnvironment=Production&UploadType=sdkevents

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: invalid HTTP response code received. URL: https://api.epicgames.dev/telemetry/data/datarouter/api/v1/public/data?SessionID=%7BE28B50CA-4156-4F13-9883-188039C67D70%7D&AppID=EOSSDK.PhaseRelease.ReleaseBuild&AppVersion=1.9.0-14547226%20-%20%2B%2BEOSSDK%2BRelease-1.9-CL-14547226&UserID=&AppEnvironment=Production&UploadType=sdkevents, HTTP code: 0, content length: 0, actual payload size: 0

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: request failed, libcurl error: 0 (No error)

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 0 (Found bundle for host api.epicgames.dev: 0x14908e6c3e0 [can pipeline])

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 1 (Re-using existing connection! (#2) with host api.epicgames.dev)

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 2 (Connected to api.epicgames.dev (54.165.168.103) port 443 (#2))

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 3 (We are completely uploaded and fine)

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 4 (TLSv1.2 (IN), TLS alert, Client hello (1):)

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 5 (Connection died, retrying a fresh connect)

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 6 (necessary data rewind wasn't possible)

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 7 (Closing connection 2)

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: 00000148EB5C4500: libcurl info message cache 8 (TLSv1.2 (OUT), TLS alert, Client hello (1):)

2021-02-23 02:19:38.431 - Thread: 27 -> EOS|LogHttp: Retry exhausted on https://api.epicgames.dev/telemetry/data/datarouter/api/v1/public/data?SessionID=%7BE28B50CA-4156-4F13-9883-188039C67D70%7D&AppID=EOSSDK.PhaseRelease.ReleaseBuild&AppVersion=1.9.0-14547226%20-%20%2B%2BEOSSDK%2BRelease-1.9-CL-14547226&UserID=&AppEnvironment=Production&UploadType=sdkevents

photo
1

Hello, Jack!

I appreciate this thread is quite old. Is this still an issue that persists? If so, can you please provide an updated log? If it is no longer an issue, I will close this thread for you :)

Kind Regards

Laura, QA Department

photo
1

Hello, Engineer!

Because there is no new comment from you, and we are unable to reproduce the issue on our own, I will close this thread now as outdated.

If you or any other player will experience this issue again, please make a new thread and provide all needed info there.

Thank you for understanding.

Kind Regards

Keen Software House: QA Department

Replies have been locked on this page!